Every article about location pages tells you how to rank them. Almost none mention the step before that: Google has to index them at all, and in the last few years it has become brutal about declining city pages in bulk. I have built and indexed more than 90 of them for one locksmith business cluster, tracked URL by URL, so this guide starts where the ranking advice should: getting the pages stored.
The short answer
Most location pages do not rank because Google never indexed them, and Google declines templated city pages in bulk because only the place name changes between them. Before any ranking work, each page has to clear one test: cover the town name and you should still be able to tell which town the page is about. Pages that pass carry genuinely local detail, the real coverage areas and response times, and they go live in waves with proper internal links instead of one bulk dump. The 90+ tracked pages behind this guide reached 72 percent indexed on the flagship site exactly that way.
Why does Google decline location pages in bulk?
A set of location pages is, structurally, the exact thing Google’s quality systems were built to catch: many URLs on one template where only the place name changes. Google samples a few, recognizes the pattern, and files the rest under Crawled, currently not indexed, or never fetches them at all and leaves them in Discovered.
The owners I hear from usually built twenty city pages in a weekend, watched three get indexed, and concluded Google hates local businesses. Google does not hate local businesses. It declines interchangeable pages, and a find-and-replace city template is interchangeable by definition.
What separates the pages that index
The locksmith cluster in my case studies runs more than 90 town and service pages, with the flagship site at 72 percent indexed and climbing. What made those pages clear the bar was not a trick. Each page carries content that only makes sense for its town: the areas and estates actually covered, response times from the real base of operations, the services that town actually orders, and photography that is not the same stock image on every page.
The test I apply before publishing any location page: cover the town name and read it. If you cannot tell which town the page is about, neither can Google, and it will not store the page. That is the honest version of every “unique content” bullet point in the usual advice.
Structure carries the rest. The pages interlink as a real hierarchy, service pages link to towns and towns link back, everything sits in the sitemap, and nothing hides five clicks deep. Google reads that architecture as a statement that these pages are the business, not an SEO bolt-on.
The two mistakes that poison the whole set
Faking presence. Pages claiming offices in cities where the business has none get flagged by users, undermine trust signals, and put every other page on the domain under suspicion. A service-area business should say plainly that it travels to the town. That honesty costs nothing and survives every update.
Publishing the whole set at once with no support. Fifty new templated URLs appearing in one day, linked from nowhere, is the exact shape of the catalogue problem stores have. Publish in waves, link each wave properly, and submit the priority towns by hand rather than pressing Request Indexing on everything.
Getting an existing set unstuck
If your location pages already sit unindexed, the order of operations is the same one I run on client jobs: fix the pages that matter first, the towns where the business actually wins work. Rewrite those to pass the cover-the-name test, wire them into navigation, then submit them individually and track each one. The long tail of towns follows as the site’s standing improves, on the timelines covered in how long indexing takes.
Building sets like this is also work I do end to end: the locksmith cluster’s pages, design system, and indexing all came from the same desk, which is why the builds page and the case studies overlap.
If your location pages are stuck, send me the site. I will tell you whether it is the template, the structure, or the rollout, free, usually within a day. No obligation.
Quick answers
How many location pages should I publish at once?
In waves, not in bulk. Publishing hundreds of templated town pages in one push looks like spam and gets sampled accordingly. Smaller batches of genuinely localized pages, indexed and proven before the next batch, is the pattern that worked across 90+ pages.
Do location pages need unique content for every town?
Each page has to pass one test: if you cover the town name, can you still tell which town the page is about? Swapping the place name into the same paragraph fails that test, and Google declines those pages in bulk.