Traffic drop after a Google update: step-by-step diagnosis

To diagnose a traffic drop after a Google update, first prove the update caused it: match the drop's start date to the Search Status Dashboard, rule out tracking, technical and seasonal causes, and confirm in Search Console that impressions and positions fell, not just clicks. Then find which queries and page groups lost, compare them honestly with the pages that now outrank you, and improve those pages for readers. Wait until the update has finished rolling out before you judge anything.

Which Google updates happened recently?

Google lists confirmed ranking updates, with start dates and durations, on the Google Search Status Dashboard. As of late October 2026 the recent entries are:

Google also makes smaller changes all the time without announcing them. If your drop does not line up with an entry, do not assume an unannounced update; check the other causes below first.

Is it really the update, or something else?

Google's own guide to debugging traffic drops lists six main causes: algorithmic updates, technical issues, security issues, spam issues (including manual actions), seasonality and changing interests, and site moves or migrations. An update is only one of them, and the others are easier to fix.

Two data events in particular catch people out. Google stopped honoring the num=100 parameter in mid-September 2025, which cut reported impressions for many sites without changing clicks. And Google's Data anomalies page records a logging error that affected impressions, CTR and average position from May 13, 2025 to April 27, 2026; clicks were not affected. Both are covered in impressions up, clicks down: AI Overviews or something else.

How do you diagnose the drop, step by step?

1. Confirm the update has finished. Google's core updates guidance says to confirm the rollout is complete and to wait "at least a full week after a core update completes before analyzing your site in Search Console." Rankings bounce during a rollout.
2. Check the data is real. Open the Data anomalies page for your date range. Then compare Search Console clicks with your analytics organic sessions. If only analytics fell, fix the tag or consent setup, not your content.
3. Check for notices. In Search Console, open Security & Manual Actions. A manual action names the policy and has a review process; an algorithmic drop has neither.
4. Check indexing and crawling. In Page indexing, look for a jump in Excluded by noindex tag, Blocked by robots.txt, Server error (5xx) or Not found (404) that starts near your drop. In Settings, Crawl stats, look for falling crawl requests or rising response times. Inspect a few lost URLs with URL Inspection.
5. Compare the right periods. In Performance, Compare the week after the rollout ended with the week before it started, as Google suggests. Then compare the same 28 days year over year to rule out seasonality, using the 16 months of history Search Console keeps.
6. Read the pattern. If impressions and position fell, rankings changed. If impressions held and only clicks fell, Google says to look at your titles and snippets or at richer results from competitors; that is not an update loss.
7. Find the losers. On the Pages tab, sort by Clicks difference. Then on the Queries tab, do the same. Write down the top 20 of each.
8. Group them. Tag each lost page by template (blog, product, category, location), topic and age. Tag each query by intent (question, commercial, brand, local).
9. Look at who replaced you. Search five of the lost queries. Note what now ranks above you: forums, brand sites, government sources, video, an AI Overview, or competitors with deeper content.
10. Check broader demand. Use Google Trends on the main lost queries. If interest fell for everyone, your share may be unchanged.

What does the pattern of the loss tell you?

How do you assess content after a core update?

Google points site owners to its helpful, reliable, people-first content questions. Apply them to the pages that lost, side by side with the pages that won. A few of them, verbatim:

• "Does the content provide original information, reporting, research, or analysis?"
• "Is the content produced well, or does it appear sloppy or hastily produced?"
• "Is this the sort of page you'd want to bookmark, share with a friend, or recommend?"
• "Is it self-evident to your visitors who authored your content?"
• "Is the use of automation, including AI-generation, self-evident to visitors through disclosures or in other ways?"

The same page describes generating lots of text "without manual oversight or curation" as little to no effort. Be blunt with yourself: if the page that replaced you has first-hand testing, real photos, prices or a named expert and yours summarizes other articles, that is the gap.

Practical fixes that follow from the assessment:

• Merge thin pages on the same topic into one strong page and redirect the rest.
• Add first-hand evidence: your data, photos, tests, case details, prices, dates.
• Show who wrote or reviewed the page and why they are qualified, where readers would expect it.
• Remove or noindex pages that exist only to catch search variations.
• Update out-of-date facts and fix factual errors.

What if the drop lines up with a spam update?

Read Google's spam policies and check your site against the ones that most often hit ordinary businesses: scaled content abuse (many pages made mainly to rank), expired domain abuse, link spam, thin affiliation, and the site reputation policy, which covers third-party content "published on a host site mainly because of that host's already-established ranking signals." If you host sponsored or partner sections, review them.

Google's spam updates page says that once a site complies, its systems "learn over a period of months" that it does. For link spam updates, it adds that when the effect of spammy links is removed, any ranking benefit they gave is lost and does not come back. Buying more links is not a fix.

How long does recovery take?

Only Google can answer that, and its answer is careful. From the core updates guidance:

• Improvements can be reflected in days, but it can take several months for Google's systems to confirm a site is producing helpful content over the long term.
• If nothing changes after a few months, Google suggests waiting for the next core update.
• There is no guarantee that changes you make will produce a noticeable impact in search results.

So plan for a quarter, not a week. Make the changes that would make the page better for a reader even if there were no update, then measure on the same queries and pages 28 days at a time.

What should you not do?

• Do not change titles, URLs and content across the whole site during the rollout. You will not know what worked, and you may break pages that were fine.
• Do not disavow or delete links in a panic. Google's disavow links help page says most sites will not need the tool.
• Do not rewrite pages that still rank well. Google specifically warns against radical changes to well-performing pages.
• Do not trust a single third-party "visibility" chart over your own Search Console clicks.

SEO Rank Fixer keeps the boring part of this running: it checks your top pages every night and alerts you when one breaks, gets noindexed or starts losing clicks, flags decaying pages and queries, and in Advanced mode you can annotate update dates on your charts. For pages that slipped just off page 1, the playbook in fixing striking-distance pages applies, and a quick check with the free SEO checker catches the technical causes in a minute.