Google’s confirmed 2026 ranking history is not one March event. The official record includes a February Discover core update, March and May core updates, and spam updates in March, June, and August. A traffic change near one of these dates is a correlation to investigate, not proof that Google penalized a site or targeted AI-written content.
Official Google ranking updates in 2026
| Start date | Update | Official duration | Scope to investigate |
|---|---|---|---|
| February 5 | February 2026 Discover core update | 21 days, 17 hours | Discover visibility for English users in the United States during the initial rollout |
| March 24 | March 2026 spam update | 19 hours, 30 minutes | Compliance with Google Search spam policies |
| March 27 | March 2026 core update | 12 days, 4 hours | Broad ranking reassessment across queries and pages |
| May 21 | May 2026 core update | 11 days, 21 hours | Broad ranking reassessment across queries and pages |
| June 24 | June 2026 spam update | 2 days, 1 hour | Compliance with Google Search spam policies |
| August 18 | August 2026 spam update | 2 days, 16 hours | Compliance with Google Search spam policies |
The dates and durations above come from the Google Search Status Dashboard. June and August were spam updates, not core updates. Google’s August 28 site-reputation policy announcement was a policy and enforcement change; it should not be relabeled as an August core update.
Core, spam, and Discover updates require different checks
| Update type | What Google says | First site check |
|---|---|---|
| Core | A broad change to ranking systems, not a penalty aimed at one site or page | Compare page and query cohorts, then assess sitewide usefulness and reliability |
| Spam | An improvement to automated systems that detect policy violations | Review the exact spam policies and any Search Console manual-action notice |
| Discover core | A broad update to systems that surface articles in Discover | Analyze Discover separately from Web Search |
Google did not say that any of these 2026 updates removed AI-written pages as a class. The relevant question is whether a page is useful, original, reliable, and compliant, regardless of how its first draft was produced.
Why timing alone cannot identify the cause
A site can change at the same time as Google. Articles may be rewritten, recrawled, dropped from the index, consolidated, or linked differently during an update window. If those events are mixed together, the analysis cannot separate an algorithm effect from a site change.
For every affected URL, record four dates or states:
- the date the current article version was published;
- Google’s last crawl date for that version;
- the indexed, crawled-not-indexed, or discovered-not-indexed state;
- the update window that overlaps the observation period.
If Google crawled before the article changed, current Search Console performance may still reflect the old version. If a page moved out of the index, ranking analysis should wait until indexing and page-selection questions are resolved.
Build matched Search Console cohorts
Google recommends waiting at least one full week after a core update finishes and comparing equal periods before and after it. Keep search type, country, device, and period length consistent. Use separate cohorts so that one sitewide total does not hide opposite movements.
| Cohort | Question | Action if it fails |
|---|---|---|
| Indexed and unchanged | Did rankings or click-through rate change without a site edit? | Review queries, competitors, snippets, and page usefulness |
| Edited and recrawled | Did Google process the new version before the comparison window? | Attribute cautiously and track this cohort separately |
| Edited but not recrawled | Is the observed performance still tied to the old version? | Wait for a crawl before judging the edit |
| Not indexed | Is the issue discovery, selection, duplication, or technical access? | Run URL Inspection, intent-overlap, and technical checks |
Separate page loss from query cannibalization
Analyze pages, queries, and query-by-page rows together. A page that loses impressions while another page on the same site gains the same query may have an ownership problem rather than an update-specific quality problem. Assign one primary owner to each search task, then decide whether nearby pages should be differentiated, consolidated, or retired.
Protect a page from destructive changes when it has current clicks, meaningful organic sessions, conversions, or external links. A small average-position move is not a reason for a large rewrite.
Use a dated SERP snapshot as supporting evidence
A current SERP can show whether Google is favoring news, official documentation, tutorials, product pages, or discussions for a query. Save the query, country, language, timestamp, organic results, and visible SERP features. The SearchCans Google Search API can preserve that snapshot as JSON.
A SERP snapshot does not prove why a ranking changed, and it does not provide search volume. Use it with Search Console history, Analytics behavior, URL Inspection, internal links, and external-link evidence.
What to do after a spam update
- Check Search Console for a manual action, while recognizing that automated spam systems do not require one.
- Review Google’s current spam policies against actual publishing and linking practices.
- Identify scaled pages with repeated intent, templated filler, unsupported claims, or little independent value.
- Preserve useful evidence, examples, and external-link value before consolidation.
- Publish corrections in small, traceable batches and repair internal links to final canonical URLs.
Do not delete pages only because their decline happened near a spam update. The policy review and the page-level evidence must support the action.
What to do after a core update
Review the site as a portfolio. Each retained page should have one search task, a clear owner within its keyword cluster, and material that competing pages cannot reproduce without doing the same work. Examples include a dated dataset, a reproducible test, a working implementation, a first-party observation, or a decision framework tied to evidence.
Google says improvements may take days or several months to be reflected and does not guarantee recovery. Avoid changing pages that are already performing well merely because a rollout occurred.
A cautious monitoring sequence
- Confirm the update’s type, start, and duration on Google’s dashboard.
- Wait for a stable comparison window.
- Separate Web, Discover, Image, and other search types.
- Split URLs by edit, crawl, and index state.
- Compare page, query, and query-by-page performance.
- Review spam-policy exposure separately from content usefulness.
- Change only pages with a documented deficit.
- Monitor each changed batch for 14, 28, and 56 days.
Official sources
- Google Search Status Dashboard: confirmed 2026 ranking updates, dates, and durations.
- Google Search core-update guidance: comparison windows, assessment, and recovery timing.
- Google Search spam-update guidance: how automated spam updates relate to policy compliance.
- Google Search spam policies: current policy definitions.
- February 2026 Discover core update: scope and rollout guidance.
- August 2026 site-reputation policy update: policy and regional enforcement change.
