Work through four possibilities in order. Is the drop real, or a reporting artifact? Does the date line up with a confirmed Google update? Did something change on your site? Did something change on someone else's?
The date is the most useful piece of information you have. Almost everything below sorts itself once you know it.
First: Is It Actually A Drop?
Start here, because a surprising number of panics turn out to be measurement problems. Three known ones have hit in the past two years, and each made healthy sites look damaged.
Your rank tracker lost visibility, not your site
Google removed the &num=100 search parameter. Rank-tracking tools had used it to pull a hundred results in a single request, which is how they reported positions beyond the top ten cheaply.
When it disappeared, tools across the industry started showing keyword losses. Ahrefs documented the impact publicly. Those losses were a measurement change, not a ranking change. If your drop appears in a third-party tool but not in Search Console, this is the first thing to rule out.
The 15 September 2025 Search Console glitch
A dramatic drop dated specifically to 15 September 2025 was a confirmed Search Console reporting glitch. Not an algorithm event. If your chart has a cliff on that exact date, you are looking at a bug that has since been documented.
The impression logging error
This one is subtler and still affects how you read old data. Google confirmed a logging error affecting Search Console impression data from around May 2025, with a fix that only began rolling out in early April 2026.
The practical consequence: impressions, click-through rate and average position from before late April 2026 may be an inflated baseline. Clicks were not affected. So if you are comparing this month against last spring and the impressions look catastrophic, check the clicks line before you conclude anything.
Open Search Console, look at clicks only, and set the range to 16 months. If clicks are steady and only impressions fell, you probably have a reporting artifact rather than a ranking problem.
If clicks fell too, keep reading.
Second: Check The Date
Once you know the drop is real, the date does most of the diagnostic work. A drop that starts inside a confirmed Google rollout has a different explanation — and a different response — than one that starts on a random Tuesday.
Put the approximate date below. It checks against Google's confirmed update history and the known reporting artifacts.
Pick a date
Use the day the decline began, not the day you noticed it. Those are often two or three weeks apart.
Google's Confirmed Update Timeline
These dates come from Google's Search Status Dashboard. They are the only update dates worth trusting — everything else is inference from volatility trackers.
| Update | Window | Length |
|---|---|---|
| May 2026 core update | 21 May – 2 June 2026 | ~12 days |
| March 2026 core update | 27 March – 8 April 2026 | 12 days |
| March 2026 spam update | 24 – 25 March 2026 | <20 hrs |
| February 2026 Discover core update | 5 – 27 February 2026 | 22 days |
| December 2025 core update | 11 – 29 December 2025 | 18 days |
| June 2025 core update | 30 June – 17 July 2025 | ~17 days |
| March 2025 core update | 13 – 27 March 2025 | ~14 days |
| December 2024 core update | 12 – 18 December 2024 | ~6 days |
| November 2024 core update | 11 Nov – 5 December 2024 | ~24 days |
| August 2024 core update | 15 Aug – 3 September 2024 | ~19 days |
| March 2024 core update | March – May 2024 | 45 days |
Source: Google Search Status Dashboard, as reported by Search Engine Land, Search Engine Journal, Search Engine Roundtable and Ahrefs. Retrieved August 2026.
The cadence tightened. Core updates used to arrive twice a year. In 2026 two landed roughly six weeks apart. If you have not looked at your Search Console data in a quarter, you have probably lived through one without noticing.
Google states that ranking drops do not necessarily mean something is wrong with your site, that core updates are broad and do not target specific sites or pages, and that recovery often comes with a later core update rather than an immediate fix.
It also recommends waiting at least one full week after a rollout completes before analysing your data. Mid-rollout numbers are noise.
Which Pages Actually Lost?
This step decides everything after it, and most people skip it. A drop spread across every page means something site-wide or an update. A drop on four pages means those four pages.
Here is how to see it in Search Console, which is free and which you already have if anyone set it up.
- Open the Performance report and switch to the Pages tab.
- Set the date range to Compare, and pick the four weeks before your drop date against the four weeks after.
- Sort by the clicks difference column, smallest first. Your biggest losers are now at the top.
Then read the shape of it. If a handful of pages lost almost everything and the rest are flat, the cause is on those pages — content edits, lost redirects, or a competitor beating you on those specific queries.
If everything dropped by a similar percentage, no individual page is at fault. That pattern points at a core update, a technical problem affecting the whole site, or seasonality.
And if a few pages dropped while others gained, that is the classic core update signature. Google reassessed the results and you moved in both directions.
Impressions steady, average position steady, clicks down. That is not a ranking drop at all — you still rank where you did, and fewer people are clicking.
Usually that means something new appeared above you on the results page. An AI Overview, a new ad block, a shopping carousel. The fix is a different problem from the one you thought you had.
Third: Things You Changed
If the date does not match an update, look inward. These are the self-inflicted causes we see most often, roughly in order of frequency.
You rewrote a title or an H1
The most common one, and the most reversible. Changing a heading changes how Google understands what a page is about. A page that was a strong match for a phrase can quietly stop being one.
We have watched a single headline edit cost a page-one position. If your drop began within a week or two of a content change, restore the previous version first and see whether positions return before you investigate anything else. That is the cheapest test available.
You redesigned the site and lost the redirects
The most expensive one. If a new site changed URLs without mapping every old address to its new equivalent, the rankings those pages held do not transfer. They just stop.
Check Search Console for a spike in 404s. Crawl your old sitemap and find every URL now returning an error. Then map each one to its closest replacement. Traffic built over three years can vanish in a weekend this way, and it usually takes months to fully recover.
A staging tag survived the launch
A noindex meta tag or a development robots.txt carried over to production will remove pages from Google entirely. It looks like a catastrophic ranking collapse and it is a two-minute fix once you spot it.
Search Console's Pages report will tell you: look for pages excluded by "noindex" or "blocked by robots.txt" that should not be.
You consolidated or deleted pages
Merging thin pages is often good advice. It also removes URLs that were ranking for something, and if those redirects were not set, that traffic goes with them. Any consolidation should be paired with a redirect map, not just a delete.
You changed platform or host
Migrations break things quietly. Slower response times, changed URL structures, dropped schema, missing canonical tags, an accidentally blocked crawler. If the drop coincides with a platform move, start there rather than with content.
Fourth: Things You Didn't Change
Rankings are relative. You can stand perfectly still and fall, because position is a comparison rather than a score.
A competitor got better
Someone published a more complete page, earned links, or finally built the service page you have been meaning to write. Nothing about your site changed. You just got outperformed on that specific query.
Search your term and look at what is above you now that was not before. This is usually visible in about ninety seconds.
An AI Overview appeared
If an AI-generated answer now sits above the results for your query, clicks fall even when position holds. Watch for the signature: impressions steady, average position steady, clicks down. That pattern is not a ranking problem, and no amount of on-page work will fix it directly.
What helps is being one of the sources such answers draw from, which is a different discipline. We cover it in AI search optimisation.
Your business information drifted
For local businesses especially. A phone number changed on one directory, an old address resurfaced, a listing you forgot about contradicts your site. Google's confidence in the business erodes and map pack positions soften. This is slow, quiet, and very fixable — see local SEO.
It is seasonal
Check the same period last year before diagnosing anything. Roofing enquiries fall in February. Tax services fall in May. A drop that repeats annually is a calendar, not an algorithm.
The whole channel dropped, not just Google
Here is a check most recovery guides skip. If email engagement, social traffic and direct visits all fell at the same time, the algorithm is probably not your problem. Something happened to demand, or to your business, and search is just where you noticed it first.
What To Do, In Order
- Confirm it is real. Clicks in Search Console, 16-month view. Rule out the three reporting artifacts above.
- Date it precisely. The day the decline began, not the day you noticed. Use the checker above.
- Check the dashboard. Was a confirmed update rolling out? If yes, wait for it to finish plus one week before doing anything.
- List your own changes. Every edit, launch, migration and deletion within three weeks either side of the date.
- Identify the affected pages. Sort Search Console by biggest losers. A few pages points at content. Most pages points at the site or an update.
- Check the technical basics. Indexation, robots.txt, noindex tags, 404 spikes, redirect chains, page speed.
- Look at who replaced you. Search the term. See what is there now. Note what they have that you do not.
- Fix the highest-confidence cause first. One thing at a time, so you can tell what worked.
Keep a change log. A dated note every time anyone edits content, launches a page, changes a plugin or touches the theme.
It costs nothing and it turns "we have no idea what happened in April" into a five-minute diagnosis. Almost nobody does this, and everybody who has ever needed it wishes they had.
What Not To Do
Do not make changes during a rollout. Rankings move unpredictably mid-update because different systems update at different times. Week-one movement frequently reverses before completion. Changes made now also make it impossible to tell later whether a recovery came from your fix or the update settling.
Do not delete pages in a panic. Deleting content because it lost rankings removes any chance of it recovering, and Google's guidance on core updates points toward improving quality rather than culling.
Do not buy links to fix it. Whatever the cause, this is not the answer, and it adds a second problem to the one you already have.
Do not change five things at once. You will recover — maybe — and have no idea why, which means you cannot repeat it or avoid the cause next time.
Do not assume a penalty. Manual actions appear in Search Console under Security & Manual Actions. If there is nothing there, you do not have one. Core update movement is not a penalty, and Google is explicit that it is not a judgement that you did something wrong.
Questions People Ask
Work through four possibilities in order. First, check whether the drop is real — Google has had several confirmed reporting problems that made healthy sites look damaged. Second, check the date against Google's confirmed update timeline, because a drop that starts inside a core update rollout usually has a different explanation than one that starts on a random Tuesday. Third, look at what changed on your own site around that date. Fourth, look at what competitors changed. Most drops resolve to one of those four, and the date is what tells you which.
Compare your drop date against the Google Search Status Dashboard. If it began during a confirmed rollout window and affected many pages at once rather than a few, a core update is the likely cause. If it began on a date with no confirmed update and affected a small number of pages, something on your own site is the more likely explanation. Google recommends waiting at least a full week after a rollout completes before analysing Search Console data, because rankings move unpredictably mid-rollout.
Something changed, just not on your site. A competitor published better content or earned links. Google reassessed the results in a core update. Your business information drifted out of sync across directories. An AI Overview appeared above the results and absorbed clicks that used to reach you. Or the drop is seasonal and the same thing happened last year. Google's own guidance on core updates states that a ranking drop does not necessarily mean something is wrong with your site.
Check three known artifacts before diagnosing anything. Google removed the &num=100 search parameter that rank-tracking tools relied on, which made many tools report keyword losses that were measurement changes rather than ranking changes. A dramatic drop dated 15 September 2025 was a confirmed Search Console reporting glitch. And Google confirmed an impression logging error affecting Search Console data from around May 2025 until a fix began rolling out in early April 2026, meaning impressions, click-through rate and average position before late April 2026 may be an inflated baseline. Clicks were not affected by that one.
Google's stated position is that recovery often comes with a later core update rather than an immediate fix, because the systems need to see sustained improvement before reassessing. Core updates currently arrive roughly every three months, so a realistic recovery window is one to two update cycles, assuming the underlying quality issue is genuinely addressed. Making frantic changes during a rollout is the most common mistake, and it makes the eventual diagnosis harder.
Yes, and it is one of the most common self-inflicted causes. A title or H1 rewrite changes how Google understands what the page is about, and a page that was a strong match for a phrase can stop being one. If your drop began within a week or two of a content edit, restore the previous version first and see whether positions return before investigating anything else.
Almost always redirects. If the new site changed URLs without mapping every old address to its new equivalent, the rankings those pages held do not transfer. Check Search Console for a spike in 404 errors and crawl the old sitemap to find URLs that now return errors. Other common causes are a staging noindex tag left in place at launch, a robots.txt file carried over from the development environment, and content that was shortened during the redesign.
No. Rankings move unpredictably during a rollout because different ranking systems update at different times, and week-one movement frequently reverses before completion. Google recommends waiting at least one full week after a rollout finishes before analysing your data. Changes made mid-rollout also make it impossible to tell later whether a recovery came from your fix or from the update settling.
Want A Second Pair Of Eyes On It?
Send us the site and roughly when the drop started. We'll check the date against the update timeline, look at which pages lost what, and tell you what we think happened — in writing, for free, with no call required.
If it turns out to be a reporting artifact and nothing is actually wrong, that's what we'll say.
Get A Free Audit 📞 1-800-481-8638Update dates in this article come from Google's Search Status Dashboard as reported by Search Engine Land, Search Engine Journal, Search Engine Roundtable and Ahrefs, retrieved August 2026. Google's guidance on core updates and recovery is quoted from its own core updates documentation. No client data or case study results appear in this article.