Google's November 2026 Core Update Started Rolling Out on November 10: Global, All Languages, Up to Two Weeks, the Third of the Year — Leave Your Site Alone During the Rollout and Wait a Week After It Ends Before Reading the Data

Google's Search Status Dashboard shows that the November 2026 core update began rolling out at 18:06 UTC on November 10. It applies globally and to all languages, and the rollout may take up to 2 weeks to complete. A core update is a broad change to Google's ranking systems and does not target specific sites or pages, but rankings on almost any site can move during these two weeks.

What is confirmed so far

• This is the third core update of the year. The first two ran from March 27 to April 8 (12 days, 4 hours) and from May 21 to June 2 (11 days, 21 hours). By Search Engine Journal's count it is the 8th ranking update listed on the dashboard this year.
• On LinkedIn, Google called it a "regular update" designed to better surface relevant, satisfying content from all types of sites. Search Engine Journal notes that the wording matches the March update; Google named no specific objectives, and the Search Central blog has no separate post.
• Barry Schwartz of Search Engine Roundtable says the industry saw big ranking movements in the days before the official announcement. Google has not confirmed that.
• No end date has been published. Google says it will update the dashboard and its ranking release history page once the rollout is complete.

What not to do during the rollout

• Do not rush to change the site. Google's core update documentation is direct about this: a small drop (from position 2 to 4, for example) needs no drastic action, and Google recommends against changing content that is already performing well.
• Do not apply quick fixes. The documentation's example is removing a page element because you heard it was bad for SEO; Google advises changes that make sense for users and are sustainable, with deleting content as a last resort.
• Do not let the server misbehave in these two weeks. This one is our own advice: if the site also has timeouts or 5xx errors, you will not be able to tell afterwards whether a ranking change came from the algorithm or from your own availability problems.

When to read the data, and what to compare

Google's method is to confirm on the dashboard that the rollout has finished, wait at least a full week, and then compare that week in Search Console with a week before the rollout started, meaning the week before November 10. Look at web search, images, video and news separately. Only a sustained, large drop (the documentation's example is from position 4 to 29) calls for a self-assessment of the whole site. Search Engine Journal adds a point that is easy to miss: if this rollout takes the full two weeks, it ends around November 24, and the week right after it contains Thanksgiving, Black Friday and Cyber Monday, so a retail site comparing that holiday week with an ordinary week will get distorted numbers.

We described how to do a before-and-after comparison in our report on the end of the September spam update; rankings also move when there is no official update, and the way to diagnose that is in this article. How server location and response time actually affect rankings is covered in does server location affect SEO, and the setup for running your own rank-tracking tools is in choosing a VPS for SEO tools.