On this page · 10 sections
- What Google announced on 12 November 2026
- The November 2026 timeline: four overlapping events
- What Google has not said
- How to separate Hydrogen from the core update
- Five SEO changes for US and UK sites
- Worked example: reading a US and UK retailer's November data
- What not to do, according to Google
- US and UK notes, and dates to watch
- How eCorpIT can help
- References
Summary. On 12 November 2026 Google made Gemini 4 Hydrogen available in Google Search for all users worldwide and called it the biggest model upgrade Search has had. Robby Stein, Google's VP of Product for Search, listed four changes: better handling of multi-part, misspelt and very specific questions; a wider query fan-out that links to a broader range of sites; more images, comparison tables and custom tools in answers; and more nuanced answers in every AI Mode language. On X, as reported by Search Engine Roundtable, he added that Hydrogen is now the default model in AI Mode and handles the hardest questions in AI Overviews. The launch landed two days into the November 2026 core update, which still had no completion entry on 15 November, and in the same week as a logging error that cut generative AI impressions in Search Console for 9 to 11 November. Google has published no new guidance for site owners, and its documentation still says AI Overviews and AI Mode need nothing beyond normal SEO. Our five changes, which are our analysis rather than Google advice: cover sub-questions inside strong pages, state specifics in plain text, make images and tables usable, confirm eligibility and controls, and rebuild measurement before Black Friday on 27 November.
About this article. For SEO leads, content teams and analytics owners with US or UK search traffic. On 15 November 2026 we checked every Google statement against the Google Keyword blog, Google Search Central documentation and blog, Search Console Help and the Google Search Status Dashboard, the API price against Google's Gemini API pricing page, and UK dates against the Competition and Markets Authority's notices and summaries. Posts on X are attributed to Search Engine Roundtable, which reported them. This is general information, not legal advice, and no vendor paid for inclusion. Researched with AI assistance and reviewed by our editorial team.
What Google announced on 12 November 2026
Google published two posts that day. Stein's Search post covers what changes for searchers, and it is short. Koray Kavukcuoglu's post introduces the model itself. The table lists every Search change Google named and where it said so; the X posts come from Search Engine Roundtable's report.
| Change | What Google says | Where and status |
|---|---|---|
| Intent | Search handles multi-part questions, hard-to-read typos and highly specific requests, follows instructions and calls tools more precisely, and answers each part | Search post; live for all users |
| Query fan-out and links | Hydrogen runs simultaneous queries across the relevant subtopics and links to a broader range of sites than before | Search post; live |
| Visual answers | More images, structured responses, comparison tables and custom tools | Search post; live |
| Language | More nuanced answers in all supported AI Mode languages | Search post; live |
| Default model | The new default in AI Mode, and used for the hardest questions in AI Overviews | Robby Stein on X, via Search Engine Roundtable |
| Reach | Available to all users, globally | Nick Fox on X, via Search Engine Roundtable |
The model post adds context. Google describes Gemini 4 Carbon and Gemini 4 Argon as its frontier models for deep, long reasoning, and Hydrogen as the fast model for everyday and agentic work. It prices Hydrogen in the Gemini API at $1.50 per million input tokens and $7.50 per million output tokens, flat across a 1 million-token context window, which the pricing page confirms for the standard paid tier under the model ID gemini-4-hydrogen. Google also says Hydrogen finishes tasks 2.5 times faster than Gemini 3.8 Flash and cuts fabricated claims by more than five times. Those are Google's own figures, not independent tests. The post describes its before-and-after images as comparisons between Gemini 3.5 Flash and Hydrogen in Search, which suggests Search previously ran on an older Flash-class model; Google has not said so directly. Our Gemini 4 Hydrogen pricing and API migration guide covers the developer side.
Subscribers see one more layer. On 10 November Google began rolling Gemini 4 Carbon out to all Google AI Ultra subscribers in AI Mode, as well as in the Gemini app and Google Antigravity. Everyone else gets Hydrogen by default.
The November 2026 timeline: four overlapping events
Search data from mid-November will mix several changes. Put them on one timeline before you read any chart. The core update entries come from the Search Status Dashboard, the logging error from Google's data anomalies page, and the launches from Google's own posts.
| Date | Event | Source | What it can move |
|---|---|---|---|
| 9 to 11 November | Logging error lowered impressions in the Search Console generative AI report | Search Console data anomalies page | Reported AI impressions only, not real visibility |
| 10 November, 10:07 PST | November 2026 core update released, global and all languages, up to two weeks | Search Status Dashboard | Classic rankings, and AI answers that draw on them |
| 10 November | Gemini 4 Carbon in AI Mode for Google AI Ultra subscribers | Google Keyword blog | A small paid audience's AI Mode answers |
| 12 November | Gemini 4 Hydrogen in Search for all users | Google Keyword blog | AI Mode answers and links; the hardest AI Overviews |
| 15 November | Core update still has no completion entry | Search Status Dashboard | Rollout continues |
| 24 November | End of Google's two-week estimate | Our arithmetic | An estimate, not a deadline |
| 26, 27 and 30 November | Thanksgiving, Black Friday, Cyber Monday | Calendar | US demand spikes that distort week-on-week comparisons |
Two weeks is an estimate. Seven of the 13 core updates since March 2023 on the dashboard ran longer than 14 days, the longest 45 days in March 2024, while the March and May 2026 updates each took about 12 days. Our November 2026 core update tracker records the timings.
Search Engine Roundtable's Barry Schwartz noted that Hydrogen arrived mid core update and suggested it affects AI Overviews and AI Mode rather than core rankings. That is his reading, not Google's. It is the likeliest split, but Google's guide says its generative AI features rest on its core ranking and quality systems, so a core update can move AI citations too.
What Google has not said
Read the announcement for its gaps as much as its claims. As of 15 November 2026:
- No traffic or citation figures. Google gave no number for how many more links Hydrogen shows, how often it appears in AI Overviews or how clicks behave.
- No new Search Central guidance. The Search Central blog's two November posts cover moving to a CDN without blocking Googlebot and Search Central Live in Zurich. The documentation log's 12 November entry adds a page on identifying Search traffic, nothing on Hydrogen.
- No change to eligibility rules. The AI features page, last updated 10 December 2025, still says AI Overviews and AI Mode have no extra requirements and need no special optimisation.
- No full split between surfaces. The same page says AI Mode and AI Overviews may use different models and techniques, so their answers and links differ. Stein's post makes that concrete for AI Mode. In AI Overviews, Hydrogen handles only the hardest questions, so other AI Overviews may still run on another model, and Google has not said which queries count as hardest.
- No market exceptions. Global and all supported AI Mode languages are the only scope words. Nothing is specific to the US or the UK.
That last point matters for UK readers. The Competition and Markets Authority (CMA) fair ranking conduct requirement gives Google until 17 December 2026 to comply, after which it must give publishers 30 or 15 business days' notice of material ranking changes, depending on the type. Whether a model swap inside AI Mode counts as a material change is an open question, covered in our CMA fair ranking analysis. Hydrogen arrived before that date, so it was not tested.
How to separate Hydrogen from the core update
This section is our analysis; Google has published no diagnostic method for model changes. The logic is simple: core updates move classic positions, while a new AI Mode model mostly changes which pages appear inside AI answers and how those answers look.
| What you see in Search Console | More likely cause | Why |
|---|---|---|
| Average position falls across a page group, all query lengths | Core update | Classic ranking moved |
| Position steady, generative AI impressions sharply up or down | Hydrogen or other AI feature changes | AI answers changed while rankings held |
| Gains concentrated on queries of eight or more words, position steady | Hydrogen fan-out and intent handling | Google says it handles multi-part, specific questions better |
| Multimodal AI impressions shift on product or how-to pages | Visual answers, or the core update | Check whether classic positions also moved |
| Generative AI impressions dip only on 9 to 11 November | Reporting error | Google logged it as a data issue |
| Drop in one country only | Neither by default; check holiday demand, hreflang and local competitors | Both changes are global |
Two filters help. In the Performance report, choose + Add filter, then Queries, then Custom (regex).
Enter ^(\S+\s){7,}\S+$ to keep queries of eight words or more, then compare their clicks and position with shorter queries. Search Console uses RE2 syntax and matches anywhere in the query unless the pattern is anchored, as this one is.
In the generative AI performance report, use the Countries tab to split the United States from the United Kingdom, because Thanksgiving shifts US demand and has no UK equivalent.
Five SEO changes for US and UK sites
Google's position is that work aimed at AI features is still SEO: its guide to optimising for generative AI, last updated 10 July 2026, says AEO and GEO are, from Google Search's point of view, simply SEO. Each change below starts from something Google has said, then adds our recommendation. Where we speculate about Hydrogen, we say so.
1. Cover sub-questions inside your strongest pages, not in new thin pages
Google's basis. Google defines query fan-out as concurrent, related queries the model generates to fetch more results, and its example turns a question about a weedy lawn into searches about herbicides, chemical-free removal and prevention. Hydrogen widens that fan-out across all relevant subtopics. The same guide warns that building separate pages for fan-out queries mainly to manipulate rankings or AI answers breaches the scaled content abuse spam policy.
What to do. Take your 20 most valuable pages. For each, list the sub-questions a buyer asks before acting, from Search Console queries, sales call notes and support tickets, and check that each has a clearly headed section with a direct answer. A US heat pump installer's cost page should cover sizing for a 2,000 sq ft home, state and utility rebates, and installation time; a UK equivalent should cover a three-bedroom semi, grant eligibility and installer certification. One strong page with ten answered sub-questions beats ten thin pages.
Speculation, labelled. A wider fan-out probably lets more distinct pages earn a supporting link in one answer, so a page that answers one sub-question precisely may be cited without ranking for the head query. Google has published no citation counts, so treat this as a hypothesis to test in your own data.
2. State the specifics that multi-part questions ask for, in plain text
Google's basis. Hydrogen targets highly specific requests and aims to answer each part of a question. Google's AI features page lists keeping important content available as text among its best practices, and its guide says its systems understand synonyms, so long-tail variants need no stuffing.
What to do. Put decision facts in text near the top of commercial pages: price, size, compatibility, eligibility, delivery cut-off, returns window and warranty. UK pages should show sterling prices including VAT; US pages should show dollars and say whether sales tax is added at checkout. If you run separate US and UK pages, keep hreflang annotations correct so the right version is retrieved. Write last order dates for Christmas delivery as text, not only in a banner image.
Speculation, labelled. A model that follows instructions more closely may be less forgiving of pages that hide key facts behind tabs, PDFs or images. Google has not said this.
3. Make images and comparison tables usable as sources
Google's basis. Google says Hydrogen shows more images, structured responses, comparison tables and custom tools. Its guide recommends high-quality images and video, says sites already following its image and video SEO guidance are optimising for generative AI search, and points retailers and local businesses to Merchant Center feeds and Business Profiles. The AI features page asks that structured data match the visible text.
What to do. Use original product and process images with descriptive file names, alt text and captions. Publish specification comparisons as HTML tables, not screenshots. Keep Product structured data, Merchant Center prices and on-page prices identical, which matters most during Black Friday price changes. Local businesses should set Business Profile hours for Thanksgiving and the UK Christmas bank holidays.
Speculation, labelled. Google has not said whether AI Mode's comparison tables draw on tables from source pages or are built from text. Clean tables cost little and help readers either way.
4. Confirm eligibility and decide on controls before peak season
Google's basis. To appear as a supporting link, a page must be indexed and eligible to show in Search with a snippet. The site must also be included in Search generative AI features in Search Console, which is the default. Snippet controls (nosnippet, data-nosnippet, max-snippet) and noindex limit what appears, and robots.txt rules for Googlebot govern crawling. Google-Extended is the control for AI training and grounding in some of Google's other systems, not for Search.
What to do. Check that robots.txt and your CDN or bot-management rules do not block Googlebot; Google's 11 November blog post covers how a CDN move can go wrong. In Search Console, open Settings > Search generative AI and confirm each property you want included is set to include, directly or by inheriting from its parent property.
Search templates for leftover nosnippet or tight max-snippet values from past experiments. UK publishers that want finer control should note the CMA timetable: directory-level controls are due by 3 December 2026 and a page-level control by 3 March 2027, as explained in our page-level opt-out guide.
5. Rebuild measurement around four overlapping events
Google's basis. The generative AI performance report, open to all websites since 31 August 2026, shows impressions in AI Overviews and AI Mode by page, country, device and date, with dates in Pacific Time, and can be filtered to text-based or multimodal searches. It shows impressions only, and the newest data can be preliminary. Google's new page on identifying Search traffic, added on 12 November 2026, says Search uses the origin referrer policy, so analytics sees only https://www.google.com/ or a local domain such as https://www.google.co.uk/, never the query.
What to do. Add custom annotations to your Search Console performance charts for 9 to 11 November (logging error), 10 November (core update) and 12 November (Hydrogen); each note takes up to 120 characters. Export the generative AI report weekly. Use 2 to 8 November, a full Monday to Sunday week before the logging error, as your baseline for AI impressions. In GA4, check that custom channel rules, referral exclusions or filters do not push Google traffic from local domains into Referral or Direct. Expect analytics and Search Console totals to differ; Google names privacy settings, redirects and different measurement methods as normal causes.
Worked example: reading a US and UK retailer's November data
The figures below are illustrative, not client data. Suppose a home and garden retailer sells in both countries and compares the baseline week of 2 to 8 November with 16 to 22 November for three page groups.
| Page group | Classic clicks | Average position | Generative AI impressions | Our reading |
|---|---|---|---|---|
| US buying guides | 12,000 to 9,840 (down 18%) | 4.1 to 6.3 | 30,000 to 31,500 (up 5%) | Core update; wait for it to finish |
| UK category pages | 8,000 to 7,760 (down 3%) | 3.2 to 3.3 | 20,000 to 28,000 (up 40%) | Hydrogen fan-out or visual answers; check landing-page sessions in analytics |
| How-to guides, both markets | 5,000 to 5,600 (up 12%) | Steady | 15,000 to 18,750 (up 25%) | Long-query gains; reinforce sub-question coverage |
For the US buying guides, 12,000 clicks less 18% is 9,840, and position slipped by 2.2 places. AI impressions rose by only 1,500, so the loss sits in classic rankings. Google's core update guidance is to confirm the rollout has finished, wait at least a full week, then compare with a week before the update began. If the rollout ends on 24 November, the earliest clean comparison week starts on 1 December, after Thanksgiving week. Hold content changes on that group until then.
For the UK category pages, AI impressions rose by 8,000 while clicks fell by only 240. That looks like a change in presentation, not in ranking. Because the report shows impressions only, check AI-driven visits through landing-page sessions in analytics. The response is changes 2 and 3: make prices including VAT, stock and delivery dates explicit, so a page shown inside an answer gives a reason to click.
What not to do, according to Google
Google's guide lists tactics that do not help in Google Search, and Hydrogen changes none of them: llms.txt and similar files (Google Search ignores them), chunking content into tiny pieces, rewriting pages just for AI, chasing inauthentic mentions and overfocusing on structured data. Building a page for every fan-out query risks the scaled content abuse policy. Google also says no third-party tool has access to its internal ranking or AI systems, so be wary of any vendor claiming to measure Hydrogen's citation logic directly.
US and UK notes, and dates to watch
United States. We know of no US rule that requires Google to report AI Mode metrics or give notice of model changes. Google's two-week estimate for the core update ends on 24 November, two days before Thanksgiving, so compare against the same holiday week in 2025 rather than the week before.
United Kingdom. From 3 December 2026 the CMA's publisher conduct requirement obliges Google to give publishers engagement metrics for its search AI features, including impressions, clicks and click-through rate across AI Overviews and AI Mode. Our CMA metrics baseline guide explains what to export now so you have a before-and-after.
Both. If you sell in both markets from one domain, check hreflang and currency switching. A model that handles specific requests better may still surface the wrong regional page if signals conflict.
Dates to watch. The core update's completion entry, estimated by 24 November. The CMA deadlines of 3 December (publisher requirement, including directory-level controls and metrics) and 17 December 2026 (fair ranking). Google's first compliance reports to the CMA, due on 3 January 2027 for the publisher requirement and 17 January 2027 for fair ranking. The page-level control by 3 March 2027. Search Engine Roundtable also reported on 13 November that some users saw Search without the AI Mode tab and AI Overviews without the follow-up box; the report carried no Google comment, and such tests may never launch.
How eCorpIT can help
eCorpIT is a Gurugram-based technology organisation, founded in 2021, assessed at CMMI Level 5 and MSME certified, with senior-led engineering teams working across AWS, Microsoft and Google platforms. Our SEO, AEO and GEO audit service checks AI feature eligibility, snippet controls, crawl access through CDNs, sub-question coverage and US and UK currency and hreflang signals, and sets up measurement windows that separate model, core update and seasonal effects. Talk to us at /contact-us/.
Last updated: 15 November 2026.