# Pulse ยท September 17, 2026 > Google cuts Search Profile eligibility to 10,000 followers and adds a UCP cart-transfer path, dbt Summit ships an MCP server and AI agent, and Claude Cowork merges into chat. Canonical: https://brandonlazovic.dev/pulse/2026-09-17/ Author: Brandon Lazovic Published: 2026-09-17 ## Google's UCP update adds a cart-transfer option and expanded checkout-flow testing Status: Confirmed | Topics: agentic-commerce, product-feeds-shopping Google said on September 16, 2026 that its Universal Commerce Protocol (UCP) integration now includes cart transfer, letting a shopper move from Google to the merchant's own site to finish checkout, plus enhanced checkout-flow testing tools for merchants. The update is part of a broader holiday-shopping package covering AI-visibility reporting, product feeds, and loyalty data. It is rolling out gradually in the U.S., with Australia and Canada following in early 2027. In plain terms: UCP is the shared technical rulebook that lets shopping agents from Google, Shopify, Stripe and others talk to a merchant's checkout the same way; this update adds a cart-transfer option that sends the shopper back to the merchant's own site to finish buying instead of completing the purchase entirely inside Google. Why it matters: A merchant already on UCP gets a way to hand a shopper back to its own site mid-checkout instead of completing the entire transaction inside Google, which changes how much of the buying experience the merchant controls. Our take: I wrote about UCP's fourth spec release breaking fulfillment and consent schemas that merchants had already integrated against, four releases in. This cart-transfer feature is additive rather than breaking, but it lands on the same spec whose track record so far is shipping changes faster than most merchants can absorb them. - [Google: Boost your holiday sales with these agentic commerce updates](https://blog.google/products-and-platforms/products/shopping/google-shopping-updates-holiday-shopping/) ## dbt Summit 2026 ships an MCP server, an AI agent for analytics engineering, and a Fivetran context layer Status: Confirmed | Topics: ai-data-stack, llm-models-agents dbt Labs and Fivetran announced AI-agent capabilities at dbt Summit 2026 on September 16, 2026: dbt Wizard, a project-grounded AI agent for analytics engineering, reached public preview, with its CLI in public beta and desktop app in private beta; a dbt MCP Server plus Anthropic and ChatGPT integrations reached general availability; and Fivetran's Context Layer, built on an open Agents Schema, entered private beta to centralize warehouse metadata for LLMs. dbt v2 and dbt State also reached general availability. In plain terms: MCP is a plug that lets an AI assistant connect to a tool and use its data; dbt just shipped its own official plug, plus an AI helper built into dbt itself that already understands a team's specific data models. Why it matters: A data team using dbt now has a first-party MCP server and an in-project AI agent to point at, instead of building custom tooling to expose warehouse context to an LLM. Our take: I wrote a 10-minute audit for treating any MCP server as a supply-chain dependency with reach into your data, since it runs with your credentials and reads tool text a model can act on. dbt's own MCP server is first-party rather than a third-party plugin, which changes the trust calculus, but a data team should still run that same audit before pointing an agent at it in production. - [dbt Blog: Fivetran + dbt Labs Announces New Capabilities to Make Enterprise Data Agent-Ready at dbt Summit 2026](https://www.getdbt.com/blog/fivetran-dbt-labs-announces-new-capabilities-to-make-enterprise-data-agent-ready-at-dbt-summit) - [dbt Blog: Everything we announced at dbt Summit and why it matters](https://www.getdbt.com/blog/dbt-summit-2026-product-announcements) ## Google cuts Search Profile eligibility to 10,000 followers and adds single-login multi-brand management Status: Confirmed | Topics: organic-search-core Google announced on September 16, 2026 three changes to Search profiles, the publisher pages Google surfaces in Search: eligibility for U.S. creators and publishers drops to 10,000 followers across YouTube, Instagram, X, or TikTok; a single login now manages Search profiles for multiple sub-brands at once; and article display gets longer headlines and optimized image thumbnails. No international rollout date was given. In plain terms: A Search profile is a page Google can show next to your name in search results, pulling in your posts from YouTube, Instagram, X, and TikTok; publishers used to need at least 35,000 followers on most of those platforms to qualify, and now the bar is 10,000 on any of them. Why it matters: Dropping the bar to 10,000 followers opens Search profiles, and the discovery real estate they carry in Search, to a much wider tier of publishers and creators than the 35,000-to-100,000 range Google set in August. Our take: Google has now cut this eligibility bar twice in five weeks, which points at Search profiles becoming a mass-market identity layer rather than a top-creator perk. The question worth watching is whether Google backfills the profile with enough content to be worth a publisher's time at 10,000 followers, or whether the lowered bar mostly just expands who is eligible to apply. - [Google: 3 new ways we're improving Search profiles for publishers](https://blog.google/products-and-platforms/products/search/3-new-ways-were-improving-search-profiles-for-publishers/) ## Google publishes a guide for adding a Search Profile badge to a publisher's own site Status: Confirmed | Topics: organic-search-core, structured-data-schema Google published developer documentation on adding a Search profile badge, a clickable widget that links a publisher's own site to their Google Search profile, the hub Google builds from a creator's YouTube, Instagram, X, and TikTok content. The guide covers markup, brand guidelines, and placement, including touch-target size and logo integrity when combined with other badges. Google gave no launch date for the badge itself. In plain terms: The badge is a small button or logo a publisher can add to their own website, like a social-media follow icon, that links visitors straight to that publisher's Google Search profile page. Why it matters: A badge is a low-effort way for a publisher to send its own site traffic toward the Search profile Google already built for it, ahead of the wider push Google would need to make the profile worth that traffic. Our take: Publishing an embeddable badge is Google asking publishers to do the discovery work Search itself is not yet doing for these profiles, which is a smaller ask than driving profile traffic through search results directly. Worth watching is uptake: a badge only helps if a publisher's own site still gets enough direct traffic to make the click worth sending elsewhere. - [Google Search Central: Add a Search profile badge to your website](https://developers.google.com/search/docs/appearance/search-profiles) ## Anthropic merges Claude Cowork and Claude chat into a single interface Status: Confirmed | Topics: llm-models-agents Anthropic announced on September 16, 2026 that Claude Cowork, its longer-running task mode, is merging into the main Claude chat interface across web, desktop, and mobile. The unified interface lets a user bring a quick question or hand off a longer task to the same Claude, with work continuing after the user closes the app. The rollout starts on Pro and Max subscription plans over the coming weeks. In plain terms: Claude Cowork was a separate mode built for tasks that keep running after you leave, like a report due later; now that mode lives inside the same window as everyday Claude chat instead of being a separate destination. Why it matters: Collapsing the quick-question and long-running-task modes into one Claude interface removes a decision point a user previously had to make about which mode to open before starting work. Our take: Folding a background-task mode into the default chat surface follows the same direction OpenAI took folding its Codex desktop app into a unified ChatGPT desktop app: both point toward one general-purpose agent interface rather than separate tools for separate durations of work. What is worth watching is whether the merged interface makes it obvious to a user when a request has silently become a long-running background task instead of an immediate answer. - [Anthropic: Claude Cowork and chat are now one Claude](https://claude.com/blog/cowork-is-now-claude)