Key facts
- The sitemap listed fourteen location pages, each for a neighbourhood in a single county on the far side of the metro from the company's address.
- No page existed for the company's own city, which appeared in its address and its lead form, or for the county that city sits in.
- The location pages were part of a JavaScript app that served search engines almost no HTML, so even the fourteen that existed were largely invisible, a separate finding on the same site.
- A home services company ranks most easily where it actually is, because its address, its reviews and its service history all point there, and the site had built pages everywhere else.
- The fix added pages for the home city and county with real local substance and kept the neighbourhood pages only where the company could show it works.
The finding
The company's location pages covered fourteen neighbourhoods, all in one county that is not where the company is based. Its own city, the one in its address and the one a customer would naturally search with the service, had no page. Neither did the surrounding county. Whoever built the pages seems to have chosen a target area from a map rather than from where the business is, and the result was a site that competed hardest where it had the least right to win.
What we looked at
We listed every URL in the sitemap and grouped the location pages by county. We compared that list with the company's address on the site and on its lead form, and with the county that address sits in. We fetched a sample of the location pages to see whether they carried local substance or a swapped name; they were thin and, because of the site's JavaScript rendering, mostly empty to a crawler. We checked the Google Business Profile's service area, which included the home area the site ignored.
Why it mattered for leads
Local search rewards proximity and consistency. A company's address, its reviews and its profile all say where it is, and a page for that place ranks with the least effort. Pages for neighbourhoods across the metro compete against companies that are actually there and rarely win. The company had spent its location effort on fourteen long shots and skipped the one page a customer in its own city, searching garage door repair plus the town, was most likely to click.
False positive checks we ran
We checked whether the company had recently moved and the pages reflected an old base; the address history on the profile did not suggest that. We checked whether the fourteen neighbourhoods were where the company's jobs actually were, which would justify the pages; the reviews and the profile did not support that either. We checked whether the home city was covered by the home page itself; it was mentioned in the footer address and nowhere else. We separated this finding from the JavaScript rendering problem, which would have hidden any page, so that fixing one did not get mistaken for fixing the other.
The fix
The proposal's demo added a page for the company's own city and pages for the county around it, each with real local substance: the kinds of homes and doors common there, the neighbourhoods served, the response time from the company's base, and the reviews that mention the area. The far-side neighbourhood pages were kept only where the company could show completed work, and the whole site was rebuilt to serve its content as HTML so that any location page could actually be read by a crawler.
How to check your own site for this
List your location pages and put your own address next to the list. If the city and county you are based in are missing, add them first; they are the pages you can win. For every other location page, ask whether you can name a completed job, a review or a reason a customer there would choose you over the company down their street. If you cannot, the page is a long shot and may be worth merging into a service-area page rather than keeping as a thin standalone.
Related questions
Only for the ones it can genuinely serve and show work in, and always starting with where it is based. A page with real local substance for the home city outperforms a dozen thin pages for distant neighbourhoods.
Because its address, its Google Business Profile, its reviews and its service history all point there. Search engines weigh that consistency, and a page for the home area lines up with it.
No. The rendering problem hid every page from crawlers; this finding is about which pages existed at all. Both were on the same site, and the fix addressed both, but they are separate mistakes.
Local facts a customer would recognize: the homes and door types common there, response time from your base, neighbourhoods named, reviews from that area, and a completed job or two. A swapped city name in a template is not that.
It kept the ones where the company could show completed work and merged the rest into a service-area page, so nothing that earned a click was thrown away.
an anonymized finding from a real proposal audit; the business is described by type only; SearchPod sells the services that fix findings like this.
Want your site audited the same way?
Get a free, no-obligation proposal within one business day. We look at your site and your market and tell you plainly what we would do, and what we would not.
Get your free proposal