Google Core Update November: How to Prepare Your Site

Here is the situation as of November 5, 2026: Google has not confirmed a core update for November. The last confirmed broad core update was in May 2026, and the last confirmed update of any kind was the September spam update, which finished rolling out on October 8. At the same time, forecasters are unusually specific about the window: in a Search Engine Journal column on October 15, analyst Dan Taylor put the chance of a Google update within 30 days at 96.8%, with late October to mid-November as the most likely window, and SEO tracking tools reported volatility through October that Google has not confirmed. So the honest position is neither "an update is coming, panic" nor "nothing is happening, relax." It is: an update is plausibly imminent, nothing is confirmed, and the useful work is the work you can only do before it lands — taking a baseline. Everything in this article is that work: what to measure this week, what to freeze, and what to check, so that if rankings move, you can tell what actually changed instead of guessing.

Confirmed versus forecast: keep the two apart

The single most common mistake during update season is treating a forecast as a fact and then "fixing" things that were never broken. A forecast is a prediction from volatility data and past timing; a confirmed update is an entry on Google's Search Status Dashboard with a start date and an end date. Until the dashboard says otherwise, there is no November core update to react to — only a window to prepare in. That distinction drives every recommendation below: nothing here asks you to change content to please an update that has not been announced, because Google's core updates documentation says core updates do not target specific sites or pages, and that most sites do not need to do anything at all.

Bookmark the dashboard and check it before you act on any update rumour. If a drop in your traffic lines up with a dashboard entry, you have a real incident to diagnose. If it does not, you have volatility, a seasonal shift, a technical fault, or a competitor's improvement — all of which have different fixes, and all of which get misdiagnosed as "the update" every single season.

Step 1: Take the baseline snapshot this week

A baseline is a dated record of how your site performs right now, taken before anything changes, so that later comparisons mean something. Without one, you cannot answer the only question that matters after an update: how much did we actually move, and where? Do this once, this week, and save the export somewhere you will find it in December.

1. Search Console, last 28 days versus the previous 28 days. Export the Performance report twice: once for queries, once for pages. Record total clicks, impressions, average CTR and average position, then write down your top 20 pages and top 20 queries with their clicks and positions. The page-level list is the important one — core updates move pages, not whole sites evenly, and a site-wide average hides a page that fell from position 4 to 29 behind ten pages that did not move at all.
2. Your top 10 pages, individually. For each of your ten most valuable pages, note its main query, its current position, and its click-through rate. A page at position 3 with a 2% CTR has a different problem from a page at position 29 with a 0% CTR, and you will not remember which was which in three weeks unless you write it down now.
3. Index coverage as it stands. Note how many pages are indexed, and list any pages that matter but are not indexed, plus any coverage warnings. If a page is not indexed before the update, you cannot blame the update for its absence afterwards.
4. Page experience snapshot. Record your Core Web Vitals status for your most important page templates — not every URL, just the templates that carry your traffic. A page-speed checklist tool pass over your homepage and your top two content templates takes minutes and gives you a dated "before" to compare against.
5. One line on seasonality. Write one sentence about whether your niche is seasonal right now — retail rising into the holidays, travel falling after summer, finance steady. Seasonal traffic changes look exactly like update damage if you forget to account for them, and a one-line note now prevents a wrong diagnosis later.

Worked example of what "good" looks like: a small content site's baseline might read "2,400 clicks, 61,000 impressions, 3.9% CTR, average position 24.1; top page /guides/example at position 6.2 with 310 clicks; 84 pages indexed, 3 excluded by noindex intentionally; homepage passes Core Web Vitals, article template fails on mobile LCP." That paragraph, dated November 5, is worth more than any tracker screenshot after the fact, because it separates what you knew before from what you discover after.

Step 2: Freeze the risky changes

The second preparation is a freeze, and it is counterintuitive: the best thing to do before a forecast update is to stop changing things. Google's own guidance for sites that drop after a core update is to avoid "quick fix" changes — removing a page element because someone heard it was bad, rewriting a performing page on a rumour, deleting content that is merely old. Those reactions are just as harmful before an update as after one, because they destroy your baseline: if you rewrite five pages this week and rankings move next week, you cannot tell whether the update moved them or you did.

So for the forecast window, freeze three categories. First, no redesigns, no template changes, and no site-wide title or meta rewrites on pages that already perform — those are high-blast-radius changes with no confirmed reason behind them. Second, no bulk content deletion; Google is explicit that deleting content is a last resort, only for sections that cannot be salvaged, and a deletion spree before an update is exactly the kind of change that looks like panic in hindsight. Third, no new aggressive monetisation on your best pages — heavy ad or affiliate changes alter page experience at the worst possible moment. Routine publishing can continue; a new article is not a risky change. But anything that touches your existing top pages should wait until the window passes or an update is confirmed and diagnosed.

Step 3: Run the technical checks that cost nothing

