Pages for each town you serve: when they help and when they're doorway pages

A page for a town you serve is fine when it tells someone in that town something your main service page doesn't. Twenty copies of one page with "Leeds" swapped for "Bradford", "Wakefield" and "Harrogate" are a different thing: Google's spam policies name "multiple domain names or pages targeted at specific regions or cities that funnel users to one page" as an example of doorway abuse. Google doesn't set a number of pages that is allowed. The line is whether each page has its own reason to exist.

What Google actually says

The doorway abuse section of Google's spam policies describes pages "created to rank for specific, similar search queries" that lead users to intermediate pages that aren't as useful as the final destination. Two of its examples fit town pages directly: pages for specific regions or cities that funnel users to one page, and "substantially similar pages that are closer to search results than a clearly defined, browseable hierarchy".

Google's guide to helpful content adds questions to ask yourself, including "Is the content primarily made to attract visits from search engines?" and "Are you using extensive automation to produce content on many topics?" A batch of town pages generated from one template, made to catch town-name searches, answers yes to the first.

Google says sites that break its spam policies may rank lower or not appear in results at all. A quieter outcome needs no policy at all: near-identical pages can be crawled and left out of the index, which the indexing statuses guide explains under "Crawled - currently not indexed".

A decision rule for each town

Ask three questions about each town before creating a page.

1. Do you have something to say that is true only there? Jobs you've done in the town, local rules or permits, the housing stock you meet, travel time and call-out terms, reviews from customers there.
2. Do people search for the service with that town's name? Search Console's Performance report shows which queries with town names already bring impressions. A town nobody searches for together with your service doesn't need its own page.
3. Can you keep the page accurate? A page that says "we fit kitchens in Ripon" needs updating when you stop going there.

Then decide:

Local Search Forum moderators give a similar answer to owners asking how many town pages they're allowed: there is no limit, but pages should not be copies with the name changed, and small neighboring towns can share one page that names each of them.

What goes on a town page

A page that stands on its own has things on it that couldn't be copied to the next town without being false. A field set to work from:

• The service in that place. "Boiler servicing in Harrogate" with what's specific: older stone houses with back boilers, a conservation area that affects flue positions, if those are true.
• Work done there. Two or three recent jobs with a street name or area, a sentence on the problem and what you did, and your own photos. Ask customers before naming anything that identifies them.
• Practical terms. Whether there's a call-out charge, typical lead time for that area, which days you work there.
• Reviews from customers in that town, quoted with permission or linked to your Google reviews.
• Local details the customer needs, such as the council's permit page for skips or parking, if it applies to your work.
• Contact. The same phone number and business name as everywhere else.

What doesn't make a page distinct: a paragraph about the town's history copied from an encyclopedia, a list of nearby postcodes, the same text with synonyms swapped, or a map embed on its own.

Write fewer pages and make each one real. Five town pages with local material and a clear areas page give customers more than twenty templates.

Structure the pages so they're easy to browse

Google's doorway example contrasts pages "closer to search results" with "a clearly defined, browseable hierarchy". In practice:

• One Areas we cover page that lists every town you serve and links to the town pages that exist.
• Each town page links back to the areas page and to the relevant service pages.
• Town pages are linked from your menu or areas page, not only listed in the sitemap. A page that only exists in the sitemap gives visitors no way to reach it.

Avoid a page for every service in every town ("boiler repair Ripon", "boiler servicing Ripon", "boiler installation Ripon"). That multiplies the near-duplicates. A town page can cover the services you offer there, and link to each service page for detail.

Your Business Profile is separate

Town pages and your Google Business Profile do different jobs. Google ranks local map results on relevance, distance and prominence, and a service-area business sets its areas in the profile itself; Google's local ranking page doesn't say that town pages on your site extend where you appear on the map. The Google Maps 3-pack guide covers that side. A town page is for the ordinary search results and for the person from that town reading it; it doesn't move your map pin.

If you already have a set of near-identical pages

Don't delete them all at once. Check the Pages tab of Search Console's Performance report for each one:

• Pages with clicks: rewrite them with local material, starting with the ones bringing the most.
• Pages with impressions but no clicks: decide using the rule above; rewrite or merge.
• Pages with no impressions over 16 months: merge into the regional or areas page and redirect the old URL there with a 301.

Checking a large set

On a site with ten town pages, reading them side by side shows the problem. With dozens, a crawler helps. Semrush's Site Audit has a check called "Pages with duplicate content issues" for pages whose content is highly similar, according to its issues list. That flags the obvious templates; it can't tell you whether a page is useful to someone in that town. That part is still your judgment against the field set above.