Google's November 2026 core update: did your traffic move?

On the tenth of November, Google released its November twenty twenty-six core update. Google says the rollout may take up to two weeks. So, did your traffic move?

And if it did, was it the update, or something else that happened the same week? Guessing is expensive. Here is how to check what actually changed, step by step.

We will follow one case on a demo site, Lumen Garden Company. The data is fictional, and this drop happened in October, not this week. Think of it as a

detective story with one rule: no guessing. Every case starts with a signal. On the dashboard, one line says impressions are down six point three percent against the previous twenty-eight days,

with a button: Investigate this drop. Check the date at the top: data through the sixth of November. Search Console runs a few days behind, so that is the last day you can trust.

In the sidebar, Investigate and act shows a red six: six cases waiting. Open the list. Each card says what moved, and the first suspect SerpUp found.

We open the one from early October: impressions, from the first to the ninth. This is the case file, and the Answer tab comes first. Status:

needs attention. Confidence: medium, with a dashed label, not yet calibrated. That label is a warning.

Treat the confidence as a lead, not a measurement. Under it, what to do next. No action is recommended from the checks that ran. SerpUp does not invent a

fix just to look useful. Now the evidence. What we checked: seven checks. Two found evidence, and five could not be checked.

Suspect one: a change in search result features. Click-through fell on appearances whose position did not move. Medium confidence, still not calibrated. Suspect two is the one from the headlines:

a Google update. Read the wording. Possible contributor. Overlap in time is the only signal, and Google does not say which sites an update affected.

And five checks could not run. That matters. A check that could not run is not a clean bill of health. It means the question is still open. The timeline puts events on

a calendar around the drop day, the first of October. On the twenty-fourth of September, the September spam update was rolling out. That is before the drop. It lines up in time.

That makes it a candidate, not a cause. The page says so in plain words: an event near the drop is a likely contributor at most, never a proven cause.

On the fifth of October, a trust audit finished, after the drop. Only events before the change day can be suspects. So, the verdict.

Back on the Answer tab: no page lost clicks to a change in search result features, so there is nothing to fix here. Use Watch for two weeks. That is the honest ending of many cases.

The update lines up in time, but the evidence cannot tie it to a loss on any page. So you do not rewrite your site in a panic. You watch.

If you want the full reasoning, Details lists the alternatives considered, the affected pages, and what SerpUp has recorded, and from when. When the evidence does support a fix,

it lands in the Action Center. The work is ranked. Each item shows a gain range and a job size, and Make task freezes the evidence, so you can compare later.

Notice the label on every estimate: not validated against past outcomes. These are candidates you choose, not promises. Open a task. This one adds Organization schema to the home page.

The status line shows where it is: deployed, and waiting for its check. The fix pack is the change, written out. Which file,

what to add, how risky it is, about how long it takes, and what to do if it goes wrong. Copy for your agent puts the whole pack on your clipboard as a prompt for a coding agent.

Or hand it to a developer. SerpUp does not edit your site. You apply the change, and you deploy it. After the deploy, Did the fix work runs the same check again.

Before the fix: the check needs action. Now: the check passes. But look at the next line. Seven days after deploy:

inconclusive, because no traffic measurement exists for this task. A passed check and a traffic gain are two different claims. Here is a task that is further along. It is verified,

and now monitored. The acceptance criterion was simple: the live title is new. Impact reviews come at seven, fourteen and twenty-eight days. Day seven is an early signal,

with a lift from minus two to plus nine percent. A range that crosses zero is not a win yet. Wait for day twenty-eight. You should not have to open the app to

find the next case. Alerting setup shows your rules and, more important, whether anything can reach you. Seventeen rules and zero destinations means no alert arrives. Add a destination,

then send a test. Autopilot lists what runs by itself, and what it never touches. It never edits a page, and it never approves or closes a fix. And if you work with an AI assistant,

connect it with a key. A read-only key is the default. It reads your data and changes nothing. So, when an update lands: check what moved,

test the explanations, fix what the evidence supports, and verify. SerpUp's White Friday offer is forty percent off Starter, Pro and Agency. It ends on Friday,

the twenty-seventh of November. serpup.app/white-friday.