An auto body shop rebuilt for local search and accessibility
S&R Motors runs a collision center and a mechanical service center from one shop in Hayward. Their WordPress site blurred the two, still advertised a location that had closed, and was missing accessibility features the owner had been asked about. We rebuilt it as 53 pages with the two sides of the business finally separated.
- 53 pages, every one server rendered
- Zero accessibility violations across 13 audited routes
- 17 legacy URLs redirected, nothing left to 404
- Call and text taps tracked as conversions
What was wrong
S&R Motors is I-CAR Gold Class certified for collision work and ASE certified for mechanical service. Those are two different businesses sharing one roof, and the old WordPress site treated them as one undifferentiated list of services. A customer with a dented fender and a customer due for an oil change landed in the same place and had to work out the rest themselves.
Three other things were wrong. The site still advertised a second location that had closed. Service pages sat at the root of the domain, which made restructuring risky. And in April the owner told us the site was missing two things he had been asked about directly: an accessibility widget and a cookie notice.
What we built
We split the site into two arms. A collision center hub and a service center hub, each feeding its own service pages, 26 in total: 16 collision, 10 mechanical. Every service page is driven by a typed model carrying its own metadata, hero image, benefits and FAQs, so adding a service is a data change rather than a new page to hand build.
On top of that sit seven city pages for the surrounding towns, a page covering the 21 vehicle brands the shop services, a blog, and a specials page where a selected coupon carries all the way through the booking link into the form, the lead email and the CRM record.
Three lead forms share one component and one API route: contact, estimate and appointment. The estimate form takes up to four damage photos, compresses them in the browser before upload, and delivers them as email attachments. On the server the uploads are checked against an allow list of file types, capped for size, and their filenames sanitized. Leads reach the shop by email and as a machine readable record posted into their DealerCenter CRM.
The accessibility work
We built the accessibility widget ourselves rather than dropping in a third party overlay. That was a deliberate call written into the spec as a non-goal, because those overlays have a poor record and a worse reputation. Ours has six toggles: large text, high contrast, underlined links, paused animations, a dyslexia friendly font and a large cursor. Settings persist, and an inline script restores them before the first paint so the page never flashes the wrong way first.
An automated axe-core sweep runs across the site. The audit committed at the end of April records zero violations across all 13 tested routes against the WCAG 2.0 and 2.1, A and AA rule sets.
The cookie notice was built as a real consent manager with separate categories for essential, analytics and marketing, and it gates both the analytics and the chat widget rather than just announcing itself.
Getting found
The shop is typed in structured data as both an auto body shop and an auto repair shop, with coordinates, opening hours and an eight city service area, alongside schemas for services, FAQs, articles and breadcrumbs. Every page has its own social sharing image, 43 of them. The sitemap is generated from the routes themselves, so it cannot fall behind.
Analytics tracks every tap on a phone number or text link as a conversion, which the old site did not do at all. Seventeen permanent redirects carry the old WordPress URLs to their new homes.
Questions
What is this site built with?
Next.js 16 with the App Router, React 19 and Tailwind CSS, hosted on Vercel. All 53 pages are server rendered.
How was the accessibility work handled?
We built the accessibility controls ourselves rather than adding a third party overlay, because those overlays have a poor record. An automated axe-core sweep runs across the site, and the audit records zero violations across all 13 tested routes against the WCAG 2.0 and 2.1 A and AA rule sets.
What happened to the old WordPress URLs?
Seventeen of them redirect permanently to their new homes, so the links and any ranking they had carry across instead of landing on a 404.
Can you build something like this for my business?
Yes. We work with local businesses across the United States, and every project starts with the same discovery and strategy work. Tell us about your business and we will tell you honestly whether we are the right fit.
