Skip to content
PreferiumJoin the waitlist

SEOGoogle

Google can lose faith in your whole site over mass-generated pages

John Mueller said on Bluesky that low-value programmatic pages can cost a site Google's trust at site level, and that deleting them does not undo it quickly. What that means if you publish templated pages at scale.

A model house wrapped in tangled white string stands on a table among stacks of blank paper, a large magnifying glass tilted toward it.

John Mueller’s September 2026 comments warn against publishing large sets of pages that add little value. Removing those pages may be necessary, but it does not establish how quickly Google will reassess the rest of the site.

When a template produces useful pages

Programmatic SEO means building pages from a template plus a list, instead of writing them one at a time. You have a page design — “Plumbers in ___” — and a list of two thousand towns. A script fills in the blank and publishes two thousand pages. Each one gets its own web address, and each one can, in principle, show up in Google for someone searching that town.

Nothing about that is against the rules. Job boards, property listings, currency converters and store locators are all built this way, and they’re genuinely useful, because each page carries information that only applies to that row: different jobs, different houses, different exchange rates.

The failure mode is when the rows don’t actually differ. The town changes, the sentence doesn’t. The template produces many URLs without giving each reader useful local information.

What Mueller said

Writing on Bluesky, Google Search Advocate John Mueller said programmatic SEO often produces a site that is spam, borderline spam or low quality — and when it does, Google’s systems may have “lost faith in your site providing good value to users” on the strength of those pages. He described recovery as something that takes time and significant effort to demonstrate value, and put it in the same category as coming back from a spam problem or a core update hit. Search Engine Roundtable reported the remarks on 7 September, linking his original post; Relevant Audience covered them separately.

Note what is absent. No page-count threshold. No recovery timeline. No named site, no algorithm update, no distinction drawn between pages written by a language model and pages written by a template from 2018. This is guidance restated, not policy changed.

The concern extends beyond individual URLs

Google’s published rulebook on spam — the search spam policies — defines scaled content abuse as generating many pages mainly to manipulate rankings rather than to help anyone, and the remedy it describes is to keep those pages out of Search. Do not read that as a promise that effects stop at the individual URLs.

Mueller is describing something wider. The pages are the evidence; the judgement is about the site. That distinction changes the maths for anyone who has ever shipped a large templated section as an experiment, on the assumption that the downside was capped at “those URLs won’t rank.” If the downside is actually the site’s standing overall, then the money pages that had nothing to do with the experiment are exposed too.

It also changes what “cleaning up” means. Removing a large page set needs its own checks for useful content, links and customer journeys. Convincing a system that has already formed a view of the site is not, and Mueller was explicit that it isn’t fast.

What to do about it

Judge each template separately. Sitewide traffic charts hide this completely. Pull the numbers for one page set at a time — how many of those URLs are indexed at all, how many get impressions in a month, how many get clicks. A template where the great majority of pages have never had an impression is telling you something.

Check that the rows carry real information. Open three pages from the set and read them side by side. If the only differences are the ones a find-and-replace would produce, the set is thin no matter how many words are on each page.

Choose a remedy for each page set. Improve, consolidate or remove pages according to their value and purpose. A noindex tag excludes a crawlable page from results; it does not prove the wider quality issue is resolved.

Validate in one locale before scaling. Building the same weak template in six languages multiplies the evidence against you rather than the reach.

Know what you already have. Plenty of sites are carrying a programmatic section somebody shipped years ago and forgot. Recovery advice is irrelevant if nobody has counted the pages.

Want this running under your brand?Preferium AI Edge is a white-label platform agencies resell to their clients: your brand, your Stripe, your packages and prices. Registration opens to agencies from the waitlist first.Talk to usJoin the waitlistHow white label works

Build your agency on Preferium

Partner registration opens by invitation from the waitlist, and there is no date yet. Read the agency agreement and how partner billing works before you decide.

  1. Connect a client site
  2. Set the control level
  3. Run under your brand

Privacy choices

Choose which optional technologies Preferium AS may use. All of them are off until you choose.

Analytics: Google Analytics 4 counts page views. Google may receive the page address, referrer, network address, browser and device details, and online identifiers. Browser storage: _ga, _ga_*: Up to 730 days. Renewed on activity. The browser may shorten the storage period.

Provider: Google Ireland Limited. Google may transfer data to the United States.

See the cookie notice, the privacy notice and theterms.

Necessary technologies Used for site functions

Preferium AS and Cloudflare deliver the site and protect forms against abuse. A local preference remembers if you pause animation. When optional tracking is available, the site can also remember your documented privacy choices.

Consent receipt
Provider: Preferium AS. HttpOnly receipt that documents and retrieves your consent choice. Name in the browser: __Host-preferium_consent. Storage period: The receipt is valid for up to 180 days without rolling renewal.
Local privacy choices and pending rejections
Provider: Preferium AS. Local storage of privacy choices and pending rejections. The entry alone can never allow optional technologies; a valid server receipt is required. Name in the browser: preferium-consent-v2. Storage period: Until the entry is overwritten or the browser site data is cleared. No automatic timed deletion is configured.
Privacy choice synchronization between tabs
Provider: Preferium AS. The latest message that synchronizes privacy choices and pending rejections between tabs. The message can only close optional technologies and trigger a new server check. Name in the browser: preferium-consent-sync-v1. Storage period: Until the entry is overwritten or the browser site data is cleared. No automatic timed deletion is configured.
Motion pause preference
Provider: Preferium AS. Session storage restores the requested accessibility preference between pages in this tab. Nothing is sent to a server. Name in the browser: preferium-motion-paused. Storage period: Until this browser tab session ends.
Cloudflare Turnstile
Provider: Cloudflare. Abuse protection that loads only on forms where Turnstile is necessary. Storage period: Short-lived control value tied to a form submission.
Analytics

Helps us understand how the site is used, when you consent.

Provider: Google Ireland Limited. The data may include the page address, referrer, network address, browser/device, online identifiers and usage events.

_ga, _ga_*
Processes site usage for aggregated analytics after specific consent. Storage period: Up to 730 days. Renewed on activity. The browser may shorten the storage period.

You can withdraw your choice via Privacy choices. That stops further optional loading but does not recall data already sent to Google. We attempt to delete known first-party values; the browser may prevent deletion of third-party values.

How Google uses and is responsible for data · How Google uses information from partner sites · Google privacy policy