While content changes are frozen, technical checks are free: they fix things that are broken regardless of any update, and they remove the technical suspects from any later diagnosis. Run these four, in this order.

First, crawl control: confirm your robots.txt and sitemap are valid and consistent — a sitemap listing URLs that robots.txt blocks is a quiet, common failure, and a robots.txt and sitemap validator catches it in one pass. Second, redirect chains on your most linked pages: a chain of two or three hops bleeds crawl budget and ranking signals, and it is trivial to check before an update rather than during one. Third, your top pages' rendering: confirm the CSS and JavaScript Google needs are not blocked, since an unstyled render changes how Google judges the page. Fourth, your internal links to your top pages: a page that lost its internal links in a recent redesign is a page whose drop you will wrongly blame on the update. None of these checks require a hypothesis about the update. They are just hygiene, and hygiene done now is evidence later.

SEO audit tools to run before the update

The tools worth running now are the ones that produce a dated record you can compare against, not the ones that produce a score. A crawler or audit tool that exports your site's issues — broken links, missing titles, thin pages, redirect chains — gives you a "before" list; after the update, you re-run the same audit and diff the two. A single-number site score gives you nothing comparable, because you cannot tell which of its hundred inputs moved. The same logic applies to rank trackers, which deserve their own warning: during a rollout, trackers show violent day-to-day swings as Google's systems settle, and a one-day tracker spike is not a diagnosis. Check trackers weekly during a rollout, not hourly, and always confirm a tracker move against Search Console before acting on it — trackers estimate, Search Console measures.

Use the audit output for one specific job: a triage list, not a work list. Write down the pages that are thin, duplicated or outdated, and rank them by traffic. Do not fix them yet — remember the freeze. The list's purpose is speed after the fact: if a triaged page drops when the update lands, you already know its weakness and you already know it was weak before, which turns a week of investigation into an afternoon of targeted improvement.

If it hits: the first 48 hours, and the week after

If the dashboard confirms an update and your traffic moves, do not diagnose on day one. Google's guidance is specific: confirm the update has finished rolling out, then wait at least a full week before analysing in Search Console, comparing the week after against the week before the rollout started. Rollouts take up to two weeks, and rankings during a rollout are not final — reacting to mid-rollout positions is reacting to noise. In the first 48 hours, do exactly two things: confirm the update on the dashboard and re-export your baseline numbers so the comparison is ready. Everything else waits.

When the week has passed, the diagnosis itself follows a fixed order, and we have covered it in full in our companion piece on how to diagnose a traffic drop after an update — confirm the dates, separate search types, size the drop page by page, and only then assess content against Google's self-assessment questions for helpful, people-first content. The short version of its verdict, worth repeating here because it prevents the most common error: a small drop, like position 2 to 4, needs no drastic action at all, and a large drop, like position 4 to 29, needs a content assessment, not a technical scramble. Deliberate that now, before any drop exists, and you will not have to deliberate it under stress later.

Frequently asked questions

Has Google confirmed a November 2026 core update?

No. As of November 5, 2026, Google has not announced a core update since May 2026. The November window comes from analyst forecasts based on tracker volatility and past timing, not from Google. Check the Search Status Dashboard for confirmed updates rather than reacting to rumours.

What is the single most useful thing to do before an update?

Take a dated baseline snapshot: Search Console clicks, impressions, CTR and position for your top 20 pages and queries, index coverage, and Core Web Vitals for your main templates. Without a baseline, you cannot tell after an update whether a page actually moved or just looks like it did.

Should I stop publishing during the forecast window?

No. Routine publishing is not a risky change. Freeze only high-blast-radius changes to existing performing pages: redesigns, template changes, site-wide title rewrites, bulk deletions, and heavy monetisation changes. New articles do not disturb your baseline.

Which rank tracking tools are worth checking during a rollout?

Use them weekly, not hourly, and always confirm a tracker move against Search Console before acting. Trackers estimate positions from sampled searches and swing violently mid-rollout; Search Console is the measurement. A one-day tracker spike is noise, not a diagnosis.

How long should I wait after an update before judging the damage?

At least a full week after the rollout completes, comparing that week against the week before the rollout started. Rollouts take up to two weeks, and mid-rollout positions are not final. Google's own guidance says most sites do not need to do anything, and small drops need no drastic action.

Is deleting thin content a good pre-update move?

No. Google calls deletion a last resort, only for content that cannot be salvaged, and a pre-update deletion spree destroys your baseline — you will not know whether the update or your deletions moved rankings. Build the triage list now, and act on it only after a confirmed update and a proper diagnosis.

Preparation for a forecast update is unglamorous work: a snapshot, a freeze, four technical checks, and a triage list you hope you never need. It is also the only work that pays off in both outcomes. If the update arrives, you will diagnose it in days instead of weeks, because you will know what changed and what did not. If it does not arrive, you still have a clean baseline, a validated technical setup, and a prioritised content list — which is simply good site ownership, update or no update. Check the dashboard, take the snapshot, and then leave your performing pages alone.