Nash Services.

A brochure gets handed across a desk. It cannot be found at two in the morning by a consultant in a truck who needs a light tower on location by daylight. Nash had a fleet, three phone numbers and three safety certifications, and none of it existed anywhere Google could see.

The other constraint was honesty. No Google reviews yet, no heavy haul, no invented fleet counts. The site had to be built around what Nash can actually put on a truck, and nothing else.

The site runs on Astro and deploys as a Cloudflare Worker, so every page is prebuilt and served from the edge and the only server code is the quote form. The design is true black, heavy condensed display type, hairline rules and the client’s own fleet photography, with nothing generated in its place. The equipment hub breaks out into nine category pages, one per unit type, beside light oilfield hauling, commercial, safety, a page per yard, careers and contact.

Every rental page is written around the search it answers: light tower rental Grande Prairie, generator and light tower combo, wellsite shack rental. Each carries its own Service schema node, each yard its own LocalBusiness with coordinates and service-area towns, and the whole thing is tied together with breadcrumbs, a sitemap index and exactly one h1 per page. Deliberately no review or rating markup: Nash has no Google reviews yet, and the site will not pretend otherwise.

The integrations do one job each. Quote and contact forms post to a Cloudflare function that verifies a Turnstile token, drops honeypot submissions and sends through Mailgun to dispatch. A daily Worker is wired to pull Google reviews into KV and sits dormant until the Business Profiles are live, so the testimonials section switches on without a rebuild.

Tracking is built into the site, not bolted onto it. Google Tag Manager loads after the first interaction so it stays off the critical path, and the site pushes its own events: a quote form that actually got through Turnstile and Mailgun, a tapped phone number attributed to the yard it belongs to, an email click, a directions click, a form started and a form that errored. Nothing personal ever enters the data layer.

In GA4, form leads, phone taps and email clicks are the key events, with the yard, form and inquiry type as custom dimensions, so a monthly report can say which office the calls went to and whether they came from search. GA4’s own form tracking is switched off because it counts submissions the spam filter rejected. Google Ads conversion tags are imported and paused, ready for the day Nash decides to run ads, with no code change needed.

All of it feeds the Sixo client dashboard, so Nash sees sessions, landing pages and leads by channel on one page. The first quarter on a brand-new domain reads small, and the report says so plainly: what moves it is reviews, the Business Profile and telling existing customers the site exists.