Google starts rolling out the November 2026 core update

Google began rolling out the November 2026 core update on 10 November and says it may take up to two weeks to complete. The update applies globally and to every language, so Australian sites are in it from the first day.

The Google Search Status Dashboard logs the start at 10:06 am US Pacific time, which was early on the morning of 11 November in eastern Australia. Google's Search Central account announced it on LinkedIn the same day: "This is a regular update designed to better surface relevant, satisfying content for searchers from all types of sites."

That is the same sentence Google used for the March 2026 core update. Neither the dashboard entry nor the LinkedIn post names a specific goal. The Search Central blog had no post on it when the update was announced, and Google's core updates help page still shows a revision date of 10 December 2025.

Search Console comparisons start a week after the rollout ends

Google's core updates documentation says to wait at least a full week after a core update finishes, then compare that week's Search Console data with a week from before the rollout began. For this update the baseline is the week before 10 November.

Rankings can move while a rollout is in progress, which is why Google tells site owners to hold off on reading Search Console until it is done. Google also says core updates do not target particular sites or pages; it describes them as a way to keep its ranking systems current as the content on the web changes.

Google says it will update the ranking release history page once the rollout is complete. The entry is already listed; when a duration appears next to it, that is the signal to start the one-week clock.

Separate Black Friday traffic from ranking losses

A full two-week rollout would finish around 24 November. The week after that includes US Thanksgiving, Black Friday and Cyber Monday, so Google's recommended comparison puts a peak sales week against an ordinary week in early November.

For any business that runs Black Friday or Cyber Monday offers, clicks and impressions in that week will be up for reasons that have nothing to do with the update. A ranking loss can sit underneath a seasonal gain and go unnoticed until December, when the promotional traffic falls away.

Two weeks is also an estimate. The last two core updates came in under it, at 12 days and 4 hours in March and 11 days and 21 hours in May. The December 2025 core update ran 18 days and 2 hours, and the November 2024 core update started on 11 November that year and took 23 days and 13 hours, finishing on 5 December. If this one runs long, the clean comparison week slides into December as well.

The Search Status Dashboard lists eight ranking updates this year

The dashboard lists eight ranking updates this year. Before this one came the February Discover update, a spam update and a core update in March, the May core update, and spam updates in June, August and September. November is the third Search core update of the year (February's was a Discover-only core update) and the first since the May update finished on 2 June, more than five months ago.

The spam updates in between were mostly quick. June took 2 days and 1 hour and August 2 days and 16 hours. September's ran 13 days and 16 hours, from 24 September to 8 October, and in its wake Search Console data delays of more than 64 hours left site owners judging that update on incomplete numbers until the report caught up.

Semrush readings ran high from 27 October

Volatility sensors run by rank-tracking tools showed movement well before 10 November. Semrush's sensor has scored 9.4 or 9.5 out of 10 every day since 27 October. On a combined chart that scales each tool from 0 to 100, Mozcast sat around 80 from 30 October to 2 November and SERPrecon hit 100 from 2 to 4 November. Nothing from Google connects that earlier movement to this update, and the dashboard lists no other ranking change since the September spam update ended.

Treat those sensors as a prompt to look and no more. Semrush said last month that Google sometimes serves poisoned results to rank trackers, pages that look normal but differ from what a person sees, which is one more reason to judge this update on your own Search Console clicks and on the enquiries that reach your phone and inbox.

Site owners need a Search Console baseline saved now

Google's method only works if the "before" numbers are fixed now. Done once, the later comparison is quick.

• In Search Console, note clicks, impressions and average position for 3 to 9 November, by page and by query, for the pages that bring enquiries or sales. Save the export so the comparison uses a fixed set of numbers.
• Check that the baseline week is clean. Search Console click spikes from 31 October to 2 November on some sites looked like bot traffic, with clicks up 2x to 6.5x while impressions stayed flat. If your site had them, check whether they continued into the following week.
• Add an annotation for 10 November in GA4 and any reporting dashboard, and another when the status dashboard marks the rollout complete.
• If you run Black Friday or Cyber Monday promotions, plan a second comparison: the same promotional week last year for total traffic, and a set of non-promotional queries for ranking position.
• Diarise a check one full week after the completion date, whatever that turns out to be.

Reactive page edits wait for the comparison

A page edited on day four of a rollout cannot be evaluated. If it recovers, there is no way to tell whether the edit did it or the update settled, and if it falls further the same problem applies in reverse. Hold any content or structural change that was planned as a reaction to this update until the one-week comparison is in.

Work that was already scheduled, such as new product pages or a Black Friday landing page, can go ahead. Only changes made because of a ranking swing need to wait, since the swing itself may not be there in two weeks.

If the comparison does show a loss, Google's advice for sites affected by a core update is to review their content against its core updates guidance. Core updates can also affect Discover traffic, so a site that gets Discover traffic should include it in the same before-and-after check.

Take the 3 to 9 November numbers today, add the annotation, and leave the site alone until the status dashboard shows a duration against the November 2026 entry. A week after that date is when this update can be judged.