Google's November 2026 Core Update Is Rolling Out. Don't Judge Your Rankings Before December
Google released its first core update since May on Nov. 10. We pulled every core update from Google's own status dashboard to see how long the last three took, and wrote a small script that tells you which two weeks to compare in Search Console.
Google released the November 2026 core update on Nov. 10, 2026 at 10:06 a.m. Pacific; it applies globally, to all languages, and may take up to 2 weeks to roll out.
It is Google's first core update since the May 2026 core update began on May 21, 173 days earlier.
On Google's Search Status Dashboard, the last three core updates took 18.1 days (December 2025), 12.2 days (March 2026) and 11.9 days (May 2026) to finish.
Google recommends waiting at least a full week after a core update completes before analyzing a site in Search Console, so the earliest fair read is likely in early December.
During the rollout, the most useful steps are to note the start date, leave stable pages alone, and avoid quick fixes based on a few days of movement.
Google released the November 2026 core update on Nov. 10, 2026. The Search Status Dashboard says the incident began at 10:06 a.m. Pacific, that the update "applies globally and to all languages," and that the rollout "may take up to 2 weeks to complete."
If you run a website, expect rankings and traffic to move over the next two weeks, in either direction. The most useful thing to do today is write the date down and not react to the first few days. Google's own advice is to wait until the rollout ends, and then a week more, before you judge what happened.
What did Google announce?
Only the essentials, on the Search Status Dashboard: the name, the start time (Nov. 10, 10:06 a.m. Pacific, which is 18:06 UTC), global scope, all languages, and a rollout of up to two weeks. The incident links to Google's standing documentation on core updates. There is no blog post describing what this update targets, which is normal for a core update: Google describes them as broad changes to how its systems assess content, not aimed at specific sites or pages.
It is the first core update since May 2026. Between the two, the dashboard lists three spam updates (June, August and September), but no core update.
How long does a Google core update take?
Google says up to two weeks this time. To see how that compares with recent updates, we pulled the dashboard's own incident history, which Google publishes as a JSON file, and measured each core update from start to finish:
Core update
Started
Finished
Days
December 2025
Dec. 11, 2025
Dec. 29, 2025
18.1
March 2026
March 27, 2026
April 8, 2026
12.2
May 2026
May 21, 2026
June 2, 2026
11.9
November 2026
Nov. 10, 2026
still rolling out
The two 2026 updates both finished in about 12 days. The December 2025 one ran past two weeks, to 18 days. So "up to 2 weeks" is a guide, not a promise. If this one follows the 2026 pattern, it would finish around Nov. 22; if it runs like December's, around Nov. 28.
The history file currently goes back to December 2025, so these are the only three earlier core updates in it.
When should you check your traffic?
Google's core updates page recommends waiting "at least a full week after a core update completes" before analyzing your site in Search Console, then comparing that week with the week before the rollout started.
For this update, the week before the rollout is Nov. 3 to Nov. 9, 2026. The week after depends on when Google marks it complete. If it finishes on Nov. 24, two weeks after it started, the first full week after is Nov. 25 to Dec. 1, and the comparison can be made on Dec. 2. Anything you see before then is a rollout in progress.
Two cautions for this particular comparison:
Thanksgiving week. Nov. 26 falls inside that likely "after" week. For many US businesses, a holiday week looks different from a normal week anyway. Compare against the same week last year as well, or wait one more week.
Search types. Google suggests checking Web, Image, Video and News separately, since a drop can sit in only one of them.
The script we use to get the dates right
We wrote a short Node.js script (Node 18 or later, no packages) that reads Google's dashboard history and prints each core update, how long it took, and the two weeks Google's advice points to. Run it again once Google marks the November update as finished, and it will print that update's windows too.
// core-updates.mjs: node core-updates.mjsconst DAY = 864e5;const iso = (d) => d.toISOString().slice(0, 10);const res = await fetch('https://status.search.google.com/incidents.json');const incidents = await res.json();for (const i of incidents.filter((x) => /core update/i.test(x.external_desc ?? ''))) { const begin = new Date(i.begin); const startDay = new Date(iso(begin)); console.log(`\n${i.external_desc}: began ${iso(begin)}`); if (!i.end) { console.log(' still rolling out'); continue; } const end = new Date(i.end); const endDay = new Date(iso(end)); console.log(` finished ${iso(end)}, ${((end - begin) / DAY).toFixed(1)} days`); console.log(` before: ${iso(new Date(startDay - 7 * DAY))} to ${iso(new Date(startDay - DAY))}`); console.log(` after: ${iso(new Date(+endDay + DAY))} to ${iso(new Date(+endDay + 7 * DAY))}`);}
When we ran it on Nov. 10, it printed the table above and these windows for the May update: before, May 14 to May 20; after, June 3 to June 9. The dates are in UTC, and Search Console reports days in Pacific time, so treat the edges as approximate. If you have our weekly Search Console report in Python, plug the two windows into it to get the comparison by page and query.
What to do during the rollout
Our view, based on Google's guidance and on how core updates have played out this year:
Mark Nov. 10 in your analytics and reporting. An annotation now saves an argument later about why traffic moved.
Leave stable pages alone. Google's page says that if a drop is small, you shouldn't make radical changes, and that pages still performing well don't need changing. Rewriting during the rollout also makes it impossible to tell what the update did and what your edits did.
Keep publishing as normal. New posts and routine fixes are fine. What to avoid is a reaction: mass rewrites, deleted pages, changed titles across a section.
Watch the bigger picture. A position change of a few places on a few queries during a rollout is noise. A sustained drop across many pages after the rollout ends is the signal Google says to investigate.
If you redesigned or migrated recently, check that first. A site change in the same weeks will look like a core update hit. Our checklist for rankings that dropped after a redesign covers what to rule out.
What if traffic drops after the update?
Google's advice for a large, lasting drop is to step back and assess the site as a whole against its helpful content questions, ideally with someone unaffiliated with the site giving an honest read, and to look closely at the pages that lost the most. It warns against quick fixes, and says deleting content should be a last resort.
It is also honest about timing: some improvements show within days, but it "could take several months" for Google's systems to confirm them, and sometimes the next core update is when a recovery shows. That is a reason to make changes you would keep anyway, not changes aimed at this one update.
What we don't know yet
What this update changes. Google hasn't said, and it usually doesn't for core updates. Claims that it targets a specific kind of site, AI content or a ranking factor are guesses until Google says otherwise.
Whether AI Overviews and AI Mode are affected. The incident lists "Ranking" as the affected product. Google hasn't said anything about its AI features in this update.
When it ends. We'll update this story when the dashboard marks it complete.
Kiran runs Kihan Marketing, a web design, SEO and ads agency, and manages dozens of websites across real estate, home services and healthcare. He writes about SEO, AI search and paid ads news, and what it means for the people who run websites.