Google brings Gemini 4 Hydrogen to Search worldwide
Google says Hydrogen brings more visual AI answers and broader link discovery. Track exact URLs and where they appear in the answer.
On November 12, Google announced that Gemini 4 Hydrogen is available globally in Search. Google says it can handle more detailed requests, run related searches across subtopics, and present results with more images, comparison tables, and tools. The announcement describes changes across supported AI Mode languages. It does not publish a measured change in publisher referrals. Google’s Search announcement
Record the position of each link
Choose three questions that reflect tasks your site helps readers complete. Include one comparison, one question with two constraints, and one request for an explanation. Run the prompts on mobile and desktop in the same market and language. Keep the account and Search settings consistent. Record the selected model if the interface shows it.
For each answer, save the response format and the exact cited URLs. Note whether a link appears in the text, beside an image, in a table, or in a source tray. Check which claim the link supports and whether the destination gives a reader enough detail to verify it. A link that moves into a collapsed tray is still present, but it occupies a different place in the reading flow.
Keep a record for each model if you also test the Ultra option. Mixing Hydrogen and Carbon results would make it harder to tell whether a difference came from the model, the prompt, or the interface. Use the Carbon comparison guide for the paired test. Keep observed links and actual referral sessions in separate columns.
Use paired prompts to identify what the extra detail changes
Start with a short query such as “technical SEO crawler for a migration.” Add one constraint in the paired query, such as “I need to compare redirects across two exports.” Hold the market, language, device, and account settings fixed. The pair tests a specific change in the reader’s task and gives you a reason to inspect which source pages changed.
For each run, record whether the answer satisfies the added constraint and which linked page supports that part of the answer. Mark cases where a cited page discusses crawlers in general but offers no redirect comparison. Keep the quoted claim, destination URL, and source passage together so someone else can review the decision.
Report source placement and traffic on their own terms
A mobile answer may have fewer links visible before scrolling even when its source tray lists the same destinations as desktop. Record whether each link is visible immediately, appears after scrolling, or requires the reader to open a panel. Give the count as a fraction of tested runs and identify any runs where AI Mode gave a different layout.
Use Search Console’s Generative AI report to look for changes in impressions across the pages in your test. Its public documentation defines an impression metric for generative features in Search. Use the model labels you recorded in your test for the model comparison. Use your analytics data to check attributable visits. Google’s report documentation
Keep learning
Continue this topic
Next in this topic
ChatGPT Wallet starts rolling out in Dots
Earlier in this topic
OpenAI’s LVMH Media deal brings article links to ChatGPT
AEO & AI Search
Ask a question or join the discussion