Precision Exteriors: 134 URLs, 26 Town Pages, Built On Our Own Money

Start with the disclosure, because burying it would undermine the point of the page. Precision Exteriors is not a third-party client. It is Adam Whitaker’s own exterior-contracting company, and Pufferfish Media exists because of it. Roofing, siding, windows and doors, gutters, decking and fencing, out of two offices in Cambridge and Salisbury, serving eight Maryland counties and two in Delaware.

That relationship is the reason this write-up is worth reading rather than a reason to discount it. Every decision described below was made with our own money on the line. A month where the phone did not ring was a month we absorbed directly, not a line item in someone else’s report. There is no version of this engagement where the marketing looked fine and the business quietly suffered, because they were the same business.

The problem was the ordinary one for a contractor with a wide service area: the crews drive to dozens of towns, and a website with one roofing page and one contact form gives a search engine no reason to show the company in any of them. National lead aggregators sit at the top of the results and resell the same homeowner to several contractors at once. Buying that lead means paying for a customer you had already earned, then bidding against three competitors for their attention.

The site was built as a structure rather than a brochure, and the structure is the part you can go and count.

Service architecture

Sixty-nine service pages, organised as a hierarchy instead of a flat list: 30 core service pages, 6 category hub pages that gather them, 29 child service pages beneath those for the specific jobs homeowners actually search, and 4 authority pillar pages that carry the depth. A hierarchy does two things a flat list cannot. It gives every child page an obvious parent to inherit relevance from, and it gives a reader a route from a broad question to the exact job without going back to search.

Location coverage

Twenty-six location and service-area pages: 19 built on the roofing-contractor-plus-town pattern, and 7 covering towns and counties more broadly. Each exists because there was something specific and true to write about working in that market. Where there was not, no page was published — which is why the count is 26 and not 80.

Schema

The structured-data stack is deployed across the site and is readable in any page source: RoofingContractor, LocalBusiness for both office locations, FAQPage, Service, Offer, PriceSpecification, BreadcrumbList, WebPage with SpeakableSpecification, EducationalOccupationalCredential, and Article on blog posts. The credential entity is the Owens Corning Platinum Preferred Contractor status, which has its own explainer page on the site rather than sitting as a badge image in a footer — a certification a buyer cannot understand is not doing any work.

Rendering and machine access

The site is server-rendered: the full body copy of every page is in the initial HTML response, not assembled by JavaScript afterwards. An llms.txt file is published so language models have a plain-text map of the site. Titles follow one pattern, {keyword} {City} {ST} | Precision Exteriors, and meta descriptions end with the phone number, so the number is visible in a result even when nobody clicks.

Twenty-four blog posts

Written against the questions homeowners ask before they are ready to call — storm damage, claims, materials, what a job costs and why. Blog posts do not close a roofing job on their own. They make the site the place the answer came from, which is what an answer engine needs before it will name you.

What is published here is what can be counted: 134 URLs, 69 service pages, 26 location pages, 24 blog posts, server rendering, llms.txt, and the schema types listed above. Open precision-exteriors.com/sitemap.xml and check every one of them. That is the entire claim, and it is deliberately the entire claim.

What is not published here is a traffic multiple or a revenue figure. We have those numbers, because it is our own company. We are not publishing them, because you would have no way to audit them and no way to distinguish them from the invented ones every other agency puts on a page like this. A number you cannot check is not evidence, however flattering it is.

The useful takeaway is not the size of the site. It is that this architecture was built and revised over years against a real profit-and-loss statement before any of it was sold to another business. The method on this site is not a framework read about in a newsletter. It is what we do to our own company.

How these numbers were measured

Every figure on this page comes from Google Search Console for precision-exteriors.com, read on 24 August 2026. The baseline is July 2025 and the comparison month is July 2026, so the window is a full thirteen months and the same month of the year on both ends. That matters for a roofing company, because comparing a July against a February would flatter the result for reasons that have nothing to do with the work.

Two things worth stating plainly. September 2025 shows an anomalous drop to 3,806 impressions against 21,684 the month before and 24,157 the month after; that pattern is a reporting gap rather than a collapse in visibility, and it is left in the record rather than smoothed out. And the strongest single month was May 2026, at 134,180 impressions and an average position of 11.3, which is better than the July 2026 figures quoted above. The later month is quoted because it is the most recent full month, not because it is the best one.

Average position across an entire site is a blunt measure. It moves as new pages start ranking for new queries, which can pull the average down even while the important pages improve. It is quoted here because it is verifiable and hard to game, not because it is the most flattering framing available.

Disclosure, again: Precision Exteriors is owned by Adam Whitaker, who owns Pufferfish Media. Nobody paid for this work and nobody chose this agency in a competitive process. Read it as a documented method with the data attached, not as a client reference.