Traffic Dropped After a Core Update: 7-Day Triage
A 7-day triage worksheet for confirming a core update caused a traffic drop, measuring the size of the drop in Search Console, and running Google's self-assessment before rewriting anything.
Measuring content after AI search starts with telling causes apart. A core update, a lost snippet, a title that stopped earning the click and an AI Overview that cites someone else all look like the same falling line in Search Console, and each needs a different fix. These guides separate them: confirm the cause first, measure the size of the change against a clean baseline, and report AI visibility without claiming attribution the data cannot support.
My clicks fell or stopped correlating with impressions, and I need to measure and respond.
A 7-day triage worksheet for confirming a core update caused a traffic drop, measuring the size of the drop in Search Console, and running Google's self-assessment before rewriting anything.
When your page ranks in normal results but a competitor is cited in AI Overviews, check indexing eligibility, snippet quality, and subtopic coverage before rewriting the whole page.
In 80 days of our own daily Search Console data, our two most-tested new posts were shown for 126 to 290 broad queries at positions 40-70 for about five weeks, earned no clicks there, then were cut back to a trickle near positions 5-15.
Measure AI search traffic with observable data, proxy signals, manual checks, and a dashboard that avoids fake attribution.
Rewrite meta titles only after you know the page deserves a better title link. Match the title to the searcher’s task, make the page’s proof obvious, align the meta description with the first-screen answer, and avoid clickbait or promises that the rewrite will increase clicks. Use the before/after table to choose one safer, clearer title for one page at a time.
Use a Search Console diagnosis flowchart to decide whether no clicks come from rank, title, snippet, or intent before rewriting.