Google Core Updates redistribute rankings across the web -- sometimes massively. If your organic traffic dropped in the last 90 days, this audit process helps you understand why and what to do about it.
Step 1: Confirm It Was a Core Update (Not Something Else)
Traffic drops have multiple causes: seasonal demand shifts, crawl budget problems, manual penalties, algorithm changes, or Core Update impact. Before attributing any drop to a Core Update, rule out:
- Google Search Console manual actions (Search Console > Security & Manual Actions)
- Significant crawl errors in the Coverage report
- Server downtime during the suspected impact window
- Major site changes (redesign, URL restructuring, content removal) that coincided with the drop
If none of these apply and the drop aligns with a confirmed Core Update date, proceed with the analysis.
For a detailed breakdown of which site types were affected by the May 2026 Core Update and what signals drove recoveries: https://yositeup.com/blog/google-may-2026-core-update-analysis-who-was-hit
Step 2: Identify Affected Pages in GSC
In Google Search Console > Performance > Search Results:
- Set date range to cover 30 days before and 30 days after the Core Update date
- Click "Compare" and select the two periods
- Sort by "Clicks difference" (ascending) to find your biggest losers
- Export to spreadsheet
Pages with the largest click and impression drops are your primary focus for recovery analysis.
Step 3: Categorize the Drops
Group affected pages into categories:
- Informational content (what is X, how does X work): Most vulnerable to AI Overviews. Google's AI now answers many of these directly -- the page may still rank but get zero clicks.
- Comparison and list content (best X for Y, top tools for Z): Partially captured by AI. May need restructuring toward deeper analysis.
- Action-oriented guides (how to set up X, migration from X to Y): More AIO-resistant because users need step-by-step detail. Focus recovery effort here.
For what signals actually drive rankings vs. what has lost effectiveness: https://yositeup.com/en-us/blog/what-really-impacts-seo-in-2026
Step 4: Evaluate E-E-A-T Signals on Affected Pages
Core Updates consistently reward content with demonstrable Experience, Expertise, Authoritativeness, and Trust. For each significantly affected page, audit:
- Is there a clearly identified author with relevant expertise?
- Does the content cite specific sources, data, or firsthand experience?
- Is the page on a domain with topical authority in this subject area?
- Does the content go beyond what can be found in the top 10 results -- or does it synthesize existing information?
Pages that dropped are almost always ones where competitors have stronger E-E-A-T signals on the same query.
Step 5: Check What Replaced You
For your top losing pages: search the target query and analyze what now ranks in your former position. Are the ranking pages:
- More comprehensive (longer, more detailed, more specific)?
- From higher-authority domains?
- Better optimized for E-E-A-T (author bio, citations, original data)?
- Structured differently (FAQ, table, numbered steps)?
The gaps you identify become your content improvement priorities.
Step 6: GEO Signals for AI Overview Optimization
If your pages still rank but receive no clicks, AI Overviews may be capturing the query directly. This is a GEO (Generative Engine Optimization) problem, not a traditional ranking problem.
For a complete framework on getting content cited in AI Overviews, ChatGPT, and Perplexity: https://yositeup.com/blog/geo-generative-engine-optimization-2026
Recovery Timeline
Core Update recovery is not immediate. Google's guidance: improvements made after a Core Update may not be recognized until the next Core Update. Typical recovery windows:
- Technical fixes (crawlability, indexing): 2-4 weeks
- Content quality improvements: 2-6 months
- E-E-A-T signal building: 3-9 months
Prioritize action-oriented content over informational content for faster recovery -- AI Overviews capture the latter regardless of your ranking position.
Top comments (0)