Local SEO

Town pages that help customers, and the ones Google treats as doorways

Most trades businesses with city pages have no idea which side of Google's doorway-page line they're on. This guide runs you through the town-swap audit, the six signals Google uses to judge legitimacy, and what happens to your whole domain if it gets it wrong.

What Google's Doorway Page Policy Actually Says

Google's spam policies define doorway pages as: "Sites or pages created to rank for specific, similar queries. They lead users to intermediate pages that are not as useful as the final destination."

Google applies four diagnostic questions when reviewing a suspect page. The phrase that matters is created to rank for specific, similar queries — if your Manchester page and your Birmingham page would read identically after a find-and-replace on the city name, that is exactly what this policy describes. It has been in Google's guidelines for over two decades. Since the 2024 core update, enforcement is more algorithmic, meaning your rankings can drop before you receive any warning.

  • Are these pages created for search engines, or do they also serve a user who lands on them directly?
  • Are the pages similar enough in topic that merging them would better serve users?
  • Do the pages duplicate aggregated content already on the site without adding value?
  • Do these pages exist as an island — difficult to navigate to from the rest of the site?

The Clone Test: How to Tell If Your City Pages Are Doorway Risk

Run three checks on every city page you have.

Check 1: Swap the town name and read the page aloud. Change every mention of "Leeds" to "Bristol" and read it back. If it reads identically — same opening sentence, same service description, same bullet points — it fails. Functionally identical means a reader in Bristol would gain exactly the same information and the same value as a reader in Leeds. A local phone number and a Google Maps embed do not change that assessment.

Check 2: Ask what a resident of that town learns that they wouldn't learn from your homepage. If the answer is "nothing except that you serve the area," the page has no unique value. A legitimate local page tells people something specific: which postcodes you cover, what the typical job looks like there, local context that changes the service description. Without that, you've built a thin coverage page, not a local page.

Check 3: Check how the page connects to the rest of your site. Doorway pages typically live in isolation — visible in a sitemap or footer, but linked from no body content. If your city page can only be found via sitemap or footer navigation, and no article or service page links to it naturally, it is structurally behaving like a doorway. Genuine local pages get linked to from related content because readers benefit from them.

If a page fails any two of these three checks, treat it as a doorway risk. Rewrite it with real local content or redirect it.

The Six Signals Google Uses to Distinguish Legitimate Local Pages

A legitimate local page does not need to be long. It needs to be specific. These are the six signals that separate a page that earns its ranking from one that is merely occupying space.

  • **Unique local content** — information specific to that area that would not appear on a generic national page. Vague references to 'serving the area' do not meet this bar.
  • **Area-specific service context** — the service description reflects conditions real in that location: housing stock, infrastructure, typical job types. If it applies equally anywhere in the country, it is not local content.
  • **Genuine NAP (name, address, phone)** — matching your Google Business Profile and directory listings exactly. A virtual address or rotating tracking number signals doorway intent, not local presence.
  • **Neighbourhood and suburb coverage** — going one level deeper than the town. A Leeds page that names Headingley, Horsforth, and Morley and says something true about each is demonstrably more specific than one that says 'Leeds and surrounding areas.'
  • **Locally relevant structured markup** — a LocalBusiness schema block with a serviceArea tied to that specific town or postcode area, telling Google the page was built intentionally for that location.
  • **Distinct internal link context** — other pages on your site link here because the content is genuinely relevant to what those pages discuss, not just because the page appears in a sitemap.

What Counts as 'Unique Local Content' for a Plumber or Heating Engineer

Here is what real differentiation looks like in practice, not in theory.

Postcodes and neighbourhoods, specifically named. "We cover LS6, LS7, and LS16 — Headingley, Chapel Allerton, and Cookridge" is local content. "We serve Leeds and the surrounding area" is not. If you cannot name the postcodes you actually cover, the page reads as generic because it is.

Local housing stock context. Much of inner Manchester is Victorian terraced housing with older gravity-fed heating systems and 15mm copper pipework. A heating engineer who mentions gravity-to-sealed system conversions and re-piping work in pre-1980 properties is writing something true about that area. Swap it to a Guildford page and it reads wrong — which is precisely the town-swap test.

