Google’s November 2026 core update began rolling out on 10 November, and your traffic charts may already look a little odd. This guide is for small site owners and bloggers who want a calm, practical plan: what Google has actually said, what to do while the rollout is running, and how to judge the impact in Search Console once it is over.
What Google has officially said
The Google Search Status Dashboard lists a “November 2026 core update” in its Ranking section, with a start date of 10 November 2026. The incident page is headed “Incident affecting Ranking” and records that the incident began at 10:06 (US/Pacific) on that date. It says the update was released globally to all languages and that “the rollout may take up to 2 weeks to complete.”
As of 13 November 2026, the incident page showed no end time. That means the rollout should be treated as still in progress. Nothing here says it has finished, and you should not assume it has until the dashboard says so.
Google’s Search Central page, “Google Search’s core updates and your website,” adds the background. Core updates happen several times a year, are broad rather than aimed at particular sites, and are announced on the dashboard with start and end dates. The page says most sites do not need to take any action because of them.
What is confirmed and what is only reported
It helps to separate three kinds of information, because social feeds tend to blur them together.
| Kind of claim | Where it comes from | How to treat it |
|---|---|---|
| Start date, global scope, “up to 2 weeks” rollout | Google Search Status Dashboard incident page | Official |
| How to assess impact, what to avoid, how long recovery can take | Google Search Central documentation | Official guidance |
| Volatility levels, winners and losers, affected niches | Industry sites and tracking tools | Reported only; not confirmed by Google |
Search Engine Journal covered the launch on 10 November. Its article, which is secondary reporting based on Google’s dashboard, noted that no volatility data or named winners and losers were available yet, that Google had not confirmed an end date, and that Google’s Search Central blog had no post about the update at the time. If you read later claims about which kinds of sites gained or lost, remember that they come from third parties measuring samples of results. They are not statements from Google, and a sample is not your site.
What to do while the rollout is running
Google’s documentation says nothing specific is required of you during a core update, and it warns against quick fixes in favour of changes that serve users over the long term. In practice that gives you a short list.
- Write down the dates. Add an annotation in your own records (a spreadsheet or reporting dashboard works) for 10 November 2026 as the start. Add the end date when the dashboard lists one. You will need both later.
- Keep a baseline. Save or export your Search Console numbers for the week before 10 November, because that is the comparison period Google’s guidance points to.
- Do not rewrite pages in a panic. Rankings can move while an update is still rolling out. Editing the pages that are doing well adds noise and may remove what was working.
- Keep your normal publishing and maintenance going. Fixing a genuine bug, a broken page or a security problem is ordinary site care and is separate from reacting to the update.
- Rule out other causes. A tracking change, a site migration, a plugin update or a seasonal dip can all look like a ranking drop. Our guide to why Google rankings drop walks through those checks.
This update is also not the same thing as the spam update from earlier in the autumn. Spam updates deal with policy violations, while core updates adjust how Google assesses content overall. If you want the spam side, see Google’s September 2026 spam update: what to check and do.
How to assess impact in Search Console
Timing matters more than any tool setting. Google’s core updates page says to confirm on the Status Dashboard that the rollout has finished, and then to wait at least a full week before analysing your site. Compare the week after the update completes with the week before it began rolling out, which here means the week before 10 November.
One practical caution: Search Engine Journal pointed out that the post-update comparison window may overlap with Thanksgiving, Black Friday and Cyber Monday. That is that outlet’s observation, but the point applies to any site with seasonal traffic. If your audience shops or searches differently at this time of year, a plain before-and-after comparison can mislead, so also look at the same period last year if you have the data.
Step by step
- Wait until the dashboard shows the update as complete, then wait at least another week.
- Open the Performance report in Search Console and compare the post-update week with the week before 10 November.
- Look at your top pages and top queries, and judge whether each change is small or large.
- Check each search type separately, such as Web, Images, Video and News, so you can see where any change actually happened.
- Write down what you see in plain terms before deciding anything.
Small drop or large drop
Google’s page gives two examples. A move from position 2 to position 4 for a page is a small drop, and no drastic action is needed. Google suggests you avoid changing content that is performing well. A move from position 4 to position 29 is a large drop, and that calls for a deeper assessment. Positions fluctuate normally, so the point is to separate noise from a real, sustained shift.
If you are not sure where to begin looking inside the report, our post on quick SEO wins in the Search Console Performance report explains the filters and views in more detail.
If you did see a large, sustained drop
Google’s guidance for a large drop is to review the site honestly against its self-assessment questions in “Creating helpful, reliable, people-first content.” Some of the questions it asks are worth keeping beside you:
- Does the page add original information, research or analysis, or does it mostly rewrite other sources?
- Does it cover the topic thoroughly and offer more than other pages in the results?
- Does the heading describe the content accurately, without exaggeration?
- Is it clear who wrote it, and is it explained how the content was made?
The same page lists warning signs of content written for search engines first: publishing many topics in the hope some will rank, summarising other people’s work without adding anything, changing dates to look fresh without real updates, and writing to a target word count. Google also suggests asking people unconnected to your site for their view.
On fixes, Google recommends meaningful improvements, such as rewriting or restructuring content for readability and navigation, and treats deleting content as a last resort. It also sets expectations: some changes can take effect in a few days, but confirming a site-wide improvement can take several months, and results are not guaranteed. If a few months pass without a change, the documentation suggests waiting for a future core update. Our guide to recovering from a ranking drop covers the practical sequence in more depth.
Common mistakes to avoid
- Judging results on day three of a rollout that may last up to two weeks.
- Treating third-party winner and loser lists as facts about your own site.
- Mass-deleting or mass-rewriting posts before you have compared the right date ranges.
Key takeaways
- Google’s dashboard lists the November 2026 core update as starting on 10 November 2026, with a rollout of up to two weeks. No end time was listed as of 13 November.
- Most sites need to take no action, and Google says to avoid quick fixes.
- Annotate the start date, keep a pre-update baseline, and wait for the dashboard to show completion.
- Wait at least a week after completion, then compare against the week before 10 November.
- Claims about winners, losers and volatility are reported by industry sites, not confirmed by Google.
FAQ
Has the November 2026 core update finished?
Google says the rollout may take up to two weeks. As of 13 November, the incident page listed a start time and no end time. Check the Search Status Dashboard for the current status before you analyse anything.
Should I change my content right now?
Google’s guidance says nothing specific is required during a core update and warns against quick fixes. Wait for completion, assess properly, and then decide whether a real improvement is needed.
Which dates should I compare in Search Console?
Google’s page says to compare the week after the update completes, once you have waited at least a week, with the week before the update began. For this update that baseline is the week before 10 November 2026.
Is there a penalty or a fix for a core update drop?
Google’s core updates page describes a broad reassessment, not a single fix. For a large, sustained drop it points to overall content quality and says that confirming a site-wide improvement can take several months.