Google's November 2026 core update: the SEO checklist to run before you change anything

Google started rolling out the November 2026 core update on Tuesday, 10 November 2026, at 10:06 Pacific time. Its Search Status Dashboard (opens in a new tab) says the update applies globally, in all languages, and that "the rollout may take up to 2 weeks to complete."

If your traffic moved this week, the most useful thing you can do is record what happened and rule out other causes. Rewriting pages or deleting content in the middle of a rollout is how site owners turn a temporary dip into a lasting one. This checklist is split into what to do now, while the update is rolling out, and what to do after Google marks it complete.

What do we know about the November 2026 core update?

Very little beyond the basics, and that is normal for a core update.

In its announcement, quoted by Search Engine Roundtable (opens in a new tab), Google called this "a regular update" meant to surface relevant, satisfying content from all types of sites. It named no sector, content type or system.

For timing, the dashboard's history is a better guide than guesses. The last three core updates took between 11 and 18 days:

If this one follows the same pattern, it finishes between about 21 and 28 November. That puts the week after it, the week Google says to wait before analysing, on top of Thanksgiving, Black Friday and Cyber Monday. Online stores should keep that in mind before reading anything into November numbers.

What should you do while the update is rolling out?

Record, rule out, and wait. Google's core updates page (opens in a new tab) says core updates are broad and do not target specific sites or pages, and that a small drop needs no drastic action.

1. Mark the date

Add an annotation for 10 November in Search Console's Performance report (right-click the chart and choose "Add annotation"), and the same note in Google Analytics. Anyone who looks at the chart in March will then know why the line moved.

2. Save a baseline

Export the Performance report for 3 to 9 November, the full week before the rollout: top pages, top queries, clicks, impressions and average position. Search Console keeps 16 months of data, but your own export is easier to compare later and records what you saw at the time.

3. Rule out the causes that are not the update

A drop that starts the same week as a core update is not always caused by it. Google's guide to debugging traffic drops (opens in a new tab) lists the usual suspects. Check these before you blame the algorithm:

• Search Console itself: look for a data anomaly notice. Search Engine Roundtable reported on 9 November that the Performance report looked wrong for many sites, before the update began.
• Manual actions and security issues: both have their own report in Search Console. A hacked WordPress site that serves spam pages to Google can lose rankings in the same week by coincidence. If you see unfamiliar pages indexed, follow the hacked WordPress site recovery guide first.
• Indexing and crawling: open Page indexing and Crawl stats. Look for a spike in "Excluded by noindex", server errors or redirect errors.
• Your own changes: list every plugin update, theme change, migration, redirect rule and robots.txt edit from the last two weeks. A caching or SEO plugin update that adds noindex to a template does more damage than any core update.
• Tracking: if Analytics dropped but Search Console clicks did not, the problem is the tag or the consent banner, not Google.
• Seasonality: compare with the same weeks last year, and check your main queries in Google Trends. Many searches fall in late November whatever Google does.

4. Leave working pages alone

Google advises against "quick fix" changes, such as removing page elements because of a supposed ranking rule, and calls deleting content a last resort. During a rollout, rankings move several times. A page you rewrite on day three can be judged on the rewrite, not on the version that ranked.

What should you check after the update finishes?

Wait until the dashboard marks the update complete. Google's page then says: "We recommend waiting at least a full week after a core update completes before analyzing your site in Search Console." Its debugging guide adds that, once you make changes, it can take a few weeks to see whether they helped.

Then compare a full week after the rollout with the week before it began:

1. Separate the search types. Use the Search type filter to view Web, Image, Video and News on their own. A drop in Image search is a different problem from a drop in Web search.
2. Find the pages that moved. In the Pages tab, compare the two periods and sort by the difference in clicks. Look for a pattern: one section of the site, one template, one kind of article.
3. Judge the size of the move. Google's debugging guide calls a move from position 2 to 4 a small drop. A fall from the top 10 to around position 29 across a wide range of queries is a large drop, and that is when a site-wide review makes sense.
4. Check queries as well as pages. A page can keep its clicks on its main query and lose the long tail around it, or the reverse.
5. Use weekly or monthly views. Search Console added weekly and monthly granularity in December 2025, which smooths out weekend dips that make daily charts hard to read.

If the drop is small, do nothing for now. If it is large and lasts, read on.

How do you review content after a core update drop?

Start with the pages that lost the most, and judge them as a reader would. Google's guide to helpful, reliable, people-first content (opens in a new tab) is the yardstick, and it changed in October 2026.

The October additions describe the "main content" of a page and four things Google's quality raters look at: effort, originality, talent or skill, and accuracy. The guide states that crediting other sources "doesn't replace the need for original effort." It also tells site owners to avoid deceptive authorship, such as invented authors or credentials.

Questions to ask of each page that dropped:

• Does it add something that is not already on the pages above it: your own data, a tested fix, an example from your own work?
• Would a reader know who wrote it and why that person can be trusted on the topic?
• If AI helped write it, did a person check every fact, and does the page say how it was made where a reader would expect that?
• Is the title accurate, or does it promise more than the page delivers?
• Was the publish date changed without a substantive update?

Improve pages that fail these questions in ways that help readers. Google is clear that there is no guaranteed fix: some changes take effect in days, others take months, and some sites only recover at the next core update.

Does the core update affect AI Overviews and AI Mode?

Google has said nothing specific about AI features in this update. What its AI features page (opens in a new tab) does say still applies: a page must be indexed and eligible for a snippet to appear, there is no special schema or AI text file to add, and normal SEO practice is what matters.

Two practical points for measurement:

• Traffic from AI Overviews and AI Mode is included in the Performance report, within the "Web" search type. There is no separate AI line in that report.
• Search Console's Generative AI performance report shows impressions for pages that appeared in AI features. Use it to see whether a drop in clicks came with a drop in AI visibility.

Copy this core update checklist

NOVEMBER 2026 CORE UPDATE CHECKLIST

NOW (while the update rolls out)
[ ] Annotation added for 10 Nov in Search Console and Analytics
[ ] Baseline exported: 3-9 Nov, pages and queries
[ ] Search Console: data anomaly notice checked
[ ] Manual actions: none
[ ] Security issues: none / site scanned
[ ] Page indexing: no new noindex or server errors
[ ] Own changes in the last 2 weeks listed:
[ ] Analytics tag and consent banner working
[ ] Same weeks last year compared (seasonality)
[ ] No rewrites or deletions of pages that still rank

AFTER (completion date + 7 days at least)
Update completed on:
Comparison: week after vs 3-9 Nov
[ ] Web / Image / Video / News checked separately
[ ] Pages with the biggest click loss:
[ ] Pattern (section, template, content type):
[ ] Size of move: normal / site-wide review needed
[ ] Pages reviewed against Google's helpful content questions
[ ] Holiday weeks accounted for (Black Friday, Cyber Monday)

When to ask for help

Most sites need nothing after a core update except patience and a clean comparison. Ask for help when the drop is large and lasting, when you find indexing errors or unfamiliar spam pages, or when a store's sales fall in the same weeks as its search traffic.

If the cause turns out to be technical rather than the update, the steps in PageSpeed good, Core Web Vitals failed cover the speed side. For a WordPress or WooCommerce site that needs someone watching updates, indexing and security every week, that is what WordPress maintenance covers.