Did a Google core update hit my site? How to tell

To tell whether a Google core update hit your site, check the update’s start and end dates on Google’s Search Status Dashboard, wait at least a full week after the rollout finishes, then compare a week after it with a week before it started in Search Console’s Performance report. If the drop begins inside the rollout window, is spread across many pages and queries, and nothing on your side broke, the update is the likely cause. Google says core updates do not target individual sites, there is no specific fix, and recovery can take months.

A drop that coincides with an update is not proof of one, which is why the second half of the job, ruling things out, matters as much as the first.

When were the recent core updates?

Google lists confirmed ranking updates on its Search Status Dashboard, with a start date and a duration for each, in US Pacific time. These are the five most recent core updates as of 8 October 2026.

Update	Started	Listed duration
May 2026 core update	21 May 2026	11 days, 21 hours
March 2026 core update	27 March 2026	12 days, 4 hours
December 2025 core update	11 December 2025	18 days, 2 hours
June 2025 core update	30 June 2025	16 days, 18 hours
March 2025 core update	13 March 2025	13 days, 21 hours

Google says core updates happen several times a year, and that it also makes smaller core updates between them which are not announced because they are not widely noticeable. The dashboard lists other updates too. The September 2026 spam update began on 24 September 2026 with a listed duration of 13 days and 16 hours; spam updates target sites that violate Google’s spam policies, which is a different diagnosis with a different remedy.

Step 1: line the drop up with the dates

Open Performance → Search results, set the date range to the last 16 months, and look at clicks and impressions. Then narrow to three months around the suspected update.

You are asking one question: did the decline start inside the rollout window? A drop that began a week before the update started is not the update. A drop that began on the second day of a rollout and deepened over the following ten is consistent with it.

Two habits make this cleaner. Ignore the last two or three days of any chart, because Search Console data is finalised two to three days late and a partial day always looks like a drop. And mark the dates: right-click the Performance chart to add a custom annotation, up to 120 characters, so the next person to open the property sees “May 2026 core update starts” on the right day.

Step 2: compare the right periods

Google’s core updates guidance is specific: wait at least a full week after the update completes, then compare that week with a week before the rollout started. Comparing anything inside the rollout window measures a moving target.

Use Compare in the date filter, choose custom ranges, and match the weekdays: Monday to Sunday against Monday to Sunday. Then run the same comparison year over year. Search Console’s 16 months of history covers that for an update in roughly the last four months; for older ones you need an export saved at the time. If last year’s same weeks fell by a similar amount, you are looking at seasonality, and Google Trends for your main queries will usually confirm it.

Step 3: page level or query level?

Sort the Pages tab by clicks difference, then the Queries tab, and look at the shape rather than the list.

A drop concentrated in one or two pages is usually a page problem: a template change, a canonical that moved, a page that dropped out of the index. A drop spread thinly across dozens of pages and hundreds of queries, with positions slipping a few places each, is the shape a broad ranking change leaves. Check the search type filter too. Google’s guidance asks whether the drop happened in Web, Images, Video or News, because each can move separately.

Then look at the size. Google’s own example is that slipping from position 2 to 4 needs no drastic action, while falling from 4 to 29 calls for a deeper assessment.

Step 4: rule out what looks like an update

What you see	Likely cause	Where to check
Analytics sessions fell, Search Console clicks did not	Tracking or consent change	Your analytics setup
A sharp dip across unrelated properties on the same day	Logging issue on Google’s side	Google’s “Data anomalies in Search Console” help page, and system annotations on the chart
Indexed pages falling	Indexing problem	Indexing → Pages
A message about a manual action	Spam policy violation	Security & Manual Actions → Manual actions
Drop starts the day of a deploy or migration	Robots.txt, noindex, redirects, canonicals	URL inspection on the top lost pages
Same fall in the same weeks last year	Seasonality	Year-over-year comparison, Google Trends

The first row catches people out: the two tools count differently, and Search Console and GA4 never match for reasons that have nothing to do with Google’s rankings. If none of these fit and the timing does, you have a reasonable case for the core update. Write it down with the dates and the comparison you used, because the client will ask, and “it was the update” without evidence sounds like an excuse. Clicks dropped, now what walks through the page-by-page part of this investigation in detail.

What Google recommends if it was the update

Google’s guidance is short, and calmer than the urgency a drop tends to create.

For a small drop, take no drastic action, and avoid changing content that is already performing well. For a large, sustained drop, assess whether the site overall delivers content that is helpful, reliable and made for people, starting with the pages that fell furthest, and consider asking someone unaffiliated with the site for an honest view.

Avoid quick fixes. Google advises changes that make sense for users and are sustainable over the long term, and treats deleting content as a last resort.

Expect to wait. Google says it could take several months for its systems to recognise improvements, and that sometimes the effect does not show until the next core update. There is no guarantee that changes will produce a noticeable impact, which is worth saying to a client before they hear it from someone else.

Where QueryWatch fits

QueryWatch does not know when Google ships an update, and it does not annotate charts with them. What it does is make sure you notice a drop on the day the data is final rather than at the end of the month.

With Pro alerts on, a relay checks every six hours, compares the latest complete day with the same weekday over the previous four weeks, and pushes a notification when the move reaches 30 percent or two standard deviations, both adjustable per property, with at most one notification per property per day. Each alert stores an evidence snapshot: the observed value, the baseline, the dates and the top contributing pages at that moment. That snapshot is useful during a core update, because Search Console data shifts while you investigate, and a dated record of what moved first is what you want when you line it up against the dashboard. The alerts page has the details.

The change investigation, which shows the top three pages, queries, countries or devices behind any move on the free tier and twenty on Pro, covers Step 3 from your phone. Pro adds 16 months of history and period comparison for Step 2. QueryWatch is an independent app and is not affiliated with Google.