Google core and spam updates in 2026: what happened, and what to do after a ranking drop
By Thomas Lovas Lokoy · Published 23 October 2026 · 6 min read
If your traffic dropped this autumn, start by finding out which update, if any, lines up with the drop. Google's Search Status Dashboard lists two core updates so far in 2026, in March and May, and four spam updates, the most recent starting on 24 September 2026. A core update drop usually means other pages were judged more helpful, not that yours broke a rule; a spam update drop means it is worth checking your site against Google's spam policies, particularly the one on scaled content. This guide sets out the 2026 timeline from Google's own dashboard, how Google says to assess a drop, and what to do in each case.
The 2026 ranking updates so far
These are the ranking entries on Google's Search Status Dashboard for 2026, as of October 2026. End dates are approximate, worked out from the start date and the duration the dashboard shows.
| Update | Started | Finished (approx.) | | --- | --- | --- | | September 2026 spam update | 24 September 2026 | about 7 October 2026 | | August 2026 spam update | 18 August 2026 | about 20 August 2026 | | June 2026 spam update | 24 June 2026 | about 26 June 2026 | | May 2026 core update | 21 May 2026 | about 1 June 2026 | | March 2026 core update | 27 March 2026 | about 8 April 2026 | | March 2026 spam update | 24 March 2026 | about 25 March 2026 | | February 2026 Discover update | 5 February 2026 | about 26 February 2026 |
Two things stand out. There was no core update in September 2026, despite searches for one; the September entry is a spam update. And the core updates took around eleven to twelve days each to roll out, while two of the spam updates finished in about two days.
Core updates: what Google says they are
Google describes core updates as broad changes to its search systems, "designed to ensure that overall, we're delivering on our mission to present helpful and reliable results". They happen "several times a year" and do not target specific sites or pages.
Google is unusually direct about what a drop means. Its core updates page says most sites do not need to worry about them, and that pages which move down are not necessarily bad: it compares the change to a ranked list in which other options have simply risen above yours.
How Google says to assess a core update drop
Google's page sets out a method, and it is worth following in order rather than reacting to the first bad day:
- Wait until the rollout is complete. The dashboard marks the end.
- Then wait at least a full week. Google says to wait "at least a full week after a core update completes" before checking Search Console.
- Compare like with like. Compare that week with the week before the update started.
- Judge the size. Small drops in position generally do not call for drastic action. Large, sustained drops warrant a self-assessment of the whole site against Google's questions about helpful content.
Google also advises against "quick fix" changes and calls deleting content a last resort. On timing, it says improvements can take effect in days, but that "it could take several months" for its systems to confirm a site is consistently helpful, and that if nothing changes after a few months, the next core update may be the next opportunity.
Our summary of Google's people-first questions is in how to write helpful content, and the trust signals behind them are in E-E-A-T explained.
Spam updates: a different question
A spam update is not a judgement about which of two good pages is more helpful. Google describes spam updates as notable improvements to its automated spam detection, including SpamBrain, its AI-based spam-prevention system. If your site changed after a spam update, Google's advice is to review its spam policies and make sure you comply. Recovery is not immediate: Google says its systems may need several months to recognise that a site now complies.
There is one exception worth knowing. After a link spam update, Google says changes may not bring improvement, because once the effect of spammy links is removed, the ranking benefit those links gave is lost for good.
The policy AI-assisted publishers should read first
For anyone publishing with AI writing tools, the most relevant section of Google's spam policies, last updated 28 August 2026, is scaled content abuse: "when many pages are generated for the primary purpose of manipulating search rankings and not helping users". Google adds that this applies "no matter how it's created".
Its examples include "using generative AI tools or other similar tools to generate many pages without adding value for users", scraping or automatically transforming other content, stitching content together from other pages, and creating many pages that make little sense to a reader but contain search keywords.
The key words are "many pages" and "without adding value". Google's separate guidance on AI-generated content, covered in AI-generated content and Google Search, does not penalise a tool; it penalises the purpose and the result. An AI draft that a person has checked, sourced and improved is a different thing from a thousand unreviewed pages.
What to do, by type of drop
| What you see | Likely cause | First steps | | --- | --- | --- | | A gradual or modest dip around a core update | Other pages judged more helpful | Wait for the full week after rollout, compare weeks, then improve the pages that lost most | | A large, sustained, site-wide drop after a core update | Site-wide helpfulness concerns | Self-assess the whole site against Google's helpful-content questions; improve, do not mass-delete | | A sharp drop around a spam update | Possible spam-policy issue | Read the spam policies, especially scaled content abuse; check for thin, duplicated or unreviewed pages | | A drop with a message in Search Console's Manual actions report | Manual action | Follow the instructions in the report, fix, then request a review | | A drop that matches no update | Technical or seasonal | Check indexing, robots.txt, redirects and last year's traffic for the same weeks |
A recovery plan you can run this month
- Pull the dates. Note when the drop started and match it against the table above.
- Find the pages. In Search Console, compare the full week after the relevant update with the week before, by page, and list those that lost most.
- Read them as a stranger would. Does each one answer its title quickly, cite its facts and add something a reader cannot get elsewhere? Our fact-checking routine is a good fixed-order review.
- Improve, then update honestly. Rewrite weak sections and fix outdated facts, following our guide to updating old posts safely.
- Prune only as a last resort. If a page cannot be made useful, merge it into a better one with a redirect rather than deleting dozens at once.
- Give it months, not days. Google's own timelines for both core and spam recovery are measured in months.
Where AI Orbit fits
AI Orbit drafts one researched article at a time, with sources, for a person to review and publish. That workflow sits on the right side of the scaled content policy only if the review actually happens. Use the drafting time it saves on the checks above. Plans and credits are on the pricing page.