The November 2026 core update
On November 10 at 10:06 a.m. Pacific time, Google released the November 2026 core update. The status dashboard carries two short statements: the update "applies globally and to all languages", and the rollout "may take up to 2 weeks to complete". That puts the latest end date at November 24. As of today, November 14, it is still running.
This is the third core update of the year. The first started on March 27 and took a little over twelve days, the second started on May 21 and took just under twelve. The gap between the May update and this one was 173 days. Add four spam updates and one Discover update, and this is the eighth ranking entry on the dashboard in 2026.
Google has said nothing about what changed. On LinkedIn, Google Search Central calls it a regular update "designed to better surface relevant, satisfying content for searchers from all types of sites". The wording matches the March announcement. There is no blog post, no named system, and no named sector. Anyone claiming to know exactly what this update evaluates is guessing.
Turbulence before the start
Search results had been moving for weeks. Search Engine Roundtable reported unconfirmed volatility on October 16, October 20 and 21, and October 24, a larger wave from October 27 that lasted about a week, and renewed movement on November 8 and 9. The dashboard shows no entry at all between October 8 and November 10.
That matters for analysis. If you lost traffic in late October, the announced core update did not cause it. Whether Google ran tests ahead of the release, as some SEOs suspect, is speculation. What is certain: for many sites, a simple "before November 10 versus after" comparison starts from a baseline that was already unstable.
Why there are no winners and losers yet
Four days in, no reputable data provider has published a list of winners and losers. Sistrix states in its post on the update that there is no usable data yet and has scheduled its analysis for November 16. Lists that already advertise thousands of analyzed domains do not hold up. One of them cites data through November 17 and was published on the 10th.
Three measurement problems make this update harder to read than earlier ones:
- The sensors were already maxed out. According to an analysis by the German blog seo-kreativ, the Semrush Sensor for Germany showed daily values between 9.3 and 9.5 out of 10 from October 27 onward. The start of the update is not visible in it.
- Rank trackers are partly served altered results. The vendors Nozzle and DemandSphere report that since September Google has returned different results to automated queries than to real users in a share of cases. Nozzle cites more than 8 percent of analyzed cases, peaking above 28 percent. These are vendor figures, and Google has not commented.
- The Search Console AI report had a bug. Google confirmed that a logging error understated impressions in the generative AI performance report from November 9 to 11. That window lines up exactly with the start of the update.
The practical takeaway: a visibility index shows movement, not cause. Your own Search Console performance report remains the most reliable source, and even that needs careful reading this month.
The timing: right into Black Week
If the rollout runs to its last possible day, it finishes three days before Black Friday on November 27. For stores this is the worst timing of the year, because two effects overlap: rankings shift while demand rises seasonally. Higher organic revenue in late November therefore says little about the update, and lower revenue says just as little.
Google recommends waiting at least a full week after a core update completes, then comparing a week after it with a week before it started. November 3 to 9 works as the baseline week. If the update ends on November 24, the first clean analysis is possible on December 1 at the earliest, and that week includes Black Friday and Cyber Monday. We therefore also compare against the same calendar week of the previous year.
AI Overviews: the other reason clicks move
While the update rolls out, the results page itself keeps changing, and that often affects clicks more than a shifted position. Sistrix measures AI Overviews on more than 80 percent of its tracked keywords in the UK, with e-commerce sites now heavily exposed. In Germany, where we do most of our work, the share passed 50 percent on November 2 and reached 57.9 percent on November 6, up from 30 percent in July.
What that can do to clicks shows in an analysis by Glenn Gabe from France, where AI Overviews launched in July. One of the five sites he examined fell from roughly 750 to roughly 400 clicks per day, with click-through rate dropping from about 2 percent to 1.1 percent. Other sites in the same analysis were unaffected. It is a single case, not a market figure, but it shows the mechanism: same position, same impressions, fewer clicks.
Since November 12 a new Gemini model has also been running in Search. It is the new default in AI Mode and handles harder questions in AI Overviews. For definition queries, AI Overviews now reportedly appear fully expanded by default. In late October Google expanded ads in AI Mode to ten more English-language countries, with none of the EU member states among them. The basics on the AI report and the opt-out switch are in our fall SEO update.
What else changed
- AI training opt-out via robots.txt: on October 30 Google announced support for a shared signal from the IETF AIPREF working group that lets sites object to AI training. It is planned for 2027 and concerns training, not appearance in AI Overviews.
- Identifying search traffic: since November 12 there is dedicated documentation on recognizing visits from Google Search by referrer. It does not mention AI Mode or AI Overviews. How to count AI visits properly anyway is covered in our post on tracking AI traffic in GA4.
- Helpful content: in early October Google added sections on a page's main content and on effort, originality, talent, and accuracy to its documentation. It is the best available description of what core updates are meant to reward.
- Moving to a CDN: a new post explains how to absorb the crawl surge during a migration. The core message: do not block the real Googlebot, and if you must, answer with 429 or 503 for hours or one to two days at most.
- Pages not indexed: John Mueller commented again on "Crawled, currently not indexed". Usually, he wrote, it is a sign that Google's quality systems are unconvinced about the site as a whole. It is rarely a technical problem with one page.
What we are checking for clients right now
Four days into a running update there are no reliable results from client accounts, and we will not pretend otherwise. What we do for every site we manage in this phase is set up the measurement so that the analysis in early December gives a clear answer:
- Secure the baseline week: we export Search Console data for November 3 to 9, by page and by query, and add November 10 as an annotation in GA4 and in our reports.
- Split by page type: guides, category pages, product pages, and local pages are reviewed separately. Core updates rarely hit a whole site evenly, and the average hides exactly the group that matters.
- Split brand from non-brand: queries containing the company name almost always stay stable through updates. Leave them in and you notice losses too late.
- Read position, impressions, and clicks side by side: a falling position is a ranking loss. If position and impressions hold and only clicks fall, an AI Overview is very likely sitting above the result. These are two different problems with two different answers.
- Cross-check rank trackers: when a tool reports a crash, we verify it in Search Console before passing it on. With tool queries currently being distorted, that step is mandatory.
- Read the AI report with a footnote: the dip from November 9 to 11 in the generative AI report is a Google measurement error, not a loss.
- Rebuild nothing while the update runs: larger changes to content, site structure, or internal links move to December. Security updates and bug fixes continue as normal. Every change goes into the log with a date.
- Leave paid campaigns alone: Black Week planning in Google Ads and Meta stays as it is, regardless of organic swings. What changed there this fall is in our Google Ads update for October 2026.
We have been managing websites since 2010 and have worked through every core update in that time. The most expensive mistakes almost never came from the update itself. They came from hasty rebuilds in the first days after it. If you want a second opinion on your numbers, reach out via contact.
If you lost traffic
Google's own guidance is clearer here than many expect. For a small drop: "There's no need to take drastic action." For a large, sustained drop, check whether the site overall, and not just individual pages, delivers helpful content. Deleting content is described as "a last resort".
On timing, Google writes that it could take several months for its systems to confirm that a site as a whole has improved. According to Search Engine Journal, Gary Illyes gave three to six months as the typical range at a Google event in Barcelona in early October, and up to the next core update in the slowest case. Google has not published the slides, so the figure comes from attendee notes. As a planning assumption it is still more realistic than hoping for recovery within weeks. How we approach a loss is described on our SEO services page.
What we recommend now
- This week: save Search Console data for November 3 to 9 and note November 10 as the starting point.
- Until completion: observe, make no major changes, log what you do change.
- Black Week: run paid campaigns as planned and do not try to offset organic swings with budget.
- From December 1: analyze by page type, with brand and non-brand separated, and against last year as well.
- If you lost: first establish whether position or click-through rate fell. That decides whether content or visibility in AI answers is the issue. For the second, our GEO Checker helps.
FAQ
When did the update start and when does it end?
It started on November 10, 2026 at 10:06 a.m. Pacific time and should finish by November 24.
What did Google change?
Google has not said. It calls it a regular update to surface more relevant content.
When can I analyze it?
One week after completion at the earliest, so from December 1, compared with November 3 to 9.
How long does recovery take?
Several months according to Google. Three to six months was reported as the typical range.
Fewer clicks at the same position?
Then an AI Overview is usually the cause, not the core update.