Google's November 2026 core update: what to check before you change anything

Google released its November 2026 core update on 10 November 2026. Its own Search Status Dashboard says the rollout "may take up to 2 weeks to complete" (the incident page). As of 13 November that page shows no closing notice, so treat the update as still rolling out.

If your clicks or impressions moved this week, you will want to know whether the update did it. Most of the answers you will read online are guesses. This post is a checklist for finding out what your own data supports, and for knowing when the honest answer is "not yet".

Lining up in time is a candidate, not a cause

A drop that starts inside the rollout window fits the update. It also fits a template change you shipped, a sitemap that broke, a page that fell out of the index, a seasonal dip, or a competitor publishing something better. Almost every week contains some announced change somewhere, so overlap in time is the weakest kind of evidence. Use it to decide what to look at first, not to decide what happened.

Step 1: wait for final data before you judge

Search Console reports the newest days as provisional. They can look low and then fill in. Compare final days only, against a baseline of the same length from before the change, and keep weekday and season in mind. The data-through date on any report tells you where "final" ends. If you read a drop off a chart that includes today and yesterday, you may be reading a delay.

Step 2: find out what fell

Split the change before you theorise about it.

• Impressions fell, click-through held: you are being shown less. That is a visibility change: ranking, indexing, or what the results page shows.
• Impressions held, clicks fell: you are still shown but chosen less. Look at titles, snippets and the layout of the results page for those queries.
• Everything fell on one day versus a few pages over weeks: a step with a date usually has an event behind it. A slow slide points to ageing content, competition or seasonality.

Step 3: find where it landed

Split by page and by query, then by country and device. A fall concentrated in one folder or template points to something near that folder. A fall spread across many unrelated pages starting within a day or two of each other is closer to what a ranking update looks like, but still not proof.

Step 4: check your own side first

These checks are cheap and they are decisive when they hit:

1. Manual actions and security issues in Search Console. These have no data feed, so no tool can check them for you; open the report yourself.
2. Whether the pages that lost impressions are still indexed.
3. Whether robots, noindex, canonical tags, redirects or a deploy changed around the first day of the drop.
4. Whether you recorded those changes anywhere. A change nobody wrote down cannot be tested later.

If one of these explains the drop, you do not need an update to explain it, and the fix is yours to make.

Step 5: hold your hands still

Resist the large rewrite. If you rewrite titles on two hundred pages in the middle of a rollout, you will never know which change did what, and Google itself says rankings keep moving while a rollout runs. Write down what you know, annotate each change you do ship with its date, and wait until the rollout has finished before judging its effect. Then measure against the baseline you chose in advance.

Where SerpUp fits, and where it does not

An investigation in SerpUp works through these same questions. It dates the change, splits it into impressions, position, click-through and query mix, lists the checks it could run, and says which ones it could not. A check that could not run is never counted as a pass. It lists possible explanations as "possible", "likely" or "strong" contributors with the evidence behind each, and reserves "confirmed" for conclusive evidence. It keeps a list of announced Google updates and shows one when its dates overlap the start of a change. It shows that as context, not as proof.

What it cannot do: read Google's reasons, tell you whether an update affected your site, see manual actions, or know about changes to your site that nobody recorded. When the decisive checks cannot run, it says the cause is unknown and lists what would make it testable.

If you want to see how a case is laid out, the first investigation guide walks through one, and the investigations methodology explains the confidence wording. The Investigations feature page lists what the product reads and what it does not claim.

The short version

Release date: 10 November 2026, rollout up to two weeks, per Google. Wait for final data. Work out what fell and where. Check indexing, manual actions and your own deploys first. Keep a record, change nothing large mid-rollout, and measure the result against a baseline you chose before you looked.

Google's own guidance is worth reading alongside this: core updates and debugging drops in search traffic. This post makes no claim about how the update affects any particular site or kind of site.