Permit and regulatory context. In conservation areas or near waterways, additional permissions are sometimes required for drainage or external works. If that applies where you work, saying so is both useful and locally distinct.

Hard water versus soft water. The South East has significantly harder water than the North West. For a boiler engineer that means different maintenance intervals, scale inhibitor fitment, and typical boiler lifespans. Content reflecting that cannot be swapped town-to-town without reading wrong.

Local job volume. If customers in that area have left you Google reviews, referencing the volume of local work completed adds verifiable proof — provided the figures are accurate. Do not invent job counts or customer names.

The Schema Piece: LocalBusiness with serviceArea vs. a Blank Page

A local page with no structured markup asks Google to infer everything from text alone. Schema makes the claim explicit and machine-readable — which matters when Google is choosing between several trades pages for a postcode search.

The correct type for a trades local page is LocalBusiness, with an areaServed property set to the specific city, borough, or postcode area the page covers. For pages covering multiple areas, areaServed accepts an array. You can also define coverage using a GeoCircle — a centre point and radius — if your coverage is better described geographically than by named places.

The address block should match your Google Business Profile address exactly. Any mismatch between schema markup and your GBP listing is a consistency signal Google notices.

Markup cannot compensate for thin content. A correctly marked-up page with two paragraphs of generic text is still a thin page. What markup does is ensure you get credit for making a local claim when your content substantiates it. If your city pages have substantive content and no schema, adding markup quickly removes one competitive disadvantage.

What Happens If Google Tags Your City Pages as Doorways

If Google determines your city pages are doorways, the consequences are not limited to those individual pages. A manual action for doorway pages affects the whole domain. Your homepage, your service pages, and your blog all lose visibility while the action stands — not just the pages that triggered it.

Algorithmic demotions work the same way. Google's systems evaluate quality signals across a domain, not page by page. A site with fifty thin city pages can see its strongest pages lose ranking as collateral damage from the low-quality signals those pages generate.

Recovering is slower than getting it right the first time. Manual action reconsiderations typically take weeks. Algorithmic recoveries after a content quality update can take months.

If you are unsure whether your existing city pages are at risk, consult an SEO professional who works with local service businesses before you create more of them. Adding pages to a site that already has a doorway problem makes it worse, not better. The cost of doing it right once is always lower than the cost of a recovery.

Frequently asked

What is the difference between a doorway page and a legitimate local landing page?

A doorway page is created primarily to rank for a specific search query — typically a 'service in town' phrase — with little or no content that is useful to someone who actually lands on it. A legitimate local landing page serves real users in that area: it names specific neighbourhoods, describes local job types, and provides information a local resident could act on.

The simplest test is the town-swap test: change the city name and read the page. If it reads identically to another city's page, it is a doorway risk.

Does Google penalise city pages that share the same template?

Using a shared template is not by itself the problem. The issue is whether the populated content is functionally identical across pages. If only the town name changes and everything else is the same, Google's spam policies describe that as a doorway page. If the template is populated with genuinely different local content for each area, the shared structure is not a problem.

What schema markup should a local service area page use?

Use the LocalBusiness schema type with an areaServed property set to the specific city, borough, or postcode area the page covers. The address block should match your Google Business Profile exactly. For pages covering multiple areas, areaServed accepts an array of locations. This markup tells Google explicitly which area the page claims to serve.

Can a doorway page problem affect my homepage and service pages?

Yes. A manual action for doorway pages applies to the whole domain, not to individual pages. Algorithmic quality signals also operate at domain level, so a large number of thin city pages can depress rankings for your homepage and service pages as collateral damage. Fix existing thin pages before adding new ones.

How do I fix city pages that might be doorways?

Start with the town-swap test: change the city name and see if the page reads identically to another. For pages that fail, rewrite them with genuine local content — specific postcodes, housing stock context, local service detail — or redirect them to a page that genuinely serves that area. Adding more template text does not fix thin content. Google evaluates substance, not length.

Not sure which side of the line your city pages are on?

Before you commission more local pages, get a straight answer on what you've already built. Book a free call and we'll tell you exactly what's working and what's at risk.