Skip to main content
Lead Generation Websites, Google Maps Ranking, WhatsApp Funnels, Ecommerce, SEO, Web DesignSpeed Optimization · Conversion Optimization · Monthly Lead Systems · AI AutomationLead Generation Websites, Google Maps Ranking, WhatsApp Funnels, Ecommerce, SEO, Web Design
November 20, 202611.20.26

Templated City Pages After a Spam Update: Prune, Merge or Rewrite?

Date your spam update drop, find the city pages that lost clicks, then keep, rewrite, merge or remove each one. A Search Console method with no promises.

Templated City Pages After a Spam Update: Prune, Merge or Rewrite?

This is the scaled content abuse local SEO question for any firm with dozens of service-plus-city pages: do Google's spam rules apply to them? Possibly, and only a page-by-page review can tell you. Google's policies target many pages made mainly to manipulate rankings, however they're made, and they list pages aimed at specific cities as an example of doorway abuse. Templated city pages sit close to both definitions, but they aren't a violation just because they exist. Below is a way to sort each page into keep, rewrite, merge or remove, using only what I could confirm in Google's own documents as of 6 November 2026.

I won't promise a recovery, and I can't tell you which update hit your site. Nobody outside Google can confirm that for one site. You can date the drop, find the pages that lost clicks and make an honest call on each one. For the wider picture of how search, answer engines and AI results fit together, start with our SEO, AEO and GEO visibility guide.

What Google's policies say about city pages

Google defines scaled content abuse as "many pages are generated for the primary purpose of manipulating search rankings and not helping users", and says it applies "no matter how it's created". So a hand-written template repeated many times isn't exempt just because no AI was involved. Its examples include using generative AI tools to produce many pages without adding value for users, and creating many pages whose content makes little sense to a reader but contains search keywords.

The doorway abuse section is the one that names locations. It lists "having multiple domain names or pages targeted at specific regions or cities that funnel users to one page" and "creating substantially similar pages that are closer to search results than a clearly defined, browseable hierarchy". Google's spam policies page shows a last-updated date of 28 August 2026.

Read those lines closely. A page about plumbing in Thane isn't a doorway because it names a city. Google's wording turns on purpose and value. Does the page help a real visitor, or does it exist to catch a query and pass the visitor along? Google makes that call, and I can't say where it draws the line for your pages. Its helpful-content questions show what it looks at, including "Does the content provide substantial value when compared to other pages in search results?" and "Are you using extensive automation to produce content on many topics?"

Confirm the date of your drop first

Start with the calendar, not the pages. Google's Search Status Dashboard lists the September 2026 spam update. Google released it on 24 September 2026 at 09:15 US Pacific time, said it applies "globally and to all languages", and noted that the rollout could take up to two weeks. The final entry says the rollout was complete as of 8 October 2026.

That window matters. A drop that starts well outside it isn't explained by this update on timing alone. Say, hypothetically, a site's clicks fall on 26 October. Google had already marked the rollout complete, so I wouldn't blame the September update. Other causes stay on the table: a different update, a site change, seasonality or a reporting glitch. Google's guide to debugging traffic drops lists all of those next to algorithm updates and points you to the Search Console Data Anomalies page.

The same Ranking history lists other 2026 changes, using the dates the dashboard shows: spam updates starting 24 March, 24 June, 18 August and 24 September, and core updates starting 27 March and 21 May. A drop that begins on one of those dates points to that update instead. Even a perfect date match is only correlation, because the dashboard says nothing about which kinds of pages an update affected. If you read practitioner commentary tying an update to templated local-service pages, treat it as an observation, not a confirmed cause.

Key figures from Google's own records (as of 6 November 2026)

Find which pages lost the clicks

Search Console can show you which pages lost clicks in about 30 minutes. Google's traffic-drop guide recommends comparing the drop period with a similar period, then sorting the Pages table by clicks lost.

  1. In Search Console, open Performance, then Search results.
  2. Set the date filter to Last 16 months to rule out a yearly pattern. Then use the Compare tab to set a period after the drop against a period of equal length before it.
  3. Open the Pages table and select Clicks Difference, so the pages that lost the most traffic come first.
  4. Add a Page filter with "URLs containing" and your location path, such as /locations/, to separate city pages from everything else.
  5. Export the table and note the shape of the drop: the whole site, a group of pages or one page.

Google says a site-wide drop calls for the Page indexing report, and a drop in a group of pages calls for the URL Inspection tool on a few of them. Here's a hypothetical example. A plumbing firm has 60 pages of the form "plumber in [area]". The export shows 45 of its 50 biggest click losses are those pages, while the homepage and three service pages barely moved. That points at the page set, not the whole site. It still doesn't prove why.

Test each page for uniqueness

Open the worst-hit pages one at a time and run this checklist. It's my own working test, not a Google rule, built from the policy wording above.

CheckPasses whenRed flag
Swap testReplacing the city name with another would make the page wrongThe page reads the same for any city
Facts only this page can stateIt describes how you really serve that area: who covers it, what you have done there, what customers there askThe details are generic, borrowed or invented
Reason to existA visitor from that area would pick this page over your main service pageIt repeats the service page with a city name dropped in
NavigationIt sits in your normal menu or an area hub that people can browseVisitors only reach it from search results or a sitemap
FunnelIt answers the visitor's question and offers its own next stepIts main job is to push visitors to one other page
Real serviceYou actually serve that placeYou don't, or you only want the keyword

