Location Page Generation at Scale

The right build level for a location page set depends on how much the markets actually differ, not on how many cities there are. Ivan Sp builds multi-city page sets at three different effort levels, matched to how much a market actually differs. Choosing the wrong level either wastes budget on unnecessary research or produces duplicate content that Google declines to rank.

Three Build Levels

Multi-location content gets built one of three ways:

Geographic adaptation. A proven page runs in a second city. The city name changes throughout while HTML, button code, URLs, and wording stay intact.
Full location build. Each city receives its own keyword research, because search behaviour and competition genuinely differ.
Regional weaving. One existing page absorbs references to many cities and regions, extending its reach without new pages.

Most clients need a mix. A primary market earns a full build, secondary cities receive adaptations, and outlying regions get woven into an existing page.

Adaptation Still Requires Judgment

A geographic adaptation is a copy-edit rather than a rewrite, and it is not a find-and-replace. One security company page moved from Sherwood Park to Leduc. The original text said the monitoring centre sat “right in the area,” which had to become the actual nearby city name for the new location to make sense.

Every adaptation gets read for statements that were true of the original city and false of the new one. Distances, neighbouring communities, and service coverage claims are the usual offenders.

What Has to Differ on a Generated City Page

One directory build covered roughly 1,000 city pages across several service categories. Six elements were required to differ genuinely per page:

City-specific introductions referencing real local landmarks and context, rather than interchangeable filler
Long-tail keyword variants combining the service, the city, and the neighbourhood
Themes summarized from real customer reviews for businesses in that city
Questions and answers specific to that city and that service
LocalBusiness schema markup written per listing rather than per template
Internal links to related services and to nearby cities

Grounding Local Claims in Real Local Facts

Inserting a city name into generic advice is the most common location page failure. One renovation page restated general guidance with “Calgary” added and no actual local information attached.

The correction referenced the City of Calgary permitting process, which is a checkable civic fact rather than an invented claim. Generated city pages get grounded the same way, in permits, regulations, climate, or geography that genuinely differ by location.

Local Intent Gets Flagged Separately

Search intent alone cannot separate “implant cost” from “implant cost Edmonton.” Both are informational, and they need different pages.

Every row in a location map therefore carries a separate local flag alongside its intent type. Without it, the two queries get merged into one page that serves neither properly.

The Three Build Levels

Level one, templated: One structure with location fields substituted. Suitable only where markets barely differ.
Level two, adapted: Templated structure with genuinely researched local content per market.
Level three, researched: Per-market keyword research, local context, and questions gathered individually.
What decides the level: How much search demand, competition, and customer questions differ by city.
Local grounding: Real landmarks, neighbourhoods, and service boundaries rather than invented colour.
Local intent flags: Queries carrying local intent, flagged separately from national ones.
The duplication risk: Pages differing only by a city name, which are filed as near-duplicates.
The honest constraint: Level one is rarely correct, and it is what most location page sets actually use.

Test Two of Your Own Location Pages

Ivan Sp suggests a test that settles the question in five minutes.

Open two of your location pages side by side.
Cover the city name in the heading of each.
Read both and try to tell which city each one is about.
Count the sentences that mention anything genuinely specific to that place.

If you cannot tell the pages apart with the city name covered, neither can Google. Fewer than four genuinely local sentences usually means the page will not index.

Where the Standard Location Page Advice Breaks Down

How many of your target cities could you write something genuinely local about?

The usual advice: Build a location page for every city you can name, since more geographic coverage means more local traffic.
What holds up in practice: Coverage without difference produces near-duplicates that never get indexed. The correct page count follows from how many markets you can genuinely research, which is usually far fewer than the number of cities you serve.

Picture a build generating pages for eighty cities from one template with a name variable. Coverage looks comprehensive on a map.

Google indexes a handful. The rest differ by one word, and the business now has seventy-odd pages consuming crawl budget and returning nothing.

I set the page count from research capacity rather than from geography. Twelve researched markets outperform eighty templated ones.

Eighty thin location pages cost the same to build as twelve good ones. Worse, they consume the crawl budget the good pages needed.

A location page that says nothing local is a page a searcher in that city can tell was not written for them. Google reaches the same conclusion faster.

