Trust and quality notes
- Last updated
- September 2, 2026
A sudden search-traffic change can make a team want to rewrite everything at once. That is usually the wrong first move.
Google’s August 2026 spam update began on August 18, applied globally and across all languages, and finished rolling out on August 21.[1] Google did not announce a new list of prohibited tactics with the rollout. It described the event as an improvement to its automated spam-detection systems, not a replacement for its existing spam policies.[1][2]
The practical response is not to chase a secret ranking formula. It is to inspect whether your publishing process creates pages primarily for people or primarily to capture search traffic.
Start with the distinction Google actually made
A spam update and a core update are not the same thing.
Google says its automated systems are always working to detect search spam. From time to time, it makes notable improvements to those systems and calls the rollout a spam update. SpamBrain is one of the AI-based systems Google uses for this work.[2]
That means the August rollout should be treated as a detection change. Google has not said that every site seeing movement violated a policy, nor has it published a special August checklist. The standing spam policies remain the clearest basis for an audit.[3]
This distinction matters because speculative fixes can cause more damage than the original traffic movement. Deleting useful pages, changing working URLs, or rewriting an entire site before the rollout settles can destroy information that readers still need.
Audit the patterns most likely to create low-value pages
Google’s policies cover many forms of abuse, but four areas deserve immediate attention for teams using AI or repeatable publishing workflows.
1. Scaled pages without added value
Google defines scaled content abuse as generating many pages mainly to manipulate rankings rather than help users. The policy is based on purpose and value, not on whether a person or an AI tool produced the page.[3]
The risky pattern is easy to recognize: many pages follow the same shell, repeat information already available elsewhere, and exist mainly to target slight variations of a keyword.
Review a sample of recent pages and ask:
- Does each page answer a meaningfully different question?
- Is there original analysis, evidence, experience, or a useful tool?
- Would the page still deserve to exist if search engines sent it no traffic?
- Does the page help a reader complete a real task?
If the answers are weak, improve, consolidate, or remove the page from search rather than producing more versions of it.
2. Scraped or lightly transformed material
Republishing information from another source is not made original by changing a few words. Google identifies scraping, automated synonym changes, translation without added value, and stitched-together summaries as spam when they are used to manipulate rankings.[3]
A source-based article should make its contribution obvious. That contribution might be a tested process, a decision framework, first-party data, a comparison based on real use, or a clear interpretation for a specific reader.
Citation is necessary, but citation alone does not create value. A page can name its sources and still be an unnecessary copy of them.
3. Doorway pages and near-duplicate landing pages
Doorway abuse includes creating substantially similar pages for close variations of a query, region, or service, then funneling every visitor to the same destination.[3]
Look for groups of pages where only the location, role, industry, or product name changes. If the substance is the same, one strong page with clear navigation is usually better than dozens of thin entry points.
This is especially important when a team turns a content calendar into an automated publishing workflow. Automation should enforce distinct reader value, not just fill every keyword slot.
4. Links created for ranking credit
Google defines link spam as creating links to or from a site primarily to manipulate rankings. Its examples include paid links that pass ranking credit, excessive exchanges, automated link creation, and low-value content built mainly to carry links.[3]
Partnerships, sponsorships, directories, and affiliate relationships can still be legitimate. The test is whether the relationship is disclosed, the page helps the reader, and sponsored or paid links are qualified correctly.
Do not measure a partnership by how many keyword-rich backlinks it produces. Measure it by whether the combined work creates something useful enough that people would choose to visit or share it.
Use a page-level scoring rubric
A simple review score makes the audit repeatable. Score each page from zero to two on five questions:
| Question | 0 | 1 | 2 |
|---|---|---|---|
| Reader purpose | Exists mainly for search traffic | Mixed purpose | Solves a clear reader problem |
| Original value | Repeats available material | Adds limited framing | Adds evidence, experience, analysis, or utility |
| Distinctness | Near duplicate | Some unique sections | Clearly deserves its own URL |
| Source integrity | Unclear or copied | Sources named | Sources verified and contribution is explicit |
| Link integrity | Links mainly influence rankings | Mixed commercial and editorial purpose | Links are useful, disclosed, and appropriately qualified |
Pages scoring eight to ten are strong candidates to keep and improve. Pages scoring five to seven need focused revision. Pages scoring zero to four should be consolidated, removed from search, or retired unless there is a clear reader reason to preserve them.
This is an internal decision tool, not a prediction of Google’s ranking system. Google does not publish a page-level score for these factors.
Check the publishing system, not just the published page
A weak page is often the symptom of a weak workflow.
Review how ideas enter the queue, which claims require evidence, who can approve a draft, and what prevents one source from becoming dozens of shallow pages. A useful content system should keep the source, the reader’s question, the original contribution, and the approval decision visible.
The same discipline applies when using an AI assistant. Give it source material, audience context, and a quality rubric. Require it to flag unsupported claims and near-duplicate angles. Use a person to make the final editorial decision. The Agentic Workers library and tools directory can help teams build these checks into a repeatable workflow without treating every content problem as a custom software project.
Avoid panic-driven recovery work
Google says sites affected by a spam update should review the spam policies. If a site changes its practices, improvement may take months while automated systems learn that the site is complying.[2]
That makes three common reactions especially unhelpful:
- Rewriting everything immediately. Wait for reliable page and query data, then prioritize the clearest risks.
- Adding more words to thin pages. Length does not create originality or usefulness.
- Buying links to replace lost rankings. That can deepen the same policy risk you are trying to fix.
Start with Search Console data before and after the rollout. Separate sitewide movement from page-level movement. Group affected pages by template, source type, and publishing workflow. Then fix the pattern that produced the pages, not only the visible copy.
The durable standard is simple
Google’s latest spam rollout does not require teams to guess which detector changed. It requires a more useful question: would this page exist, in this form, if rankings were not the goal?
A durable publishing process produces fewer interchangeable pages, adds a clear contribution to every source, and gives people a reason to trust the result. That is better for search, but it is also better for every reader who lands on the page.
If your team needs to identify which repeated workflows are worth improving first, run the Agentic Workers AI Readiness Audit.
Sources
[1] https://status.search.google.com/incidents/LEubPCm2octf2uMqCFKE [2] https://developers.google.com/search/docs/appearance/spam-updates [3] https://developers.google.com/search/docs/essentials/spam-policies