Google starts a global core update
Google released its November 2026 core update on November 10, applying it globally and across all languages, with a rollout that may take up to two weeks.1 For search teams, the immediate task is to annotate the start of the rollout and watch for changes across their important pages and markets.
Avoid treating a movement during the rollout as a settled outcome. Compare traffic and visibility by page and query after the rollout, and separate any investigation from other changes made to the site during the same period. Use the Search Status Dashboard to check the update’s status before drawing conclusions.
Gemini 4 Hydrogen reaches Google Search
Google says Gemini 4 Hydrogen is now available globally in Search for all users.2 Google says its improved query fan-out conducts simultaneous queries across relevant subtopics and connects users to a broader range of helpful links.2 It also says responses will include more images, structured responses, comparison tables and custom tools.2
For content practitioners, the practical check is to test the complex questions your audience asks, including requests with several requirements. Look at which subtopics appear in the response, which pages are linked and whether the answer uses a table or another visual format. Record the full question and response so you can compare results without assuming that one test represents every search.
Review existing content against those questions. Where a page addresses only part of a question, consider whether a clearer explanation or comparison would help the reader. Do not treat a format change alone as evidence that a page will be selected.
Google explains crawl risks during CDN moves
Google says crawler traffic to an origin server can spike after a site moves behind a content delivery network, or CDN, before edge caches are populated.3 It says fast, stable responses can gradually increase Google’s crawl capacity limit when there is crawl demand.3 A new CDN starts with a cold cache, so an uncached request must be fetched from the origin server before a cacheable copy can be served from the edge.3
This matters to teams planning a migration: faster edge responses and an unprepared origin can create competing pressures. Before routing all traffic through the CDN, pre-warm important pages and frequently crawled URLs at a controlled pace. Coordinate that work with the people responsible for server capacity and security rules.
Google warns that blanket bot protection without verified-crawler exemptions can leave crawlers on challenge or error pages, and that pages and shopping listings can begin to drop out of Search if the block remains.3 Check CDN and firewall settings for verified-bot exemptions rather than applying a blanket challenge. If the origin needs temporary relief, Google recommends short-term 429 or 503 responses, for a few hours or at most one to two days.3
Adobe tools are coming to AI Mode
Google says Adobe will bring its creative tools to AI Mode in Google Search.4 Adobe is also expanding its connectors in Gemini and Gemini Enterprise with Acrobat and additional creative tools.4
For teams producing images and other creative assets, this is an integration to watch rather than a reason to change a publishing workflow today. Keep it separate from the Search model rollout: the announcement describes what is coming, not a completed AI Mode launch. When it becomes available, test the actual workflow before deciding where it fits in content production.
A new API can score content against defined questions
Google has introduced the Gemini Decisions API for closed-set decisions, powered by Gemini Decision 1.5 It accepts a shared multimodal input and up to 1,000 independent questions, returning probabilities and confidence scores for candidate options.5 Google says a single request can mix yes/no checks, multiple choice and rubric scores against a shared input.5
For teams building content-review or routing tools, this offers a way to test defined criteria against an input rather than ask for an open-ended written answer. Start with a narrow review task, write explicit criteria and compare the results with human judgments before using them in a workflow. Route uncertain cases to a reviewer instead of relying on a score alone.
Comments 0
No comments yet.
Sign in with GitHub or Google to comment. Reading needs no account.