Four Things Commonly Assumed About Location Pages

Which of these describes your location page plan?

I meet these four assumptions on most multi-city builds.

Commonly assumed	What actually holds
More cities means more coverage.	Pages differing only by a city name are filed as near-duplicates. Coverage requires genuine difference per market.
Local colour can be added generically.	Invented local detail is fabrication, and readers in that city notice immediately. Real landmarks and boundaries are the only usable material.
One keyword research pass covers every city.	Demand, competition, and phrasing differ by market. A term dominating in one city can be irrelevant in another.
Templated pages are always the cheap option.	Templated pages that never index cost the full build and return nothing. Fewer researched pages cost less per indexed page.
Every service area needs its own page.	Service area coverage can be stated on one page. A separate page is warranted only where the market genuinely differs.

The number of location pages worth building is a research capacity question. Answering it honestly is what separates a page set that indexes from one that does not.

A Worked Example: Choosing a Build Level

Consider three city sets assessed for build level. The assessment below is illustrative, written to show how the level is chosen. No client engagement is described here.

City set	How much markets differ	Correct build level
Three metro suburbs, same demand and competition	Barely	One page covering the service area
Eight cities, similar demand, different competitors	Moderately	Level two, adapted per market
Fifteen cities across two provinces	Substantially	Level three, researched individually
Eighty cities with no local presence	Unknown, and unresearched	Do not build
Pages that would index	Varies by level	High at levels two and three

I assess difference before choosing a level. The fourth row is the most common situation and the answer nobody wants.

Building eighty templated location pages is opening eighty branch offices with the same photo in the window. Anyone walking past two of them notices.

The first row is worth stating. Three suburbs with identical demand need one page, and building three creates competition between them.

How a Location Build Runs

I assess market difference before choosing a build level or a page count.

List every market under consideration and record demand, competition, and local phrasing per market.
Compare markets against each other, since the differences decide the build level.
Choose the build level from how much the markets genuinely differ.
Set the page count from research capacity rather than from the number of cities served.
Run keyword research separately for each market that earns its own page.
Collect real local context per market, including landmarks, neighbourhoods, and boundaries.
Prohibit invented local detail, since readers in that city recognise it immediately.
Flag queries carrying local intent separately from national ones.
Generate a sample of five pages and read them side by side before building the rest.
Check indexation per page after 28 days, since near-duplication shows up there first.

How This Engagement Is Scoped

I scope location builds by the number of markets researched rather than by cities served.

What arrives: A market difference assessment, a build level recommendation, a page count, and a sample set.
Typical duration: Six to twelve weeks, depending on market count and research depth.
What the client supplies: The market list, local knowledge, and template access.
Included: Market assessment, level selection, per-market research, generation, and indexation checks.
Not included: Inventing local detail, and building pages for markets that cannot be researched.
What changes the estimate: Markets in several regions, or a business with no local presence to draw on.
How it is quoted: After a short scoping call, once the market list is reviewed.

Tools and Primary Sources

The references below cover duplication and local behaviour. Each opens in a new tab.

Google spam policies defines scaled content abuse, which templated location sets commonly trip.
Consolidating duplicate URLs explains how near-identical pages are consolidated rather than indexed.
Google local ranking guidance states the factors applying independently in each local market.
Search Console Page Indexing report reports the near-duplicate statuses that reveal a failed location build.

Common Questions

How many location pages is too many?

The limit is set by real local differences rather than by a number. Forty cities where the business genuinely operates differently supports 40 pages, and 40 cities sharing one service area does not.

Do location pages need a physical address in each city?

Not for standard service pages. Google Business Profile listings do require a genuine presence, and claiming addresses that do not exist risks the listings themselves.

What about cities the business serves but has no presence in?

Regional weaving handles those. A service-area page mentioning travel distances and coverage is honest, where a dedicated city page implying a local office is not.

How many location pages should a business actually build?

As many markets as it can research properly. A smaller set of researched pages produces more indexed pages and more local visibility than a large templated set.

Discuss This Work

The first call is a free 30-minute consultation with no pitch attached. You receive an honest assessment of where the site stands and what can realistically be built.

Book a free 30-minute consultation