Weatherguard NWA · An insulation contractor, findable in every city it serves

Weatherguard NWA is a family-owned insulation contractor in Bentonville. The crew installs spray foam, blown-in fiberglass, and crawl space encapsulation for homes and buildings across Northwest Arkansas. Homeowners shop for that work by service and by town, so the business had to be the answer to both questions.

The WordPress site it had could not give that answer. Page titles carried a product name and the brand but no service and no city, the words Northwest Arkansas appeared mostly in the footer, and a few stray pages had no real content at all. One wall insulation page was quietly earning search rankings that a careless redesign would have thrown away.

The brief was a site that earns the first phone call: a form short enough to finish on a phone in a driveway, the number one tap away, and proof that every request reaches a person. In a trade business, a lead that goes missing is money lost.

We started with how people search, not with a layout. Three service hubs, one each for spray foam, blown-in fiberglass, and crawl space encapsulation, answer what the work fixes, what installation looks like, and what drives the price. Spoke pages sit beneath them for wall insulation, fiberglass batts, commercial work, and metal buildings. The wall insulation page that already ranked kept its original address and became a full spoke, so its standing carried over.

Then the map. Every city the crew serves gets its own page, and the four anchor cities also get a page for each core service. Each one is written from that town's housing, neighborhoods, and common problems rather than swapped into a template, so no two read as copies. Navigation, footer links, and city grids read from Sanity, which makes adding a town a content task instead of a rebuild. Business, service, FAQ, and breadcrumb structured data ride on every template, and each FAQ is specific to its service or city.

The estimate form asks four things. Behind it, our own function screens for spam, emails the request through SendGrid, and files a backup copy in Netlify Forms, so one failing channel cannot lose a lead. If both fail, the visitor sees the phone number instead of an error. Every morning an automated check submits the live form as a test visitor, follows it to the thank-you page, and flags us if any step breaks.

The homepage also does one thing a template would not. It reads the day's real temperature from the National Weather Service and shows an estimated attic temperature beside the living room, with a static version as the fallback. Everything else is static pages with an inlined stylesheet and analytics that load after the page does, which is how the speed scores stayed high. A build step fails on missing titles, duplicate headings, broken internal links, and a changed phone number before anything ships.

The site went live on the client's own domain with every address from the old sitemap resolving to a live page or a redirect to its closest equivalent. At launch, PageSpeed scores were 96 on mobile and 100 on desktop.

Weatherguard NWA now has a page for each service, each city, and each pairing worth ranking for, a form that is tested daily, and call taps and estimate requests measured as events in Google Analytics. Search results take time to arrive, and the measurement is in place so the next chapter can be written from the numbers.