November 2026 Core Update: Separate the Real Drop From the Search Console Bug

If you opened Search Console this week and your AI impressions fell off a cliff around November 10, wait before you rewrite anything. Three separate things hit Google Search in the same 72 hours, and only one of them is a ranking change.

Google started the November 2026 core update on November 10. A Search Console logging bug undercounted AI impressions for November 9 to 11. And on November 12, Google swapped the model behind AI Mode and AI Overviews. Each one moves a different number, and on a single chart they look like one big event.

This guide separates them, gives you a diagnosis table for the patterns you’re most likely to see, and walks through what to check once the rollout settles.

Key takeaways
  • The core update started November 10, 2026 and Google expects it to take up to about two weeks. It’s the third core update of 2026.
  • Google confirmed the Generative AI report undercounted impressions for November 9 to 11. That’s a logging problem, not a performance change.
  • Gemini 4 Hydrogen became the default model in AI Mode on November 12 and now handles the hardest AI Overviews questions. That can change your AI visibility independently of rankings.
  • The rollout will likely end just before Black Friday, so ecommerce sites should compare against last year, not last week.

The quick facts

November 2026 core update
StartedNovember 10, 2026, at 10:06 am Pacific (18:06 UTC), per Google’s Search Status Dashboard
Expected lengthUp to about two weeks
ScopeGlobal, all languages
What Google saidA regular update meant to better surface relevant, satisfying content from all types of sites
What it targetsGoogle didn’t name any site types, industries or ranking factors
Earlier movementRanking shifts before 18:06 UTC on November 10 weren’t this update

That last row matters. Plenty of people saw volatility on November 8 and 9 and assumed the update had started early. Google announces core updates as they begin, so anything before the announcement was something else.

Where it sits in 2026

Core updateRollout
March 2026March 27 to April 8
May 2026May 21 to June 2
November 2026Started November 10, still rolling out

Both earlier 2026 updates took about 12 days. If this one follows the same pattern, expect completion around November 22 to 24.

Three events, one chart: the week day by day

DateWhat happenedWhich number it moves
Nov 9Search Console logging bug begins in the Generative AI performance reportAI impressions in Search Console (reporting only)
Nov 10Core update starts. Gemini 4 Carbon rolls out in AI Mode for AI Ultra subscribersClassic rankings and clicks. AI Mode answers for a small paying group
Nov 11Logging bug endsAI impressions reporting returns to normal after this date
Nov 12Gemini 4 Hydrogen becomes the default AI Mode model for everyone and handles the hardest AI Overviews questionsWhich sources AI Mode and AI Overviews use and cite

So a dip in AI impressions on November 10 tells you nothing. The bug covers it. A change in AI impressions from November 12 onward could be the core update, the new model, or both. And a change in classic clicks is the one most likely tied to the core update itself.

Google called Hydrogen its biggest model upgrade to Search so far. A new model can read questions differently, pull from different pages and cite different sources, even if your rankings don’t move at all.

Step 1: Mark the bad days before you look at anything

Open Search Console and go to the Generative AI performance report. You should see Google’s own annotation on the affected dates. Google says the issue affects data logging only, so your real visibility on those days wasn’t hurt.

Then add your own notes everywhere the data travels:

  • Search Console: add custom annotations on November 10 (core update start) and November 12 (Hydrogen). The bug already has Google’s annotation.
  • GA4: add annotations on the same dates so anyone looking at traffic later sees them.
  • Exports and Looker Studio: exports don’t carry annotations, so add a note column or exclude November 9 to 11 from AI impression charts.

For any before/after comparison, skip those three days completely. “November 2 to 8 vs the week after rollout completes” is honest. “Last 7 days vs previous 7 days” this week is not.

Step 2: Wait, and pick the right comparison

During a rollout, rankings move back and forth. Third-party rank trackers often show swings that don’t hold. Watch the Search Status Dashboard for the completion note, then collect at least another week of settled data.

The Black Friday problem

Black Friday 2026 falls on November 27. If the rollout ends around the 22nd to 24th, your first clean post-update week is also the biggest shopping week of the year. A week-over-week comparison will show huge “gains” or “losses” that have nothing to do with the update.

For ecommerce and anything seasonal, compare against the same period last year instead. Look at the change in your share: did you grow less or more than you did between the same weeks of 2025? That’s much closer to the update’s real effect than raw week-over-week numbers.

Step 3: Segment before you conclude anything

A sitewide line hides almost everything useful. Core updates usually move some page types and queries and leave others alone. Here’s how to split it in Search Console’s Performance report:

By page type

Use Page filter, then “Custom (regex)”. For example /blog/ for articles, or /services/|/pricing/ for commercial pages. Compare each group separately.

Branded vs non-branded

Filter queries by regex with your brand name and common misspellings, for example axovox|axo vox|byaxovox, then flip to “Doesn’t match regex” for non-branded. Branded traffic follows demand and reputation, not rankings, so a drop there usually isn’t the update. Google also just added a branded-queries filter to the Search Analytics API, which makes this easier for anyone pulling data into a dashboard.

Device and country

Check mobile vs desktop and your top countries separately. A drop in one country only often points to local competition or local SERP features, not a sitewide quality reassessment.

Classic vs AI

Run the same comparison in the regular Performance report and the Generative AI report. The combination tells you a lot, as the table below shows.

What your pattern probably means

