When it breaks
Was it a Google update?
Search traffic fell and there is a date on the graph where it started. Before you rewrite a single page, do the boring thing: check that date against the official update calendar, read the shape of the loss, and let the query data name the cause. The diagnosis takes an afternoon. Getting it wrong costs a rebuild aimed at the wrong problem.
First confirm the shape. If impressions held while clicks fell, an update may not be your problem at all; that pattern is covered at AI Overviews took the clicks. If traffic held and revenue fell, you want the RPM page. Undiagnosed? Start at the triage quiz.
Step one
Line the date up against the calendar
Google publishes every confirmed ranking update, with start and end dates, on the Search Status Dashboard's ranking history. That page is the only authoritative calendar; SEO news sites report suspected updates too, but the dashboard is what Google actually confirmed. Google's own advice for a suspected core update hit is to "check the Search Status Dashboard and take note of the start and end date of the core update," then in Search Console "try comparing this week with a week before the core update started rolling out."
The confirmed windows since mid-2025, as the dashboard listed them on July 11, 2026:
| Update | Rollout began | Rollout complete |
|---|---|---|
| June 2025 core update | Jun 30, 2025 | Jul 17, 2025 |
| August 2025 spam update | Aug 26, 2025 | Sep 22, 2025 |
| December 2025 core update | Dec 11, 2025 | Dec 29, 2025 |
| February 2026 Discover update | Feb 5, 2026 | Feb 27, 2026 |
| March 2026 spam update | Mar 24, 2026 | Mar 25, 2026 |
| March 2026 core update | Mar 27, 2026 | Apr 8, 2026 |
| May 2026 core update | May 21, 2026 | Jun 2, 2026 |
| June 2026 spam update | Jun 24, 2026 | Jun 26, 2026 |
Read from the dashboard July 11, 2026; no ranking update was rolling out on that date. Rollouts run days to weeks, so your drop can land anywhere inside a window, not just on day one. Always recheck the live page before concluding, because this table ages the moment the next update ships.
A drop that starts inside one of those windows is a candidate, not a conviction. A drop that starts weeks away from every window is telling you to look elsewhere: a site change, a technical problem, seasonality, or the clicks-without-rankings pattern. Google's debugging guide for traffic drops sketches the shapes: sharp site-wide steps from updates or security issues, gradual slides from technical problems or fading interest, and the repeating curve of seasonality. Compare year over year before you blame an algorithm for what the calendar does every year.
Step two
Read the shape: site-wide or page-level
In Search Console's Performance report, set the comparison Google suggests: the week before the rollout began against a week after it completed. Then look at where the loss lives. A core update reassesses the site broadly, so its signature is a haircut across many pages and many queries at once. A loss confined to one page or one cluster, with the rest of the site flat, points at something narrower: a stronger competitor on those queries, a content problem on those pages, or a technical issue in that section.
Check the size of the position moves too. Google's guidance distinguishes a small slip, position two to four, from a large one, and says a small decline needs no drastic action. Falling from position 2 to 4 halves your clicks and means Google still likes the page; falling from 4 to 29 means the page effectively left the results. Those are different problems, and only the second one justifies real work.
One more gate before you conclude "update": open the Manual Actions report in Search Console. A core update is not a penalty and never appears there. If that report is empty, nobody demoted you by hand, and anyone selling you "penalty removal" for a core update is selling a service for a thing that does not exist. There is nothing to remove. There is only content to make better.
Step three
Let the query classes name it
Export your queries for the comparison window and sort them into rough classes: brand searches for your site by name, informational questions, and the commercial or tool-like queries where the searcher needs to do something. Each class failing has a different meaning. Brand queries holding while informational queries collapse says your audience still wants you and the algorithm rerouted the strangers. Everything falling together, positions included, is the core-update signature. Informational clicks falling while impressions and positions hold is not a ranking event at all; that is the AI Overviews pattern, and it needs a different response than a rebuild.
| What the reports show | Likely read | Your move |
|---|---|---|
| Broad drop across pages and queries, starting inside an update window, positions down | Core update reassessment | The honest-recovery section below. No quick fix exists. |
| One section or cluster down, rest of site flat | Page-level problem | Assess those pages against the queries they lost; check what now ranks instead. |
| Clicks down, impressions and position stable, informational queries | AI Overviews absorption | Measure it query by query. |
| Drop repeats at the same time every year | Seasonality | Compare year over year and change nothing rash. |
| Notice in the Manual Actions report | Manual action, not an update | Follow the notice's own remediation steps; this page is the wrong guide. |
The honest part
What Google actually says about recovery
Google's core-update documentation is unusually plain, and it is worth taking at face value instead of filtering it through people selling recoveries. Pages that fall in a core update are not necessarily broken. Google's analogy is a refreshed list of top restaurants: the ones "that move down aren't necessarily 'bad'; there are just other restaurants that make your top 20." There is no fix to apply, because nothing was flagged. The guidance is to "focus on making changes that make sense for your users and are sustainable in the long term," to self-assess the site as a whole against people-first content questions, and it adds that "deleting content is a last resort," only for what cannot be salvaged.
On timing, Google says improvement can take months: "it could take several months for our systems to learn and confirm that the site as a whole is now producing helpful, reliable, people-first content," and "if it's been a few months and you still haven't seen any effect, that could mean waiting until the next core update." It also says outright that "there's no guarantee that changes you make to your website will result in noticeable impact in search results." That is the honest frame: recovery is measured in update cycles, the confirmed cores of the past year landed roughly two to five months apart, and the work is content work, not a technical trick.
We will not dress that up. If the diagnosis says core update, the calm response is to decide, with open eyes, whether this site earns months of content investment on those terms. That decision has its own framework at pivot or persist, and if search demand for your topics still exists, the rebuild case is real. What does not work is panic-pruning, mass rewrites aimed at an imagined penalty, or paying someone to "remove" one.
Sources for this page: Google's Search Status Dashboard ranking history, core updates guidance, and Debugging drops in Google Search traffic, all checked July 11, 2026.
Diagnose first, then decide
An afternoon in Search Console beats a quarter of guessing. If the verdict is an update, the fork between rebuilding, pivoting, and selling is laid out calmly at pivot or persist. If the loss turns out to be clicks rather than rankings, read the AI Overviews page next. The rest of the failure modes live at When it breaks.
Run the triage quiz All the failure modes