Google started the November 2026 core update on 10 November. Its status dashboard says the rollout "may take up to 2 weeks to complete", which runs to 24 November, three days before Black Friday. Google's advice is to wait a full week after it finishes, then compare a week of Search Console data with the week before the update. This year that "full week" lands on Black Friday and Cyber Monday, when traffic jumps for reasons that have nothing to do with the update. Compare the weeks Google's way and seasonal growth can hide a real loss. This note gives you a way to strip the season out with last year's numbers, a rule for what to do with the result, and a calculator that runs it.
Key takeaways
- The rollout can run until 24 November. Until it ends, any change you see is unfinished, and any edit you make blurs the reading.
- Divide this year's change by last year's change over the same weeks. That gives you the update's effect with the holiday ramp taken out.
- Inside ±10% after adjustment, leave the site alone. Below −10%, run a full triage on the pages that lost ground.
01What is the November 2026 core update?
A core update is a broad change to how Google ranks pages, not a penalty and not aimed at any one kind of site. Google's Search Status Dashboard logged this one at 10:06 Pacific time on 10 November 2026, and says it applies worldwide and to all languages.
| Date (2026) | What happens |
|---|---|
| Tue 10 Nov | Core update starts |
| Tue 24 Nov | Latest finish if the rollout takes the full 2 weeks |
| Thu 26 Nov | Thanksgiving (US) |
| Fri 27 Nov | Black Friday |
| Mon 30 Nov | Cyber Monday |
| Tue 1 Dec | First day a full post-update week exists, if it finishes on the 24th |
It is Google's third core update of 2026. The March update took just over 12 days to roll out and the May update just under 12, so a finish shortly before Thanksgiving is likely.
02Why a week-on-week comparison fails in November
Google's core update guidance says to confirm the rollout has finished, wait "at least a full week" after it completes, and compare that week "with a week before" the update started. That works in a quiet month. In late November, the week after the update is the busiest shopping week of the year for many sites, so traffic rises whether the update helped you or not.
The fix is to measure how much your traffic normally grows across the same two weeks, using last year's Search Console data, and take that growth out. Search Console keeps 16 months of performance data, so last November is still there.
03The seasonal adjustment: one division
To make the weeks line up, go back 364 days, not one calendar year. That keeps Tuesday matched with Tuesday and Black Friday with Black Friday:
| Window | This year | Last year (364 days earlier) |
|---|---|---|
| Before the update | Tue 3 to Mon 9 Nov 2026 | Tue 4 to Mon 10 Nov 2025 |
| After the update | Tue 1 to Mon 7 Dec 2026 | Tue 2 to Mon 8 Dec 2025 |
If the rollout finishes later than 24 November, move both "after" windows forward by the same number of days. In Search Console, open Performance, set the date range to Compare, enter each pair, and note total clicks. Do the same with impressions if you want to see whether visibility or click-through changed.
04Worked example: one shop, two outcomes
A hypothetical online shop, clicks from Search Console:
| Before | After | Raw change | |
|---|---|---|---|
| Last year (2025) | 7,500 | 10,500 | +40% |
| This year, case A | 8,000 | 10,400 | +30% |
| This year, case B | 8,000 | 9,200 | +15% |
Case A: 1.30 ÷ 1.40 − 1 = −7.1%. Traffic grew 30%, but the shop normally grows 40% across these weeks. A 7% shortfall is inside the noise band. Change nothing.
Case B: 1.15 ÷ 1.40 − 1 = −17.9%. The raw number still says +15%, and on Google's week-on-week view it looks like a good month. Against its own seasonal pattern, the shop lost nearly a fifth of its search traffic. That is a real drop, and it would have gone unnoticed until January.
Decision rule
- Adjusted change between −10% and +10%: noise. Don't touch pages that rank.
- Below −10%: run the Google ranking drop triage on the same two weeks to find which pages and queries lost ground, and whether visibility or click-through fell.
- Above +10%: note which pages gained, and leave them alone. Don't let a winning page get rewritten for the sales.
- No data from last year (new site): use Google's week-on-week check, and treat any gain in late November as seasonal until December data proves otherwise.
Run your own numbers. The calculator opens with case A loaded:
- Raw change this year +30.0%
- Normal seasonal change (last year) +40.0%
Enter total clicks for each week from Search Console, Performance. "Before" is the week before the update started; "after" is the first full week after it ends. Match last year's weeks by going back 364 days so weekdays line up. Runs in your browser; nothing you enter leaves the page.
05What to do between now and Black Friday
- Freeze content on pages that rank. Google advises against "quick fix" changes during core updates. An edit made mid-rollout also makes it impossible to tell whether the update or your change moved the page.
- Do fix anything broken. Errors, pages dropping out of the index, slow checkout pages and broken product feeds have nothing to do with the update. Fix them the day you find them.
- Write down your dates now. Note when the rollout ends on Google's status dashboard, then pull your two pairs of weeks one full week later.
- Don't lean on search alone for the sale. If organic traffic carries your Black Friday, line up email and any paid campaigns now, so a mid-rollout dip doesn't cost you the week.
06When the numbers point to a real drop
A drop that survives the seasonal adjustment is a content and quality question, and the fix takes weeks, not a sale weekend. That is the work in Project Atlas, where I took a 25,000-post site from a C to a high A on PageSpeed, and in the technical audits I run before any content changes. If your adjusted number comes out below −10% in December, that is the SEO and site performance work I take on.
FAQFrequently asked questions
When did the November 2026 core update start?
Google started the November 2026 core update on 10 November 2026 at 10:06 Pacific time, according to its Search Status Dashboard. Google said the rollout may take up to two weeks to complete, which would put the latest finish on 24 November, three days before Black Friday.
How long should I wait before checking the core update's impact?
Google recommends confirming the update has finished, then waiting at least a full week before analysing your site in Search Console. If the rollout ends on 24 November, the first full week of data runs from 1 to 7 December 2026.
How do I separate the core update from Black Friday traffic?
Divide this year's change by last year's change over the same weeks. Take clicks for the week before the update and the week after it ends, then the same two weeks 364 days earlier. The result shows the update's effect with the usual seasonal rise taken out.
Should I change my content during the core update rollout?
Google advises against quick-fix changes during core updates and suggests not editing content that already performs well. Fix broken pages, indexing errors and speed problems straight away, but hold content rewrites until the rollout ends and the seasonally adjusted numbers show a real drop.
Sources
- Google Search Status Dashboard: November 2026 core update · retrieved 12 Nov 2026
- Google Search Central: Google Search's core updates and your website · retrieved 12 Nov 2026
- PPC Land: Google's core update shifts rankings for up to 2 weeks before Black Friday (10 Nov 2026) · retrieved 12 Nov 2026
Rollout dates come from Google's Search Status Dashboard as checked on 12 November 2026; the update may finish earlier or later. Past rollout lengths are as reported by PPC Land. The shop in the worked example is hypothetical.