Google’s November 2026 core update is live. It started rolling out on Tuesday, November 10, 2026, at 10:06 a.m. Pacific time (1:06 p.m. Eastern), it applies globally and to all languages, and Google says the rollout may take up to two weeks to complete. If it runs the full two weeks, it finishes around November 24 — three days before Black Friday.
That is the whole announcement, more or less. Google logged one line on its Search Status Dashboard — “Released the November 2026 core update, which applies globally and to all languages. The rollout may take up to 2 weeks to complete.” — and posted on LinkedIn that it is “a regular update designed to better surface relevant, satisfying content.” Search Engine Land’s coverage of the announcement confirms the same timeline. Google has not said what changed, which kinds of sites it affects, or what it is trying to reward this time. Nobody outside Google knows yet, and anyone who tells you otherwise is guessing.
So what should you, a blogger, actually do? The honest answer is mostly: nothing, yet. But “nothing” is a specific kind of nothing — a disciplined two-week hold, a careful way of watching your data, and a short list of things to check once the dust settles. This piece is that list.
What Google actually announced
Let’s get the facts straight first, because the first 48 hours of any core update are when the worst information spreads fastest.
- Start: November 10, 2026, 10:06 a.m. PT / 1:06 p.m. ET, per the Google Search Status Dashboard.
- Scope: Global, all languages. This is the first core update of 2026 where Google used that exact “globally and to all languages” phrasing in the announcement.
- Duration: Up to two weeks. A full-length rollout ends around November 24, 2026.
- What changed: Google hasn’t said. There is no Search Central blog post about it, no new guidance, and no named system or signal.
- Where it sits in 2026: This is Google’s third core update of the year, after March 27–April 8 and May 21–June 2. The dashboard’s ranking history lists eight ranking updates in 2026 in total; this is the eighth.
One more fact that matters to readers of this site: our own article from November 9 said there was no November update yet. That was true on November 9. It stopped being true the next afternoon. We are correcting that piece and pointing it here — and I would rather tell you that plainly than quietly edit it and hope nobody notices. If a site you follow never corrects its own stale calls, that tells you something about how it treats the rest of its advice.
Why the timing stings
A core update landing on November 10 is not an accident of the calendar — Google does not schedule updates around your content calendar — but the timing is genuinely awkward for anyone whose income depends on search traffic in November.
Thanksgiving falls on November 26 this year. Black Friday is November 27, Cyber Monday November 30. A rollout that ends on November 24 finishes two days before Thanksgiving and three days before the biggest shopping weekend of the year. That means rankings are still moving while gift guides, deal roundups, and holiday content are supposed to be doing their best work of the year.
There is nothing you can do about the calendar. What you can do is refuse to make it worse. The single most expensive mistake bloggers make during a core update is treating a mid-rollout wobble as a verdict and “fixing” pages that were never broken. A rewrite made on November 14, based on three days of noisy data, can still be hurting a page in January, long after the update has finished and the original version would have recovered.
Rule one: do nothing for the first two weeks
Google’s own core update guidance has said the same thing for years, and it is worth quoting because it is the opposite of what your anxiety will tell you to do: wait until the rollout is confirmed complete, then wait at least one more full week before you judge the impact.
That is a minimum of three weeks from November 10 before any honest assessment is possible. The earliest date you can fairly evaluate this update is around December 1 — and even then, only if the rollout finished on schedule.
Here is what “do nothing” actually means in practice:
- Don’t rewrite articles because they slipped three positions on a Tuesday. Positions move during rollouts as Google tests the new ranking. A page that drops on day four can be back — or higher — by day twelve.
- Don’t delete or noindex pages that lost traffic this week. A traffic dip during a rollout is not a quality verdict; it is a system in motion.
- Don’t change your internal linking, your titles, or your site structure in response to a single day’s data. Site-wide changes made mid-rollout are impossible to attribute afterwards. If traffic recovers, you will not know whether your change helped or the rollout finished.
- Don’t buy a “core update recovery” service. There is no such service. Nobody outside Google knows what this update changed, which means nobody can sell you a fix for it. Anyone offering one this week is selling confidence, not knowledge.
- Do keep publishing. A core update is not a reason to stop. Fresh, useful content published during a rollout gets evaluated under the same new ranking as everything else. The bloggers who come out of updates strongest are usually the ones who kept shipping.
The exception to “do nothing” is a genuine technical problem: if your site goes down, if pages start returning errors, if your sitemap breaks — fix that immediately. That is not update response; that is site maintenance, and it was urgent before November 10 too.
How to read Search Console during a rollout
You should be watching your data. You should not be reacting to it yet. There is a difference, and it comes down to how you compare.
Set your baseline before the update
Google’s guidance is specific: once the rollout is complete, wait at least a full week, then compare that week’s Search Console data with a week from before the rollout began. For this update, your baseline is the week before November 10 — roughly November 2 to November 9.
If you have not already, screenshot or export that baseline now. In Search Console, go to Performance, set the date range to November 2–9, and note total clicks, total impressions, average click-through rate, and average position. (If you are still learning the tool, our guide to Search Console’s new reports walks through the current layout.) Do the same for your top 20 pages individually. You will want those numbers in December, and reconstructing them from memory is how people convince themselves a 4% dip was a 40% collapse.
Compare by page type, not by day
Daily numbers during a rollout are noise. A page that loses 30% of its clicks on a Wednesday and gains them back on Friday has told you nothing except that the rollout is still rolling. The comparisons that mean something are:
- Week over week, after the rollout ends. One full week after completion versus your pre-rollout baseline week.
- By page type, not by single page. Group your pages: how-to guides, product roundups, news pieces, opinion posts, category pages. If one type dropped and the rest held, that is a signal. If everything dropped 5%, that is weather.
- Clicks and impressions together. A page whose impressions fell but whose click-through rate held steady lost visibility, not appeal — different problem, different fix. A page whose impressions held but whose CTR fell may have a title or snippet problem, which is a page problem, not an update problem.
- Position bands, not exact positions. A page moving from position 4 to position 7 matters. A page moving from 11.2 to 12.8 in average position does not, and the decimal will lie to you about it.
What a real drop looks like
A real core-update impact has a shape. It is not a bad day; it is a step change that holds after the rollout ends and survives the one-week waiting period. We covered how to tell a real traffic swing from noise in this diagnosis checklist, and the pattern to look for in early December is the same one:
- A sustained drop of 20% or more in clicks on a group of similar pages, lasting a full week after the rollout finished, while the rest of the site is roughly flat.
- The drop shows up in impressions too — the pages are simply being shown less, not clicked less.
- The affected pages share something: a topic, a format, a depth level, a publishing era. Random pages dropping at random is noise. A cluster is a signal.
If you see that shape, then — and only then — you have something to work on. And the work is the unglamorous kind: read the affected pages as a stranger would, ask whether each one genuinely answers its query better than the pages now outranking it, and improve the weakest ones. Google’s guidance on core updates has never changed on this point: there is no single fix, because a core update is not a penalty. It is a reassessment, and the response to a reassessment is better content, not a trick.
If, on the other hand, your traffic is down 8% for three days in mid-November and back by the weekend, you experienced a rollout. That is all. File it under “weather” and move on.
What not to do: the panic checklist
I have watched bloggers react to core updates for years, and the same five mistakes show up every time. They all feel productive in the moment. They all make things worse.
1. Rewriting your best pages first. The pages that dropped are usually your most important pages, so they attract the most panic. They are also the pages most likely to recover on their own, because they have the most history, the most links, and the most engagement behind them. Leave your winners alone until December.
2. Chasing the “what changed” rumor. Within days of any core update, someone publishes a confident theory: it is about AI content, it is about forums, it is about E-E-A-T, it is about freshness. Some of these theories will be right about some sites. None of them will be verified this week. Wait for the rollout to end, then look at your own data before adopting anyone’s theory about your site.
3. Adding more words to thin pages. A 900-word article that dropped does not need to become a 2,500-word article. It needs to answer its query better. Sometimes that means more words. Sometimes it means a clearer answer, a better example, or a table instead of three paragraphs. Word count is not a ranking factor; usefulness is.
4. Disavowing links or removing pages. Disavow files and mass deletions are for real problems — spam, hacked content, pages that should never have existed. They are not a response to a ranking wobble, and they are very hard to undo cleanly.
5. Announcing the update “killed” your site on day three. Besides being premature, it locks you into a story. If traffic recovers, you have cried wolf to your audience. If it does not, you have spent the two weeks that mattered most on narrative instead of on the work.
The quality reminder — and why it is not a platitude
Every core update announcement comes with the same advice from Google: focus on content that is helpful, reliable, and people-first. Bloggers roll their eyes at this because it sounds like a non-answer. It is a non-answer in one sense — it does not tell you what changed — but it is the only answer that has ever held up across updates, because core updates are, by definition, broad reassessments of quality.
In practical terms, for a small blog, “helpful, reliable, people-first” cashes out as a short list of things you can check on any page in five minutes:
- Does the first paragraph answer the question, or does it warm up for 200 words first?
- Could a reader follow the advice on the page and get the result it promises?
- Are the facts on the page current — prices, dates, requirements, links that still work?
- Does the page say something the top ten results do not, or is it a competent restatement of the same five points?
- Would you send this page to a friend who asked the question, or would you be slightly embarrassed?
If a page fails two or more of those checks, it is a candidate for improvement — not this week, but in December, once you know whether it actually lost ground. If it passes all five, leave it alone and let the rollout finish. The pages that pass that test are the ones core updates tend to reward over time, even when they wobble for a fortnight first.
What to do after November 24
Put a date on your calendar now: December 1, 2026. That is the first day you can fairly assess this update, assuming the rollout ends around November 24 and you give it the full week Google recommends. On that day, run this checklist:
- Confirm completion. Check the Search Status Dashboard. Google posts a completion notice when the rollout ends. Do not start your assessment until you see it.
- Pull the comparison. One full week after completion versus your November 2–9 baseline. Total clicks, impressions, CTR, average position — site-wide, then by page type, then your top 20 pages.
- Sort pages into three buckets. Winners (up 20% or more), flat (within 10% either way), losers (down 20% or more for a full week). Ignore everything in the middle; it is noise.
- Read your losers. Not their analytics — the pages themselves. Compare each one with the pages now ranking above it. Ask what the reader gets there that they do not get from you.
- Fix the smallest real problem first. One page, one improvement, then watch it for two weeks. Site-wide overhauls based on one update are how bloggers break sites that were fine.
- Write down what you found. A one-page note — what dropped, what rose, what you changed, what happened next. The next core update will come, probably in early 2027, and your future self will be grateful for a record that is not a memory.
And if nothing much changed — if your traffic is within a few percent of baseline in December — that is also a result, and a good one. Most sites, in most core updates, move a little or not at all. The update is a reassessment, not a cull.
A note on our own coverage
I mentioned this at the top, and it is worth repeating at the bottom because it is the whole point of how a blog should behave during an update: on November 9, this site published a piece saying there was no November core update yet. On November 10, Google released one. The old piece is being corrected with a note pointing here, not quietly rewritten to pretend we knew.
That is the standard I would hold any site to during a rollout. If a source you follow gets a call wrong and never says so, its confident claims about what the update “really targeted” deserve the same skepticism. The sites worth trusting through a core update are the ones that show their working, correct their misses in public, and tell you when they do not know something. Google has told us almost nothing about this update. Anyone who says otherwise is selling you certainty we do not have.
For the next two weeks, the job is patience, a baseline export, and a calendar reminder for December 1. That is not a very exciting plan. It is the plan that works.
Frequently Asked Questions
When did the Google November 2026 core update start?
November 10, 2026, at 10:06 a.m. Pacific time (1:06 p.m. Eastern), according to Google’s Search Status Dashboard. It applies globally and to all languages, and Google says the rollout may take up to two weeks to complete, which would put the finish around November 24.
How long will the November 2026 core update take?
Up to two weeks, per Google’s dashboard entry. A full-length rollout ends around November 24, 2026 — two days before Thanksgiving and three days before Black Friday. Google posts a completion notice on the Search Status Dashboard when the rollout ends, and that notice is the only reliable signal that it is over.
Is this the first core update of 2026?
No — it is the third. Google ran core updates from March 27 to April 8 and from May 21 to June 2, 2026. The November update is the eighth ranking update of any kind listed on the dashboard this year, and the first core update in roughly five months.
Should I change my content during a core update?
No — not until the rollout is confirmed complete, and then not until at least one more full week has passed. Google’s own guidance says to wait a week after completion, then compare that week’s Search Console data with a week from before the rollout began. Changes made mid-rollout cannot be attributed to anything, and rewrites based on a few days of noisy data often hurt pages that would have recovered on their own.
My traffic dropped the day after the update started. Am I penalized?
Almost certainly not. Core updates are not penalties — they are broad reassessments of how content is ranked, and they are not aimed at particular sites. A drop in the first days of a rollout is normal: rankings move while Google tests the new system. A drop only becomes meaningful if it holds for a full week after the rollout ends, at 20% or more, on a cluster of similar pages.
How do I check whether the update hurt my site?
Wait until at least a week after Google confirms the rollout is complete, then compare that week’s Search Console performance with the week before November 10. Compare by page type rather than by single pages, look at clicks and impressions together, and treat a sustained 20%+ drop on a group of similar pages as the signal worth acting on. Single-day moves and small percentage changes are noise.
What did Google say this update targets?
Nothing specific. The dashboard entry and Google’s LinkedIn post describe it as a regular update designed to better surface relevant, satisfying content, with no named system, industry, or signal. Any claim about what the update “really” targets before the rollout completes is speculation, not reporting.