Google's core update puts your comparison week on Black Friday
Summary
Google's November core update started on 10 November, and Google's own advice for reading the results points at a comparison week that falls on Black Friday.
Export the Search Console data for the week before the rollout now, and for retail compare the holiday week with the same week a year earlier.
Google released the November 2026 core update on 10 November, according to the Search Status Dashboard. The dashboard entry says the update applies globally and to all languages, and that the rollout may take up to two weeks to complete. It is the third core update of the year, per Search Engine Journal’s report.
Two weeks from 10 November puts the finish around 24 November, and that is where the measurement problem starts. Google’s core updates documentation recommends waiting at least a full week after a core update completes before analyzing a site in Search Console, then comparing that week against a week before the rollout started. For a US retailer, the week after 24 November holds Thanksgiving, Black Friday and Cyber Monday. Following that instruction literally means holding peak shopping traffic against an ordinary early-November week, and the swing it produces says more about the calendar than about ranking.
The baseline is the part worth fixing today, while it is still intact. Google’s advice points at 3 to 9 November, a week that has already finished. Export it now, and annotate the 10 November start date in whatever reporting the team opens. For retail, the readable version of the post-rollout comparison is the same holiday week a year earlier, with the pre-rollout week kept as the anchor for everything not tied to shopping.
Site-wide click totals can hide the movement that matters. Google counts clicks from AI Overviews inside the same Search total as classic results, so a total that holds roughly flat can sit on top of real movement underneath it. Splitting branded from unbranded queries, and watching the few query groups that carry revenue rather than the site line, is what makes a shift visible at all.
The rollout window is a bad time to change anything the team intends to measure. Rankings can move while a core update is still deploying, and an edit made inside that window cannot be separated afterwards from the update’s own effect. Reverting is not a clean undo either: one site that pulled a mistaken noindex did not see its pages come back on the way out.
Google’s two-week estimate has held this year. The May core update ran 11 days and finished on 2 June, and the March one ran about 12 days. Google says it will update its ranking release history page once the November rollout is done, and that notice, not the volatility trackers, starts the clock on the one-week wait.
What to do
- Annotate 10 November in Search Console, analytics and any client reporting today, and export the 3 to 9 November Search Console data as the baseline.
- Wait for Google to mark the rollout complete, then wait a further week before reading anything. A drop seen on day four may not be there on day fourteen.
- Freeze changes you plan to measure. Routine publishing continues; a template change, a canonical rewrite or an internal linking overhaul can wait two weeks.
- Segment by query group before comparing, and for retail use a year-over-year holiday week instead of Google’s suggested pairing.
SE Roundtable’s write-up makes a point worth holding onto past 24 November: core updates reach Discover and featured snippets too, and Google runs periodic refreshes of this algorithm that it may not announce. Movement in December will not necessarily belong to this update, which is another reason the annotated start date matters more than the trackers.