Count the red flags on each page. Two or more, and I'd treat the page as a merge or removal candidate. Zero or one makes it a keep or rewrite candidate. The cut-off is my judgement, so adjust it to your business.

Not sure which of your city pages carry real local value? We can walk through your page set with you and sort it.

Audit my location pages

Keep, rewrite, merge or remove

Every page ends up in one of four outcomes. What decides it is whether the page is useful to a real visitor, not what you hope it does for rankings.

OutcomeUse it whenWhat to do
KeepYou serve the area and the page holds facts only it can stateLeave it, link it from your menu or an area hub and check it is indexed
RewriteYou serve the area but the page is a templateAdd specifics you can verify, such as which team covers the area, work you have done and questions customers there ask. Don't invent anything
MergeNeighbouring pages say the same thingCombine them into one stronger page, then 301 redirect each retired URL to it
RemoveYou don't serve the place, or the page has no use to a visitorReturn a 404 or 410, or add noindex, and remove its internal links and sitemap entry

For merges, Google's guide to consolidating duplicate URLs ranks redirects first among its signals and calls them "a strong signal that the target of the redirect should become canonical". The rel="canonical" link is also a strong signal. Google says it doesn't recommend noindex for choosing a canonical page within a site, "because it will completely block the page from Search". Redirect only to the page that genuinely replaces the old one, and update your internal links and sitemap so they point to the new URL.

For removal, Google's scaled-content section says that if you host such content you should exclude it from Search. Google says URLs that return a 4xx status such as 404 or 410 aren't indexed, and ones already indexed are removed. A noindex tag only works if the page stays crawlable, and Google says it may take months for Googlebot to revisit a page. Expect some movement after the change, too. Google's traffic-drop guide says that when URLs change, a medium-sized site can take a few weeks for Google to notice, and larger sites longer.

Two more notes. If you run a service-area business, presenting your areas on Google Business Profile is a separate job, covered in our guide to Business Profile for service-area businesses in Mumbai. And for how location pages and internal links work when they are done properly, see our guide to building local SEO outside your core location. If your site template is what forces every city page to look identical, fixing it is a web design and build job, not a copywriting one.

What recovery looks like, and what it doesn't

Google gives no timeline for recovery, and no guarantee. Its spam-update guidance says that making changes "may help a site improve if our automated systems learn over a period of months that the site complies with our spam policies". Its traffic-drop guide adds that some changes take effect in days while others take several months.

  • Manual actions are separate. If the Manual actions report in Search Console lists an action, Google says to fix the issue on all affected pages and select Request Review. Fixing some pages doesn't earn a partial return.
  • An empty report is limited evidence. It tells you no manual action is listed. It doesn't tell you why your traffic moved, so keep using dates and page-group comparisons.
  • Lost pages don't equal lost enquiries. After pruning, track clicks and enquiries (calls, forms, WhatsApp messages) for the pages you kept, not the page count.
  • Recheck on a schedule. Repeat the Compare view monthly and keep a dated log of every change you made, so you can tell which change preceded which movement.

Watch: Analyzing drops in Google Search traffic - Google Search Console Training

A Google Search Central training video on analysing drops in Google Search traffic. Title and channel were verified through YouTube's metadata; I haven't checked it against this specific update.

Watch on YouTube: Analyzing drops in Google Search traffic - Google Search Console Training

How we would approach your page set

When someone brings us a set of city pages, we inventory every URL, classify each one with the checks above and agree the keep, rewrite, merge and remove list with the owner before touching anything. Then we rewrite or consolidate with redirects, fix internal links and sitemaps, and monitor the result in Search Console. We don't promise rankings. The outcome depends on Google's systems and your market.

Want a second pair of eyes on your service and location pages before you change anything?

Ask for a service-page and location-page review

Reference reading

Frequently Asked Questions

Are templated city pages against Google's spam policies?

Not automatically. Google's policies on scaled content abuse and doorway abuse turn on purpose and value, and its doorway examples include pages aimed at specific cities that funnel users to one page. A city page that gives a local visitor real, distinct information is a different case from a template with the city name swapped. Google decides, so audit page by page.

How do I know if the September 2026 spam update hit my site?

Compare your clicks before and after 24 September to 8 October 2026 in Search Console, then see which pages lost the most. A matching date and a concentrated drop in one page group are clues, not proof. Google's status page does not say which pages the update affected.

Should I delete or noindex thin city pages?

Decide page by page. Rewrite pages for areas you really serve, merge near-identical neighbours with 301 redirects, and remove or noindex pages with no use to a visitor. Google says noindex only works if the page stays crawlable, and recrawling can take months.

How long will recovery take after I fix my pages?

Google gives no timeline. It says changes may help if its automated systems learn over a period of months that your site complies with its spam policies. Anyone who promises a date or a result is guessing.

If my Manual actions report is empty, are my city pages fine?

No. An empty report means no manual action is listed for your site. Google's spam policies say it detects violations through automated systems as well as human review, so the report can't tell you why your traffic moved. Use the update dates and the page-group comparison instead.

Comments

Leave a Comment

Loading comments...