Local landing pages that are not duplicates

This article is the practical companion to regional SEO architecture, which covers how a site should be structured for places at all. Here the question is narrower: given that a page should exist, what has to be on it.

When a location page deserves to exist

I look for at least one genuine difference before agreeing to a page.

• Distinct intent — people search for the service differently in that market, or want a different combination of services.
• Distinct service context — the delivery model, timelines, regulations or logistics differ there.
• Distinct evidence — there is real work, real coverage or real presence in that place that can be shown.
• Distinct constraints — travel, licensing, coverage limits or capacity that a visitor needs to know before enquiring.

If none of those apply, the honest answer is one page covering the region, with the area described plainly. That is not a compromise; it concentrates the value of every link and every visit onto a page that can actually rank.

What gives a local page substance

The service, described for that market

Not a generic service description with a place name inserted. What the engagement looks like for a business there, what typically prompts it, and what the first step is.

Genuine regional knowledge

Anything you know because you work there and a national competitor does not. Be careful here: knowledge means specifics you can stand behind, not adjectives about a vibrant local business community. If you cannot support a claim about the market, leave it out. An empty claim is worse than a plain page.

Local proof and project evidence

Work you have actually done, described accurately, with any limitations stated. Where the evidence is measured rather than anecdotal, link to it — JMG Group keeps that on the Proof page rather than restating numbers on every page, which also keeps a single source of truth if a figure changes.

Service-area distinctions

State which areas are covered and, where relevant, how. A service-area business should be explicit about this. It answers a real question and it prevents enquiries you cannot serve.

FAQs that answer local questions

Only questions that are genuinely different because of the place: coverage, travel, timelines, availability. Repeating your national FAQs with a city name is padding, and if they are marked up as FAQ structured data, they are padding a search engine can see.

Avoiding doorway pages and cannibalisation

Two related failure modes, often present together.

A doorway page exists mainly to catch a search phrase and pass the visitor along without adding anything. A set of city pages generated from one template is the textbook local example, and search engines are explicit that they do not want them.

Cannibalisation is quieter. Two pages target the same question, so the site competes with itself: links split, and the engine selects one page — often not the one you would have chosen. The clean test is to write the one question each page answers in a single sentence. If two sentences are the same, you have one page's worth of content in two places.

The structural fix is the same as for any topical overlap: one page per distinct question, wired together deliberately. That is the argument in content clusters.

Linking up, down and across

A local page should never be a dead end.

• Up: to the national service page that defines the capability, so the local page inherits rather than duplicates it.
• Down: from the regional pillar to each supporting local page, so the cluster is crawlable without relying on search.
• Across: to the small number of sibling pages a visitor would plausibly want next, not to all of them.

This site runs that structure in the open: digital marketing in Kitchener-Waterloo is the pillar, with supporting pages such as web design in Kitchener and SEO company in Kitchener, each linking up to the national capability — website development and SEO and content architecture respectively.

Canonicals, sitemaps and indexability

The technical requirements are unremarkable, which is why they get skipped.

• Every location page carries a self-referencing canonical. Pointing a city page's canonical at the pillar tells search engines to ignore it.
• Each indexable page appears exactly once in the XML sitemap, generated from the same source that builds the navigation, so the two cannot disagree.
• Pages you would not want a searcher to land on should be removed, not hidden. Omitting a page from a sitemap does not stop it being found.
• Location pages are ordinary indexable pages; nothing about them justifies a noindex tag or a redirect to the pillar.

Connecting articles to commercial pages

An informational article and a location page do different jobs. The article explains how something works and earns trust; the location page states what the business offers and asks for the enquiry. Merging them produces a page that explains too much to convert and sells too hard to be trusted.

Keep them separate and link between them, as this series does back to digital marketing in Kitchener-Waterloo. If you want the current structure of your own location pages assessed, the free Business Growth Audit reviews structure, indexability and technical foundations, and the overview article for this series is local SEO in Kitchener-Waterloo.