What you seeMost likely causeWhat to do
AI impressions dip on Nov 9 to 11 only, then recoverThe Search Console logging bugNothing. Annotate and exclude those days
Classic clicks steady, AI impressions changed from Nov 12Gemini 4 Hydrogen choosing different sourcesCheck which pages now get cited for your key queries and compare them with yours
Clicks down across almost every page typeA sitewide quality reassessment by the core updateWait for completion, then do the page review in Step 4 on your most important pages
One section down (for example the blog), the rest stableThe update treating that content type differentlyCompare that section’s top losers with what now ranks above them
Average position stable, clicks downMore AI answers or ads on your queries, not lower rankingsSearch your top queries and see what’s now above the first result
Only branded traffic downSeasonal demand or reputation, not the updateCheck Google Trends for your brand and any recent reviews or news

Step 4: Review your biggest losers like Google would

Once the rollout is done, sort pages by click change and open the ten biggest losers. For each, search the main query and look honestly at what now ranks above you. Google’s long-standing self-assessment questions for content are the best checklist here. In short:

  • Does the page offer original information, research or analysis, or does it mainly rephrase other sources?
  • Does it show first-hand experience, like real testing, real numbers or real examples?
  • Would you trust it enough to act on it, or send it to a friend?
  • Does it answer the question fully, or does a reader need to go elsewhere?
  • Is it clearly better than the pages ranking around it, or just similar?
  • Is it obviously written to rank, with padding, repeated keywords or vague headings?

Be strict. The usual finding isn’t that your page is bad. It’s that the pages that moved above you are more specific, more current or more clearly written from real experience.

Test it on one page: take your biggest loser and the page that now ranks first for its main query. List every concrete fact, number, example and screenshot on each. If theirs has more you can actually check, that’s your gap.

Step 5: Fix the right things, in the right order

Google’s guidance on core updates hasn’t changed: there’s no specific fix to apply, and recoveries tend to come from improving content overall. Those improvements are often only fully rewarded at a later core update.

Where we’d start:

  1. Pages that slipped a few positions on commercial queries. Going from 3 to 7 is a close fight. Falling off page two is a much longer one.
  2. Thin or outdated pages that compete with your stronger ones. Merge them into the better page with a 301 redirect, or improve them properly.
  3. Pages losing AI citations. Make answers clearer and easier to quote: a direct first sentence, real numbers, and visible FAQs. Our guide on writing FAQs AI engines cite covers the format.
What not to do mid-rollout
  • Mass-rewrite or delete batches of posts
  • Change URLs or site structure
  • Switch themes or migrate platforms
  • Bump dates on posts without real changes to look “fresh”
  • Buy links or launch a sudden content blitz to “recover”

Any of these makes it impossible to tell what helped or hurt, and some can make things worse.

How long until you know, and until you recover

You’ll know whether you were affected about a week after the rollout completes. That points to early December for most sites.

Recovery is slower. Google re-evaluates sites continuously, but big shifts usually show up at the next core update. In 2026 those came roughly every two to six months. So if you lost ground, plan improvements now and expect to see their full effect in 2027, not in December.

If you care more about AI visibility than rankings

This week is a good reminder that AI visibility and rankings are related but not the same. Hydrogen changed how AI Mode and AI Overviews pick sources without any ranking change at all. A site can hold its positions and still lose AI citations, or the reverse.

The levers for AI visibility are the ones we cover in how to get recommended by AI search: specific, verifiable content, consistent facts across the web, and pages that are easy to quote. Tracking it starts in the Generative AI report, which we walk through in our guide to seeing AI Mode traffic in Search Console.

What we’re doing on our own site

We’ve annotated November 9 to 12 in Search Console and GA4, and we’re not touching content until the rollout completes. Once it does, we’ll run the segmentation above on byaxovox.com and add what we found to this article, including what moved and what didn’t.

FAQ

When did the November 2026 core update start?

Google started rolling it out on November 10, 2026, at 10:06 am Pacific (18:06 UTC), according to its Search Status Dashboard. It applies globally and to all languages and is expected to take up to about two weeks.

Is this the third core update of 2026?

Yes. It follows the March 2026 core update (March 27 to April 8) and the May 2026 core update (May 21 to June 2).

Why did my AI impressions in Search Console drop on November 9 to 11?

Google confirmed a logging error that caused a decrease in impressions in the Generative AI performance report for November 9 to 11, 2026. It affects data logging only, not how your site actually performed.

Did Gemini 4 Hydrogen affect my AI Overviews visibility?

It might have. From November 12, Gemini 4 Hydrogen became the default model in AI Mode and handles the hardest AI Overviews questions. A new model can choose and cite different sources even when classic rankings don’t change.

Should I change my content during the core update rollout?

It’s better to wait until the rollout finishes and you have about a week of settled data. Changes made mid-rollout make it impossible to tell what helped or hurt.

How do I tell if the core update hurt my site?

Skip November 9 to 11, compare settled data after completion with a clean period before November 10, and segment by page type, branded vs non-branded queries, device and country. Then review your biggest losers against what now ranks above them.

How should ecommerce sites measure the update with Black Friday so close?

Compare against the same weeks of last year rather than week over week. Black Friday falls on November 27, 2026, right after the expected end of the rollout, so week-over-week numbers will be distorted by holiday demand.

Can I recover from a core update drop?

Google says there’s no specific fix. Recoveries usually come from improving content overall, and they’re often only fully visible at a later core update. Start with pages that slipped a few positions on commercially important queries.

Lost AI visibility, or just lost data?
The free checker tests whether AI search can read and verify your site, independent of rankings.
Run the AI visibility check →

Disclosure: information and opinion based on Google’s Search Status Dashboard, Google’s Search Console data-anomaly notice, Google’s Gemini 4 Hydrogen announcement and public reporting, checked November 18, 2026. The update is still rolling out, and we’ll update this page when it completes. See our full disclaimer.