During a Google core update, keep improving pages when the change helps readers, but do not rewrite pages to chase daily ranking swings, and push a site migration to after the rollout if you can. Judge the impact only once Google marks the update complete, a full week later.
This guide is part of the SEO hub. A Google core update is a broad change to Google's ranking systems that, in Google's words, does not "target specific sites or individual web pages." The facts below reflect the November 2026 core update as of November 14, 2026, when the rollout was still in progress.
Which November 2026 Google core update facts are confirmed, reported or speculation?
For the November 2026 Google core update, only three facts are officially confirmed: Google released it on November 10, 2026, it applies globally and to all languages, and the rollout may take up to 2 weeks. Reported details come from trade press, and lists of winners and losers are speculation while the rollout runs.
The November 2026 Google core update is the third core update of 2026, after March 27 and May 21 on the dashboard's ranking history. The incident was posted on November 10, 2026 at 10:07 Pacific time, and as of November 14, 2026 the rollout is still listed as ongoing.
The facts carry different weight:
- Officially confirmed. The start date, the global scope and the window of up to 2 weeks.
- Reported. PPC Land reported that the update could run until November 24, 2026, and that Google's announcement on LinkedIn was three sentences long.
- Speculation. Which kinds of sites win or lose. Google publishes no target list for a core update, and any early winners and losers list is based on partial data from a rollout that is still moving.
Google describes core updates on its core updates page as changes it makes "several times a year," plus smaller core updates it does not announce.
Should you update articles while a core update is rolling out?
Yes, you can update articles while a core update is rolling out, as long as each change makes the page better for readers. Google gives no instruction to freeze content during a rollout. The edits to avoid are reactive ones, made because a page dropped or climbed a few positions on a given day.
Core updates can roll out in stages, so a page that slips early in a rollout can move again before the rollout ends, without any edit. Google's own core updates guidance advises against "quick fix" changes, such as removing a page element "because you heard it was bad for SEO," and asks for changes that make sense for users and hold up in the long term.
The Rollout Change Test is a simple rule for any edit during a rollout: make the change only if you would make it with no update running. It works for both directions of movement.
- Pass: fixing an outdated price, date or feature name, adding an answer readers ask for, correcting an error, publishing a planned new post.
- Fail: rewriting intros, cutting sections or changing titles on pages that moved this week, only because they moved.
Keep a dated log of every edit, so you can separate your own changes from the update later.
Should a site migration or rebuild wait until the rollout is complete?
A site migration is a move of a site to new URLs, a new domain or a new platform, and it should wait until the core update rollout is complete whenever the launch date can move. Google expects a migration to cause temporary ranking fluctuations on its own, and a core update adds more in the same weeks.
Google's site move documentation says to "expect temporary fluctuation in site ranking during the move" and that a medium-sized site can take "a few weeks or more" before Google shows the new URLs instead of the old ones.
If the migration cannot move, for example because a platform contract ends, run it anyway and document it well:
- Annotate the launch date in Search Console, next to the core update start and end dates.
- Keep the redirect map and a crawl of the old site, so you can check redirects page by page.
- Compare segments that the migration did not touch, such as a subfolder that kept its URLs, to see what the core update did on its own.
Treat a redesign that keeps every URL but changes templates with the same care, because content, internal links and layout then change on many pages at once.
Why did Generative AI impressions drop in Search Console on November 9 to 11, 2026?
The drop in the Search Console Generative AI performance report for November 9 to 11, 2026 comes from a logging error that Google has confirmed. The Generative AI performance report is a Search Console report that shows how a site performs in AI Overviews and AI Mode. It lowered reported impressions only, yet it overlaps the rollout start.
Google's data anomalies page states: "A logging error caused a decrease in impressions on the Generative AI performance report in Search for data from November 9 - November 11, 2026. This issue affects data logging only." Search Engine Roundtable reported on November 12, 2026 that affected properties see an annotation about the error in the report.
Because the dip overlaps the first day of the rollout, it can look like a ranking effect. Treat November 9 to 11 as missing data in that report. Google has fixed similar gaps before: the same page says data for an August 13 to 17, 2026 logging error was restored on August 21, 2026. No restore note exists for the November error as of November 14, 2026, so check the page again before you report on those dates. Two days after the core update started, Google also changed the model behind AI Mode, covered in Gemini 4 Hydrogen in Google Search.
How long does a core update rollout actually take?
A core update rollout is the period between the start Google announces and the completed status on the Search Status Dashboard, and it often takes longer than 2 weeks. On Google's own ranking history, 5 of the 9 core updates from March 2024 to May 2026 ran longer than 14 days, and the longest took 45 days.
Plan your hands-off period around the completed status, not a calendar date. The durations below come from the Search Status Dashboard ranking history, as listed on November 14, 2026.
| Core update | Start date | Rollout duration | Longer than 14 days |
|---|---|---|---|
| March 2024 | March 5, 2024 | 45 days | Yes |
| August 2024 | August 15, 2024 | 19 days, 4 hours | Yes |
| November 2024 | November 11, 2024 | 23 days, 13 hours | Yes |
| December 2024 | December 12, 2024 | 6 days, 4 hours | No |
| March 2025 | March 13, 2025 | 13 days, 21 hours | No |
| June 2025 | June 30, 2025 | 16 days, 18 hours | Yes |
| December 2025 | December 11, 2025 | 18 days, 2 hours | Yes |
| March 2026 | March 27, 2026 | 12 days, 4 hours | No |
| May 2026 | May 21, 2026 | 11 days, 21 hours | No |
| November 2026 | November 10, 2026 | Ongoing as of November 14, 2026 | Not yet known |
Rollouts also do not move evenly. PPC Land quoted John Mueller of Google saying in March 2026 that core updates sometimes "have to work step-by-step, rather than all at one time," and that Google generally does not announce those stages. For the November 2026 core update, a 2 week window ends around November 24, 2026, close to Black Friday on November 27, so ecommerce sites face seasonal demand changes in the same weeks.
How do you set clean baseline dates around the November 2026 core update?
Compare the first full week after the November 2026 core update completes with an equal week before November 10, 2026, in Search Console. Google recommends waiting at least one full week after completion, then comparing by page, by query and by search type. In the Generative AI performance report, use a baseline week ending November 8.
The steps follow Google's core updates guidance, with two additions for November 2026.
- Confirm completion. Check the Search Status Dashboard and write down the start and end dates.
- Wait one full week. Do not analyze until a full week after the completion date has passed.
- Compare two equal weeks. In the Performance report, compare that week with a week before November 10, 2026.
- Exclude November 9 to 11 for AI features. In the Generative AI performance report, use a baseline week that ends on November 8, 2026.
- Sort pages and queries by change. Separate small drops from large ones and check Web, Image, Video and News results separately.
- Check seasonality. Put the same weeks of 2025 next to the result, so holiday demand is not counted as an update effect.
As a hypothetical worked example: if the dashboard marks the update complete on November 24, 2026, the first full week after completion runs from November 25 to December 1. Compare it with November 3 to 9 for Web results, and with November 2 to 8 in the Generative AI performance report.
What does core update recovery require if a drop holds?
Core update recovery is the return of rankings a site lost in a core update. It needs a sustained, large drop to justify work, then sitewide improvements rather than quick edits to single pages. Google says a drop from position 2 to 4 needs no drastic action, while a drop from 4 to 29 needs a deeper assessment.
For that assessment, Google points to its helpful content self-assessment and asks whether a site overall is "delivering content that's helpful, reliable, and people first." It suggests asking people unaffiliated with the site to review it and looking first at the pages that lost most. Our guide to Google AI content guidelines covers the October 2026 changes to that guidance.
Recovery takes time. Google's core updates page says some changes take effect "in a few days," but it "could take several months" for its systems to confirm a site's quality, and sometimes that means "waiting until the next core update." Deleting content is a last resort in Google's guidance, meant for sections made for search engines rather than people. If a drop came with indexing problems, check Google indexing status before you rewrite anything.
Common mistakes during a Google core update rollout
The common mistakes during a Google core update rollout come from acting on incomplete data. Each one either changes pages for the wrong reason or makes the later comparison unreliable, and each has a fix that needs only the Search Status Dashboard, Search Console and some patience.
- Judging the update on day three. Mid-rollout positions often reverse. Wait for the completed status plus one full week.
- Reading the November 9 to 11 dip as a penalty. The Generative AI performance report drop is a confirmed logging error. Exclude those dates.
- Launching a migration mid-rollout without notes. Two sources of movement then share one chart. Move the date or annotate every step.
- Rewriting pages that only moved a few positions. Google's core updates guidance says a small drop needs no drastic action. Apply the Rollout Change Test: edit only what you would edit with no update running.
- Comparing unequal or seasonal periods. A November week against a December week mixes holiday demand into the result. Compare equal weeks and add the prior year. The Search Console guide shows how to set up the comparison.
- Ignoring AI features. Clicks can fall while rankings hold, for example when AI Overviews or AI Mode answer the query. Our overview of the Google AI Mode update explains what changed for links in AI Mode.
