Say your organic clicks went down a third between April and June and nobody changed anything on the site. Two things could have done that. Google ran a core update, or Google started answering your visitors’ questions in a paragraph above your pages. On the traffic chart the two look identical: a line that goes down and stays down. In Search Console they look like opposites, and the fix for one is the wrong move for the other.
A core update moves many pages at once, on dates Google publishes. An AI answer takes clicks from question queries while the rankings stay exactly where they were.
The signature of a core update
A core update changes how Google ranks pages. When it hits a site, three things move together.
Impressions and clicks fall together. The pages show up less often, so they get clicked less often. The ratio between the two barely changes.
Positions move. Pages that sat at 3 are at 8. Pages that sat at 8 are on page two. The average position in the main report gets worse, and when you open a query that lost clicks, the position column is the reason.
The dates match the dashboard. Google posts every core update on its Search Status Dashboard with a start date and a duration. The May 2026 update started on 21 May and ran twelve days. The six before it ran between six and 23 days each. Set the Search Console comparison to the week before the start date against the week after the end date. If that is where the step is, you have your answer.
It also hits every kind of page. Service pages, case pages and blog posts lose together, because the update changed how the site is judged, not how one type of question is answered.
The signature of an AI answer
When Google starts showing an AI answer above the results for a question your page used to answer, the pattern is the reverse.
Impressions hold and clicks fall. The page is still shown, often more than before, because it is now also a link inside the answer. People read the paragraph and do not click through.
Positions stay the same or improve. Google’s Performance report documentation says the AI answer occupies one position and every link inside it gets that position. A page that was third and is now also inside the answer can show a better average than before, with half the clicks.
There is no date. AI answers spread query by query over months. There is no step in the chart, just a slope.
Only certain pages lose. The pages that explain a term, a process or a timeline lose. Service pages and comparison pages do not, because there is no paragraph that answers “which firm should I hire”. When you sort the lost queries, they start with “what is”, “how long” and “how to”.
Since August the new AI tab in Search Console shows which of your pages appear inside AI answers. The Search Console cross-check puts that list next to the click change and makes the pattern visible in one export.
The ten-minute check
- Open the dashboard and write down the start and end dates of the last core update. In Search Console compare the week before the start with the week after the end. A step that lines up with those dates is a core update. A slope that does not is an AI answer.
- Look at impressions next to clicks for the same period. Both down is a core update. Impressions flat or up with clicks down is an AI answer.
- Sort the lost queries by position change. Positions that moved several places are a core update. Positions that held while clicks fell are an AI answer.
- Read the lost queries. A mix of service queries and informational queries is a core update. Almost only questions is an AI answer.
- Open the AI tab. If the pages that lost clicks are on that list, you are inside the answer and that is the state that produced the drop.
If it is the core update
Google’s own core update page is clearer than most of what is written about it. Confirm the update has finished rolling out. Wait at least a full week after it completes before reading Search Console. For a small drop, “there’s no need to take drastic action”, and Google recommends avoiding changes to content that is already performing well. For a large and sustained drop, go through Google’s self-assessment questions about whether the site is helpful and reliable, fix what fails and then wait, because Google also says it could take until the next core update to see the effect.
The wrong move is rewriting the pages that lost while the update is still rolling out. You will not know what changed because of you and what changed because of Google.
If it is the AI answer
Nothing on the site was demoted, so there is nothing to recover by ranking work. The question that page answers is now answered above it, and the clicks that left were mostly people who wanted the paragraph. What those clicks were worth and where to move the effort is in the pages AI answers took from you. The short version: stop counting those clicks as a target, move the work to the pages that answer a choice, and rewrite the informational pages so your link is the one inside the answer.
The wrong move is writing more pages like the ones that lost.
If it is both
It happens, and it is the case where most sites make the wrong diagnosis. The step in the chart gets blamed on the update, the slope underneath it gets missed, and the site waits for a recovery that half of it will never get. Run the check on the service pages and the informational pages separately. The service pages tell you about the update. The informational pages tell you about the answers. The AI side also differs by engine, which is why AI visibility is not one number.
Where this sits
This check is the first hour of any SEO consulting engagement that starts with a drop, because the two answers lead to two different plans and the wrong one costs a quarter. If your traffic went down and you are not sure which one did it, tell me when the drop started and I will tell you which of the two signatures it matches.