Google confirmed the November 2026 core update on November 10, and as of November 18 it is still rolling out. If your rankings are moving, wait. A core update in progress is not a final result, and reacting now makes diagnosis harder, not easier.
The short version
- Google launched the November 2026 core update on November 10 and said it may take up to two weeks to complete, which puts the finish line around November 24.
- A core update that is still rolling out moves rankings up and down before they settle. Those swings are not your final position.
- Google's own guidance is that there is usually nothing specific to fix after a core update, and that you should wait for the rollout to finish before you assess anything.
- For most business-to-business software-as-a-service (B2B SaaS) teams, this rollout lands inside a Q4 change freeze. That is a reason to measure now and act in December, not a disadvantage.
Google confirmed it on November 10, and it is not done yet
The update is real, it is global, and it is still in progress as I write this. Google announced the November 2026 core update on November 10 and described it as a regular update designed to better surface relevant, satisfying content for searchers from all types of sites. The company also said the rollout may take up to two weeks to complete. Counting from the 10th, that points to completion around November 24.
You can confirm the live status yourself on the Google Search Status Dashboard, which logs the official start and end of every ranking update. Until that dashboard marks the rollout complete, treat everything you see in your rank tracker as provisional. Independent tracking tools reported their sharpest movement around November 13 and 14, per Search Engine Roundtable, which is normal for the back half of a two-week window. Provisional is the operative word.
A rollout is not a verdict
The single most common mistake I see is treating a mid-rollout ranking position as the outcome. It is not. Google is clear on this point. Its own documentation on core updates tells creators to wait for the update to be fully done rolling out before evaluating any change, because positions keep shifting until the end. A page that drops on day four can recover by day twelve without you touching a thing.
Google is also blunt about what a drop does and does not mean. A core update is not a penalty, and pages that lose visibility are not violating any spam policy. In Google's framing, there is often nothing wrong to fix. That reframes the whole exercise. You are not debugging a broken deploy. You are watching a reassessment of relevance play out, and the correct posture during a reassessment is to observe.
The middle of a rollout is the worst time to touch anything
Every change you ship right now poisons your own measurement. Say rankings dip on November 15, you rewrite three landing pages on the 16th, and positions recover on the 22nd. What recovered you? The rewrite, or the rollout settling? You cannot answer that, and now you have shipped changes you cannot attribute and may not have needed. I have watched teams churn an entire content sprint reacting to volatility that reversed on its own four days later.
This is not caution for its own sake. Attribution is the whole value of measurement. If you cannot tie an outcome to a cause, you have spent effort and learned nothing. During an active core update, nearly any change you make is confounded by the rollout, so you forfeit the one thing that would make the work worth doing.
The Q4 freeze is cover, not a problem
Here is the part most teams read as bad luck and I read as a gift. Most B2B SaaS organizations run a change freeze from roughly mid-November through the new year, locking production deploys around holiday traffic and thin on-call coverage. A core update rolling straight into that freeze feels like the worst possible timing. It is actually protective. The freeze is the rule that stops you from panic-shipping into a moving target.
When I run search for clients through a rollout, the freeze is the policy I am most grateful for. It turns do nothing from a hard discipline into a default. You are not fighting the urge to react, because the deploy pipeline is closed anyway. Use that. Let the freeze hold the line while the rollout finishes, and spend the window building the clean baseline you will act on in December.
What to actually do this week
Measure, annotate, and hold. In order:
Snapshot your data before Search Console reporting lags further. Export your Google Search Console performance data now, pull your rank-tracking positions, and grab Google Analytics 4 (GA4) landing-page sessions. Do this at the page-template level, not as a site-wide average. A site-wide line hides the only thing that matters, which is whether a specific page type gained or lost. Group pages the way you would score pages for a migration: by template and by business value, so you can see that, say, your comparison pages moved while your blog held.
Annotate the dates. Drop a marker on November 10 and the eventual completion date in GA4 and in whatever dashboard your stakeholders watch. When someone asks in January why traffic wobbled in November, the annotation is the answer.
Then hold. No content rewrites, no redirect changes, no title-tag experiments, no technical quick fixes aimed at rankings until the Status Dashboard says the rollout is complete. Routine, already-planned work that has nothing to do with chasing rankings is fine. Reactive changes are not.
When it settles, here is the clean sequence
Once the dashboard marks the update complete, you finally have a real signal to act on. Work it in this order. Confirm completion on the Status Dashboard. Compare settled positions against the snapshot you took this week, page type by page type, so you are reading movement and not noise. For the page types that genuinely lost ground, run Google's self-assessment questions from the core update documentation, which focus on content quality, originality, and experience, expertise, authoritativeness, and trustworthiness (E-E-A-T). Then ship improvements one change at a time, so the next measurement can actually tell you what worked.
That sequence is slower than reacting on the 16th. It is also the only version that teaches you anything.
What this does not cover
This is about core updates specifically, and core updates are their own animal. It does not cover spam updates, which target policy violations and do call for specific fixes. It does not cover a ranking drop caused by a technical problem, such as a botched redirect, a noindex shipped by accident, or a crawl block, which you should fix immediately regardless of any rollout. And it does not cover shifts in AI Overviews or AI Mode visibility, which move on their own schedule and need their own measurement. If you suspect a technical cause rather than the core update, stop reading and go check your server logs and index coverage.
FAQ
How long will the November 2026 core update take to finish?
Google said the rollout may take up to two weeks to complete. It began on November 10, so completion is expected around November 24, though Google can extend or finish early. The Google Search Status Dashboard is the only place that confirms the official end.
My rankings dropped during the rollout. Should I rewrite my content now?
No. Google advises waiting until the update finishes rolling out before you evaluate anything, because positions keep shifting until the end. A drop mid-rollout can reverse on its own. Snapshot your data now, hold changes, and reassess once it completes.
Is a core update a penalty?
No. Google is explicit that a core update is not a penalty and that pages which lose visibility are not violating any policy. It is a reassessment of how relevant and useful your content is relative to everything else, not a strike against your site.
We are in a code freeze. Are we at a disadvantage during a core update?
No, and arguably the opposite. Because you should not be making reactive ranking changes during a rollout anyway, a freeze simply enforces the correct behavior. Spend the window measuring so you are ready to act cleanly once the update settles.
How do I tell a core update drop from a technical problem?
A core update drop is gradual, is limited to search rankings, and lines up with the rollout window. A technical problem is usually abrupt and shows up in other signals: pages falling out of the index, crawl errors, a broken redirect chain, or a noindex tag. Check Search Console index coverage and your server logs first. If the pages are still indexed and crawlable, you are most likely looking at the core update.
If you want a second set of eyes on your rankings once this rollout settles, I run a page-level read-out that separates core-update movement from everything else so you act on signal instead of noise. Book a 20-minute session and we will look at your data together.