Thirteen free tools for diagnosing a Google traffic drop, in the order you should use them. Start with the date checker to find out whether a confirmed update hit you. If none matches, check the volatility sensor for unconfirmed movement. Then use the E-E-A-T rubric or the disavow builder depending on what the diagnosis points to. No signup, no email required, and nothing is sent to a server except the searches the tracker and sensor already run.
Live algorithm update tracker
Every confirmed Google ranking update since 2020 with start date, end date and rollout length. Synced twice a day with the Google Search Status Dashboard, so new updates appear here automatically.
Use it to match the date your traffic fell against a named update.
Open tool →GSearch Console drop analyzer
Paste your Search Console export and the tool finds the exact day traffic broke, works out whether you lost rankings or lost clicks, and matches the date against confirmed updates. Nothing is uploaded.
The most complete free diagnosis. Start here if you have Search Console access.
Open tool →SPage scope analyzer
Paste a Pages comparison export to see whether the loss is site-wide, confined to one section, or carried by a handful of pages. Also lists the pages that gained, which is the most useful comparison you have.
Run this straight after the drop analyzer. When tells you the date, this tells you where.
Open tool →?Was my site hit? Date checker
Enter the date your Search Console clicks started falling. The tool checks it against every confirmed update and the daily volatility record, then tells you what the pattern most likely means.
Start here if you know your drop date but not the cause.
Open tool →VSERP volatility sensor
Daily 0 to 10 volatility score built from 150 tracked keywords across 15 categories, comparing today's top 10 results with yesterday's. Catches the unconfirmed changes Google never announces.
Use it when your drop date matches no confirmed update.
Open tool →APost-update audit checklist
Sixty checks in diagnostic order across data integrity, technical health, spam policies, content, trust, links and the SERP. Mark each pass or fail and get a weighted verdict on the most likely cause.
Use it for a full diagnosis when the quick checks were inconclusive.
Open tool →$Traffic loss calculator
Estimate what the drop costs per month, what it has cost since it started, and what replacing the same traffic with paid ads would cost. The cumulative figure is the one that settles budget conversations.
Use it to build the business case before committing budget.
Open tool →PRecovery timeline planner
Pick the cause, the drop date and your team capacity, and get a dated plan separating the work you control from the reassessment you do not. The reassessment window comes from real core update gaps.
Use it once you know the cause, to set expectations before work starts.
Open tool →CNext core update countdown
Days since the last confirmed core update completed, measured against the historical gap between core updates. Core demotions are only reassessed when the next one runs, so this is the recovery calendar.
Use it to plan when your fixes need to be live and crawled.
Open tool →BIndex bloat ratio
Paste your Pages export to see what share of your index earns no impressions. Under 20 percent is healthy. Sites demoted by core or helpful content updates usually sit at 40 to 70 percent.
Use it after a site-wide drop, before deciding what to prune.
Open tool →@Update and volatility alerts
An email when Google confirms a new ranking update, and an email when volatility spikes without a confirmation. Two triggers, double opt-in, one-click unsubscribe. Not a newsletter.
Set it once so you hear about the next update without checking.
Open tool →EE-E-A-T scoring rubric
Twenty weighted checks drawn from what Google's quality raters are asked to look for, scored out of 100 with trust weighted heaviest. Returns your highest-impact gaps in order.
Use it after a site-wide core update drop.
Open tool →DDisavow file builder
Paste domains or URLs in any format and get a correctly formatted disavow file. Strips protocols and www, removes duplicates, flags malformed lines, checks Google's size limits.
Use it only if links are the confirmed cause.
Open tool →Which tool to use when
Using these in the wrong order is how people end up fixing the wrong thing. The sequence below matches the diagnostic order I follow in paid engagements.
| Step | Your situation | Tool | Measurement (what you learn) |
|---|---|---|---|
| 1 | You have Search Console access | Drop analyzer | The exact break date, plus whether you lost rankings or clicks |
| 2 | You have the date, now you need the scope | Page scope analyzer | Whether the loss is site-wide, one section, or a few pages |
| 3 | You know your drop date but not the cause | Date checker | Whether a confirmed update was rolling out on that date |
| 4 | No confirmed update matches your date | Volatility sensor | Whether search was unusually turbulent that day anyway |
| 5 | You want the full rollout history and context | Update tracker | Every confirmed update since 2020, with dates and type |
| 6 | The whole site dropped, not one section | Index bloat ratio | What share of your index earns nothing |
| 7 | A core update hit the whole site | E-E-A-T rubric | Which quality gaps cost the most, ranked by weight |
| 8 | Links are the confirmed cause | Disavow builder | A correctly formatted file with errors flagged |
| 9 | The quick checks were inconclusive | Audit checklist | A weighted verdict across all seven diagnostic areas |
| 10 | You need to justify a recovery budget | Traffic loss calculator | Monthly, annual and cumulative cost of the drop |
| 11 | You know the cause and need a schedule | Timeline planner | A dated plan with a realistic reassessment window |
| 12 | Fixes are in and you are waiting | Core update countdown | Where the current wait sits against the historical gap |
| 13 | You want to hear about the next one | Update alerts | An email when Google confirms an update or volatility spikes |
Step five is deliberately last, and most sites never reach it. Google generally ignores links it does not trust rather than penalising you for them, so disavowing is the right move only when there is a manual action or a known history of bought links. Reaching for it first is one of the more expensive mistakes in recovery work.
What these tools cannot tell you
Every one of these works from public data or from what you type in. None of them can see your site, so all of them produce leads rather than diagnoses.
- They cannot prove causation. Why: A confirmed update running on your drop date is correlation. Sites also drop during core updates for technical reasons, and the fix is completely different.
- They cannot see a manual action. Why: Only your Search Console shows that, and it overrides everything else. Check the Manual Actions report before accepting any algorithmic explanation.
- They cannot detect AI Overview click loss. Why: That shows as flat impressions with falling clicks in your own data. See impressions stable, clicks falling.
- The E-E-A-T score is a self-audit. Why: It reflects how honestly you ticked the boxes. Google computes no E-E-A-T score, so this measures your gaps against the rater guidelines, not a Google metric.
Guides that go with the tools
Each tool answers one question. These guides cover what to do with the answer.
- The first 48 hours checklist. Why: What to export before the data ages out, and the five things never to do in the first two days.
- Rankings dropped but no update matched. Why: Seven causes in diagnostic order, six of which are not algorithm events at all.
- How long recovery takes. Why: Real timelines by update type, with the actual gaps between core updates so you can plan.
- What the Google algorithm actually is. Why: Which ranking system does what, so you know which one your symptoms point at.
- The full update history. Why: Every era since 2011 and what each one still means for recovery today.
Frequently asked questions
Are these tools really free?
Yes, with no signup and no email required. The disavow builder and the E-E-A-T rubric run entirely in your browser and send nothing anywhere. The tracker and sensor run on data this site already collects.
How often is the update data refreshed?
The tracker syncs with the Google Search Status Dashboard twice a day, so a new confirmed update appears within hours. The volatility sensor collects a fresh snapshot every morning and scores it against the previous day.
Which tool should I use first?
The date checker, if you know roughly when your traffic fell. It takes seconds and eliminates or confirms the most common explanation before you spend time on anything else.
Can these tools replace a paid audit?
For a simple drop that matches a known update on a site you understand well, often yes. They cannot analyse your Search Console data, separate overlapping causes, or tell you which of your page templates is dragging the rest down.
Used the tools and still cannot place your drop?
Send your Search Console access or export. Within 48 hours I will tell you which update it correlates with, which page groups are affected, and whether the cause is algorithmic, technical or click displacement. Free, no obligation.
Get free recovery audit