How to Tell If a Google Update Hit Your Site
A drop that lines up with a Google update is not proof the update caused it. The order to check things in, the dates to compare, and how much movement is normal anyway.
To tell whether a Google update hit your site, compare the same pages over the same number of days before the rollout started and after it finished, and only call it the update once you have ruled out your own changes and normal drift. Google's own advice is to wait "at least a full week after a core update completes before analyzing your site in Search Console", then compare "this week with a week before the core update started rolling out".
That last part matters right now. Google's Search Status Dashboard shows the November 2026 core update starting on 2026-11-10, and as of 2026-11-14 it has not finished. Anything you read before it completes is a rollout in progress, not a result.
TL;DR:
- Take the start and end dates from the Search Status Dashboard. Wait a week after the end, then compare equal windows before and after.
- Check your own site first. In one drop we measured, 80% of a site's impressions went in the week after a core update finished, and the five pages that carried most of the loss had all been redirected.
- Measure against normal drift. Pages move a few places a month with nobody touching them, and the further down they start, the more they move.
- You can only compare against a period you still have. Search Console keeps 16 months.
When did the update run?
Google lists every confirmed ranking update on the Search Status Dashboard, with the day it started and the day it finished. The recent ones:
- November 2026 core update: started 2026-11-10, still rolling out on 2026-11-14.
- September 2026 spam update: 2026-09-24 to 2026-10-08.
- August 2026 spam update: 2026-08-18 to 2026-08-21.
- June 2026 spam update: 2026-06-24 to 2026-06-26.
- May 2026 core update: 2026-05-21 to 2026-06-02.
- March 2026 core update: 2026-03-27 to 2026-04-08.
- December 2025 core update: 2025-12-11 to 2025-12-29.
Note the type as well as the dates. A core update re-ranks sites against each other; Google says core updates "don't target specific sites or individual web pages". A spam update is about whether pages break Google's spam policies. They call for different responses, and a drop during a spam update is the one where reading those policies against your own pages is the first job.
Which dates should you compare?
Equal windows on either side of the rollout, made of whole weeks:
- Before: the week, or the four weeks, ending the day before the rollout started.
- After: the same number of days, starting a week after the rollout finished.
- Skip the rollout itself. Rankings move during it, and a reading taken in the middle is a reading of a moving target.
Whole weeks matter because weekdays and weekends behave differently. A window that starts on a Monday against one that starts on a Saturday can show a swing that is only the calendar.
In the Performance report, open the date filter, choose Compare, and set the two windows. Read the site and page totals for volume, because those count every click; the per-search rows leave out rare searches, so they never add up to the totals. Page-level vs query-level data explains the gap.
How big is the drop?
Google draws the line with two examples: a "Small drop in position (dropping from position 2 to 4)", where "There's no need to take drastic action", and a "Large drop in position (dropping from position 4 to 29)", where you should "Do a deeper assessment".
Read it per search, not only per site. A site total can fall because one large search fell while everything else held, and that is a different problem from every page sliding a little. Sort your pages by clicks lost and check whether the losers share anything: a template, a topic, a type of page.
Google also suggests splitting by search type: "This can help you understand whether the drop you've seen happened in Web Search, Google Images, Video mode, or the News tab."
Try it
Point an SEO agent at your own site, not just an essay about one.
QueryScope holds the plan for your site, reads your real Search Console, and hands the coding agent you already have one change at a time to rank for the searches you decided to win. From $49/month, everything included.
Did you change something at the same time?
Check this before you blame Google, because it is the cause you can undo. We measured one site that lost about 80% of its impressions in April, in the week after the March 2026 core update finished. The timing pointed at the update. Every one of the five pages that carried most of the drop had been redirected. The update was a coincidence.
Run the same checks on the pages that lost the most:
- Do they still return 200, or do they redirect or 404?
- Is there a noindex in the HTML or the
X-Robots-Tagheader? - Does the canonical still point at the page itself?
- Did anything ship in the same weeks: a migration, a new template, a change to internal links, a robots.txt edit?
A page that left the index for one of those reasons is covered in why a page drops out of Google's index. Also check Google's data anomalies in Search Console page: when Google changes how it logs data, a graph can step down with nothing wrong on your site.
How much would it have moved anyway?
More than most people expect. We took 2,692 pairs of a search and the page ranking for it, read across two back-to-back 28-day windows with no change recorded on the page. The median move was 0 places for searches starting in the top 3, 1.2 places from 3 to 10, 2.7 places from 10 to 20, and 5.6 places past 20. Why Google rankings fluctuate has the full measurement.
So a search that went from 14 to 17 across an update has done what an untouched search starting there does in an ordinary month. A search that went from 4 to 29 has not. The update is a reasonable explanation for the second and no explanation at all for the first.
The same applies to the pages that went up. A climb during an update is drift until it clears the same bar.
Why you need the history from before
Every comparison above needs the before window, and Search Console keeps 16 months. Comparing this November against last November, to separate the update from the season, needs a year of data. An update from a year and a half ago can no longer be read at all: its before window has already been deleted. Search Console history covers the limit and the only fix for it, which is keeping your own copy from today on.
What to do once you know
If it was the update, Google's advice on core updates is to look at the site as a whole rather than patch the pages that fell, and to expect it to take time: "some changes can take effect in a few days, but it could take several months". If it was decay on one page rather than the site being re-ranked, the response is different again, and content decay detection covers how to tell the two apart.
Either way, do not edit the pages that fell while the rollout is still moving them. A change made mid-rollout is measured against a baseline that is moving underneath it, so you will never know whether it helped.
Reading updates without doing it by hand
QueryScope keeps daily Search Console history for your site past Google's 16 months, reads the confirmed update dates from Google's own feed, and when a drop costs clicks it checks the causes in the order above: a page the live site shows a reason for, then your own recorded changes, then a confirmed Google update, then a reporting fault Google logged. When a drop lines up with an update, it holds new edits until a week after the update finishes, so nothing you change is measured against rankings that are still moving. It reads your Search Console and stops at the click.
Sources
- Google Search Central, Google Search's core updates and your website ("We recommend waiting at least a full week after a core update completes before analyzing your site in Search Console"; comparing "this week with a week before the core update started rolling out"; small drop "dropping from position 2 to 4" against large drop "dropping from position 4 to 29"; splitting by search type; core updates "don't target specific sites or individual web pages"; "some changes can take effect in a few days, but it could take several months").
- Google Search Status Dashboard, ranking updates history, read 2026-11-14 (start and end dates of the updates listed).
- Search Console Help, Data anomalies in Search Console.
- QueryScope's measurements of ranking drift and of a site-wide drop, published in Why Google rankings fluctuate.
Try it
Put an SEO agent in your editor.
Ask your coding agent what to work on. QueryScope reads your real Search Console, holds the searches you decided to win, and hands back one move at a time with the proof it worked. From $49/month, everything included. 1, 3 or 10 sites.