# Pulse ยท September 10, 2026 > Google adds football and AI Mode fantasy features to Search, Snowflake gates AI-agent data changes behind approval, and ChatGPT Shopping leans harder on feeds. Canonical: https://brandonlazovic.dev/pulse/2026-09-10/ Author: Brandon Lazovic Published: 2026-09-10 ## Google adds a live game feed, deeper stats and AI Mode fantasy insights to Search for football season Status: Confirmed | Topics: ai-overviews-ai-mode, organic-search-core Google announced three football features for Search on September 9: a Live Game Feed with play-by-play updates, social commentary, highlights and AI-powered insights, live on mobile in the US in English with collegiate support and global expansion later in September; enhanced stats including league-leader numbers and a matchup carousel rolling out globally on mobile; and an AI Mode integration that links a user's Yahoo Fantasy or Sleeper account for start/sit recommendations and waiver-wire targets, live in the US in English. In plain terms: In practice: search for a game and Google can now show live stats, and if a searcher links their fantasy account, personalized lineup advice, without leaving the results page. Why it matters: Fantasy and stats queries now resolve inside AI Mode and built-in carousels instead of sending a click to a stats site or fantasy forum. Our take: This is the same pattern Google has already run on shopping, travel and local: pull the full task inside Search so the click never has to happen. Watch whether the fantasy-account linkup becomes a template for other personal-data integrations, from fitness trackers to loyalty programs, rather than staying a football-only feature. - [Google: Get ready for the game with new football features in Search](https://blog.google/products-and-platforms/products/search/football-features-google-search/) ## Snowflake gates AI-agent changes to sensitive data behind a five-stage human-approval workflow Status: Confirmed | Topics: ai-data-stack Snowflake announced Intent-Driven Governance in public preview on September 9, automating sensitive-column classification, masking-policy deployment and drift detection across roles and classifications. Any governance change proposed through Snowflake CoCo or CoWork routes through a five-stage workflow, Observe, Understand Intent, Build Spec, Generate SQL, Execute and Verify, that requires explicit human approval before execution, with version-controlled, rollback-capable artifacts and alerts on high-severity policy drift. In plain terms: Plain terms: before an AI agent can change who is allowed to see what data, a person has to click approve, and the whole exchange gets recorded so it can be checked later. Why it matters: As AI agents get write access to production data systems, a deterministic, auditable approval gate is the specific control practitioners will be asked to point to, not a general assurance that access is logged somewhere. Our take: I found when Snowflake launched its Cortex AI Gateway for MCP governance, in 'An MCP Server Is a Supply-Chain Dependency With Reach Into Your Data,' that 9 of the 12 capabilities it tagged carried a private-preview label and only 2 were GA, so the same recompute is worth running here. Intent-Driven Governance states public preview upfront, which is more direct than the Gateway's framing was, but a governance product still gated behind preview labels on its core stages is a checkbox, not yet the shipped, load-bearing control it will need to be. - [Snowflake Blog: Intent-Driven Governance: Protect Sensitive Data at Scale](https://www.snowflake.com/content/snowflake-site/global/en/blog/intent-driven-governance-sensitive-data-scale) ## GPT-6 Astra reaches Snowflake Cortex AI in private preview Status: Confirmed | Topics: ai-data-stack, llm-models-agents Snowflake announced on September 9 that GPT-6 Astra, OpenAI's newest model, is available in private preview on Snowflake Cortex AI, running inside Snowflake's security perimeter and plugging into Cortex Agents, Cortex AI Functions, Cortex Inference, the CoCo coding agent and the CoWork work agent. Snowflake credits Astra with improved reasoning, lower token usage and stronger alignment on long-running agentic workflows compared with prior models on the platform. In plain terms: In practice: Snowflake customers can now call OpenAI's newest model without their data leaving Snowflake's own servers, one of several models added this way in recent months. Why it matters: Cortex has now added a new frontier model roughly every month since June, so a model landing there is becoming routine platform maintenance rather than a standalone event. Our take: Private preview means access is still gated to select accounts, not open to every Cortex customer yet. Watch the gap between this announcement and general availability, since that gap is where the actual proof of Astra's computer-use claims inside a real enterprise data stack will show up, or won't. - [Snowflake Blog: OpenAI GPT-6 Astra Now on Snowflake Cortex AI](https://www.snowflake.com/content/snowflake-site/global/en/blog/openai-gpt-6-astra-snowflake-cortex-ai) ## Third-party tracking finds ChatGPT Shopping leaning harder on product feeds, a shift OpenAI has not confirmed Status: Observed | Topics: chatgpt-assistants, product-feeds-shopping Search Engine Journal reports that Profound, a third-party tool tracking ChatGPT prompts, measured feed-integrated product sources jumping from 8.26% to 61.54% of ChatGPT Shopping recommendations around July 10, coinciding with the GPT-5.6 release. No OpenAI release note, help-center page or blog post confirms the shift; OpenAI's own Shopping documentation states product results are selected independently by ChatGPT and are not influenced by partnerships, and OpenAI has not addressed the specific feed-reliance data. In plain terms: Plain terms: one outside tool that watches ChatGPT's shopping answers says feed-listed products are showing up far more than before, but OpenAI itself has not said its shopping results now favor feeds, so treat the number as an observation, not a confirmed rule. Why it matters: A merchant deciding whether to prioritize ChatGPT feed submission is currently working from one vendor's measurement, not an OpenAI-confirmed ranking factor, and the two calls for action are different. Our take: I wrote in 'OpenAI's feed pivot' that ChatGPT's organic product feed and its ads feed are architecturally separate pipelines with different eligibility rules, and that the feed is the entire product record with no crawl fallback. A measured jump in feed-sourced recommendations is consistent with that architecture doing what it was built to do, but a single third-party tracker's percentage is not the same claim as OpenAI stating feed data now outranks other sources, and merchants should hold that distinction before re-prioritizing spend. - [Search Engine Journal: ChatGPT Shopping Results Lean Hard On Product Feeds](https://www.searchenginejournal.com/chatgpt-shopping-results-lean-hard-on-product-feeds/589000/) - [OpenAI Help Center: Shopping with ChatGPT](https://help.openai.com/en/articles/11128490-shopping-with-chatgpt-search) ## Google consolidates its regional Search feature and eligibility documentation into one hub Status: Confirmed | Topics: organic-search-core Google Search Central published a hub page documenting Search features available only in specific regions: five EEA feature types, aggregator units, supplier units, an ecosystem carousel, job-sites features and structured-data carousels spanning hotels, flights and other verticals; a places carousel and refinement chip for Turkiye; and a South Africa badge plus refinement chip covering travel, products, car hire and food delivery. Each feature page states its own participation requirement. In plain terms: Plain terms: Search doesn't look the same everywhere, and Google just published one reference page listing which extra features show up in which countries and what a site has to do to qualify for each. Why it matters: A site expanding into any of these three regions can now check one page for which Search features apply and what each one requires, instead of reconstructing eligibility from scattered blog posts and changelog entries. Our take: A single consolidated hub is a maintenance signal as much as a documentation one, it means Google expects the regional-feature list to keep growing rather than staying a fixed EEA-only set. Sites operating in any of the three named regions should bookmark this page over the individual feature docs, since a hub is the more likely place to get updated first. - [Google Search Central: Search features by region](https://developers.google.com/search/docs/appearance/aggregator-features) - [Search Engine Journal: New Google Guide To Regional Search Features & Eligibility](https://www.searchenginejournal.com/google-regional-search-features-eligibility-guide/588975/) ## Google's John Mueller says the old position 1-10 metric no longer maps cleanly to today's results page Status: Observed | Topics: ai-overviews-ai-mode, measurement-analytics Responding to a question about how impressions are counted for generative AI in Google Search Console, Google's John Mueller said on Reddit that 'the old position 1-10 is hard to map, or to make useful for site owners,' citing how many ways a modern results page lets users interact, AI Overviews with citations, featured snippets, People Also Ask, beyond a simple ranked list. Search Engine Roundtable surfaced the reply; Google has no replacement metric documented. In plain terms: Plain terms: a search results page today has AI-written summaries, expandable question boxes and other blocks stacked in, not just ten blue links, so a single ranking number like 'position 4' can no longer describe where a page actually showed up or how it was seen. Why it matters: A Google engineer saying the industry's core ranking metric does not map to the current results page is a statement worth citing, even though it is not itself a documentation change or a new report. Our take: Google employees have said versions of this informally for a while, but a direct 'the old metric is hard to map' framing from Mueller is a stronger practitioner citation than the usual hedge. The open question this raises and doesn't answer is what replaces position as the metric a site reports up to a client or an executive, since 'it's complicated now' is not a number anyone can put in a dashboard. - [Search Engine Roundtable: Google Says The Old Position 1-10 Is Hard To Map For Site Owners](https://www.seroundtable.com/google-position-1-10-hard-map-42053.html) - [John Mueller reply on r/SEO](https://www.reddit.com/r/SEO/comments/1wamz5g/how_are_impressions_counted_for_generative_ai_in/)