Supreme Nomads Detailing

One page wearing forty-six addresses.

The sitemap declared 46 URLs and all 46 returned the byte-identical HTML file — one title, one description, and a canonical pointing at the homepage from every route. There was no per-page metadata anywhere, so nothing decided what a search result would say. Schema existed but described the business identically on every URL, with no Service node for any service page. Detailing, ceramic coating, paint protection and nine add-ons all shared a single /services URL, so none could rank for its own search. Underneath, a 2.88 MB leftover stylesheet the design never used was render-blocking every load, and a 7,600-line script bundle re-ran on every click. On screen, the hero led with “our top priority is you” — no service named, no city, no price — and the video behind it never played on a phone.

Before

After

Fifty-three real pages, each answering for itself.

• One document became fifty-threeEvery route now has a hand-written, keyword-aware title, description and self-referencing canonical, prerendered into the served HTML at build time — built on React 19's native metadata, with no new dependencies added.
• A services architecture instead of a services pageOne /services URL became fifteen, each with its own schema and copy, plus four category pages with vehicle-size pricing tabs — all driven from a single data file so copy and pricing have one source of truth.
• Twenty-five location pages rebuilt as real local landing pagesCity-specific heroes, live Google reviews, from-pricing service cards, a service-area map and an on-page local FAQ, each with its own metadata and a per-city LocalBusiness node with real geo-coordinates — one component driving all twenty-five.
• The hero answers the first question a visitor asks“Mobile Auto Detailing in Charlotte” is what people actually type, so it became the first thing on the page. Price and a five-star review line sit directly beneath it, so someone deciding between a $60 wash and a $900 coating finds out immediately.
• 2.88 MB of dead CSS gone, and the bundle loads onceThe unused marketplace stylesheet was removed from every page and the plugins bundle stopped re-executing on every navigation. Mobile Lighthouse performance went 68 → 74 and LCP 6.6s → 4.7s, with zero layout shift.
• A site the owner can grow without meBlog posts from Sanity generate their own metadata, the XML sitemap builds itself from the same data files, and the gallery reads one Cloudinary folder per job — so the shop adds work by dropping photos in a folder.

The pages started earning strangers.

A Search Console baseline was captured at launch on purpose, so there would be an honest before to measure against; these are the two weeks after it. Before launch Google saw one page and showed it almost entirely to people already typing the business name. After, individual pages began ranking for themselves — Ballantyne at position 3–4, Lake Wylie for “lake wylie detailing” — and searches appeared that had never existed for this site. One caveat that changes how the whole table reads: nearly all of that growth happened while two dozen neighbourhood pages were still blocked from the index entirely.

What the client says.