Search
Can you build hundreds of location pages safely?
One template times fifty towns is the oldest SEO trick and now a named policy violation. What makes a generated page survive, and what it has to carry per town.
How MarketWar handles it
Five page patterns are generated from axes YOU supply — the engine only recombines your values and never fabricates data — with unique meta and structured data per page and explicit variation control, because the failure mode is not weak ranking but Google's scaled-content-abuse policy demoting the WHOLE domain. It emits page specs rather than raw HTML, so every generated page goes through the same renderer and the same checks as a hand-written one.
The oldest trick in local SEO is one template multiplied by every town you can name. It used to work. It now carries a specific risk that is worse than not ranking.
What changed
Google's scaled-content-abuse policy is aimed precisely at pages produced at volume that add nothing for the reader. The important detail is the scope of the consequence: it is a site-wide signal, not a per-page one. Fifty thin town pages do not simply fail to rank — they can drag down the pages that were working.
So the question is not "can I generate pages". It is "can I generate pages that each carry something only I can say".
What a town page has to carry
Something true of that town and not the others:
- the areas you actually cover from there, and the ones you do not,
- travel time, call-out charge, or the fact that you charge the same anywhere,
- a job you did there, described,
- something local that affects the work — parking, access, the age of the housing stock, a council rule.
If a sentence works for every town with the name swapped, it is doing nothing. That is the test, and it is the same test the answer pages in this cluster are held to: a page is allowed to exist when it says something a competitor could not copy without doing the work.
What the generator does and does not do
Five patterns — location, service-area, comparison, industry and best-in-town — generated from the axes you supply. The engine recombines your values and never fabricates data, with unique meta and structured data per page and deliberate variation control rather than one paragraph reworded fifty times.
And it emits page specs, not raw HTML: slug, title, meta, schema, intro. Those go through the same renderer and the same checks as a hand-written page, which means a generated page cannot route around the title and description bounds, the claims check, or anything else the rest of the site is held to.
That is the structural reason this is safe to use: there is no separate, lower standard for a page because it was generated.
How many to build
Fewer than you want to. Most small businesses have five or ten areas they genuinely serve and can say something specific about, and that is the number of pages to build.
The honest version of this feature is usually a smaller output than the customer expected — and it is the version that does not put the rest of the site at risk.
Where the real local win is
For a single-location business, a page per town is rarely the biggest lever anyway. Being findable in your own town is mostly about the consistency of your business information and whether your own pages say specifically where you work.
The question to ask
Take any two pages a programmatic tool produced and read them side by side. What is different other than the place name?
If the answer is nothing, do not publish either, and do not blame the generator — it did what it was asked.
What this does not do
It cannot invent a reason for a town page to exist. If you do not serve that area, or you have nothing specific to say about it, the page is thin whatever the generator does — and thin at scale is the thing that gets a domain demoted rather than merely ignored.
Common questions
Is programmatic SEO still allowed?
Yes. What is not allowed is scaled content with nothing specific in it. The policy is aimed at pages produced at volume that add nothing, and the penalty applies to the domain rather than to the thin pages alone.
What makes a town page not thin?
Something true only of that town: the areas you actually cover, travel time, a job you did there, local pricing, the parking situation. If every sentence works for every town, you have one page fifty times.
How many should I build?
As many as you can say something specific about, which for most small businesses is far fewer than the generator could produce. Five real pages beat fifty templated ones, and they cost less to maintain.
Does it write the content for me?
It produces the page spec — slug, title, meta, schema, intro — by recombining the axis values you supply. It does not invent facts about a place, and a claim with no source behind it does not publish.
Related
Why your business does not show up for your own town
The six causes of local invisibility in the order they matter, starting with the one that outranks your website entirely and costs nothing to fix.
How do you publish AI content without inventing statistics?
AI writes a convincing statistic and a plausible citation with equal confidence. What an evidence classifier blocks, and what it lets through.
Why AI assistants never mention your business
Something decides which names an assistant returns for "a plumber near me". What it reads, and why most small business sites are invisible.