Oil To Go

The problem

A quick-lube shop competes on a coupon and a different number at the counter. A mobile service has to win on something else: that the driveway is the shop, the price is the price, and the van really comes to your street. The first site was fast but thin. It could not carry a page per town, it had nowhere to publish the guides that answer what people actually search, and every price lived in more than one place.

What got built

Rebuilt in Next.js with both of our blocks vendored in: the CMS for the guides and the client admin for traffic, plan and tags. Every business fact (the phone, the service area, the prices) lives in one file that the pages, the structured data and the llms.txt all read, so the $69.99 on the pricing card, the town pages, a guide's sidebar and the share cards cannot disagree. The ad tracking carried over: every pixel event is mirrored to the Meta Conversions API from the server, so the ad account keeps learning when a browser blocks the pixel. A scheduled task drafts the next guide on the first of each month and files it as a draft; nothing publishes until the owner says so.

Details worth naming

• A home page built around the van: a full-bleed driveway hero with an ambient loop, a road along its foot that the van drives, and a pricing card whose jug fills to the five quarts included.
• One source for every price and fact, read by the pages, the structured data, the share cards and the llms.txt.
• A page for Marion, Hiawatha and Robins and one for fleets, each with its own share card and its own place in the sitemap.
• Guides published monthly from the site's own back office, drafted on schedule and never published without the owner.
• Server-side Meta conversions, so the cost per lead does not creep up as more browsers block the pixel.
• Dark mode, a real 404 (the van at a dead end), and every route drawing its own link preview.