Borough Pages That Rank: Location Pages After Google's 2026 Spam Updates

Every London local SEO audit I run eventually reaches the same temptation. London has thirty-two boroughs plus the City, hundreds of neighbourhoods and an almost unlimited supply of postcodes. Somebody on the team realises you could generate a page for each one in an afternoon.

You could. In 2026 it is also the easiest way to make Google's spam systems notice you. Here is what Google has said, what the 2026 update calendar looks like, and the line I draw between a useful borough page and a doorway.

Which spam updates did Google run in 2026?

The Search Status Dashboard lists a March 2026 spam update, a June update, an August update and a September update. The March one started on 24 March and the dashboard shows it completing in under twenty hours. June began on 24 June and ran just over two days, August began on 18 August and ran about two days and sixteen hours, and the September entry is dated 24 September.

Source: Google Search Status Dashboard, Ranking history. Google does not publish a list of exactly what each update caught, so anyone telling you precisely which tactic a given spam update targeted is guessing from patterns. What is not guesswork is the policy those updates enforce.

What does Google say about creating pages for every variation?

Google says creating separate content for every possible search variation, primarily to manipulate rankings, violates its scaled content abuse spam policy. The wording is in its guide to optimising for generative AI features, and it applies equally to classic Search. It adds that this is also an ineffective long-term strategy, because a high quantity of pages does not make a website higher quality or more relevant.

Read that against a site with thirty-three near-identical borough pages and the problem is obvious. The same paragraph, the borough name swapped, a map pin and a call button. That is the pattern the policy is written for, and the fact that the pages are individually tidy does not help.

Google's spam policies also cover doorway abuse, which is the older name for the same instinct: many pages that exist to funnel searchers to one destination rather than to serve them. A set of cloned location pages can trip both.

So are location pages a bad idea?

No. A location page is legitimate when the business genuinely serves that place and the page tells the reader something specific to it. The policy targets scale used to manipulate, not geography. A plumber serving Ealing deserves a page about plumbing in Ealing. A plumber who has never worked in Ealing does not.

My own Ealing and Uxbridge pages exist because those are places I can credibly speak about, and I would not add a third without the same test. The honest answer to 'how many borough pages should I have?' is 'as many as you can write something true about, and not one more'.

What makes a borough page worth ranking?

A page worth ranking contains information a competitor could not have written without doing the work. Google's guidance on helpful content asks whether the page offers original information and substantial value, and that is the standard I apply.

• Real jobs. Describe actual work in the borough, with the permission of the client, rather than 'we offer services in Hackney'.
• Local practicalities. Parking restrictions, controlled parking zones, building access, listed property, congestion considerations for trades. These are facts that vary by place.
• Local people and proof. Reviews from customers in that borough, named staff who cover it, photographs taken there.
• A clear service list specific to the area, not the global list with the place name stapled on.
• Honest limits. If you only cover part of a borough, say so. Specificity builds trust with readers and with Google.

What about AI-generated location pages?

Google says content produced with generative AI tools must still meet Search Essentials and the spam policies, and that it should not simply recycle what others have said or what an AI model could easily produce. The tool is not the issue. The output is.

AI is genuinely useful for a borough page, and I use it. It is good at structuring, tidying and drafting from material you supply: your notes from a job, your photos' captions, your knowledge of parking in the area. It is terrible at inventing that material. An AI model asked to write 'electrician in Camden' with no inputs will produce text that is true of every borough and therefore useless in every one.

Does the site reputation policy affect London local businesses?

Possibly, if you buy or host third-party content on a trusted site to borrow its reputation. On 28 August 2026 Google announced an update to its site reputation policy, which targets third-party content published on a trusted website just to exploit that site's good reputation. The change adjusts enforcement within the European Economic Area, and the United Kingdom is outside it.

For a London business that means a manual action under the policy still works as before for UK searchers: it directly affects results for the portion of the site affected, and the rest of the site is not touched. This matters to local link building. A paid 'sponsored' section on a respectable local publication that exists only to rank is exactly what the policy describes. Earned local coverage, genuine sponsorships and real partnerships are a different thing entirely.

What about areas I serve but have no page for?

Cover them inside one strong service-area section rather than giving each its own thin page. A business can genuinely serve a dozen London boroughs without having a dozen things to say about each. For those, an honest areas page with a short, specific note on how the service works across them is better than a dozen pages that say the same thing.

• Group by how you actually work. North, south, east and west London, or by the bases and routes you really run, tells a reader more than an alphabetical list of boroughs.
• Add a sentence of truth per area. Typical response time, the type of property you meet most, a constraint you plan for. If you cannot add one, the area belongs in the list, not on a page.
• Match the Business Profile. Set the service areas on the profile to the same places, within Google's guidance that the area should not stretch beyond about two hours of driving.
• Do not list every postcode. A page that is a wall of postcodes is the clearest doorway signal there is, and it helps nobody.
• Promote areas to their own page only when they earn it. A borough that generates real enquiries, real reviews and real jobs has the material for a real page.

This is how I structure the service pages on this site: one page per service, with a coverage section that is honest about where the work happens. It is a smaller site than the programmatic version, and a far easier one for a search system to trust.

How should I audit the location pages I already have?

1. List every location page and note whether you genuinely operate in that place.
2. Compare the pages pairwise. If more than half the text is shared between two borough pages, they are one page in costume.
3. Read each as a customer from that borough. Does it tell them anything they could not guess from the page title?
4. Merge or remove the weakest. Redirect them to a stronger parent page rather than leaving thin pages live. Google says deletion is a last resort for salvageable content, but thin duplicates are the case it has in mind.
5. Rewrite the survivors with real local material, then add genuine internal links between related areas.

If you do this and the site is smaller afterwards, that is not a loss. A site with fewer, better pages is one Google can be confident about, and confidence is what ranking runs on. It is also the same discipline I describe on the service page: one page per service, one page per area you can defend.