# Pulse ยท July 18, 2026 > Google's billions-of-clicks AI Search claim lands with no data behind it, a Top Stories carousel hits AI Overviews, Apple bans home-services Maps ads, and Shopify Collections gain multi-source targeting. Canonical: https://brandonlazovic.dev/pulse/2026-07-18/ Author: Brandon Lazovic Published: 2026-07-18 ## Google claims AI Search sends billions of clicks to sites weekly, without releasing the data behind it Status: Observed | Topics: measurement-analytics, ai-overviews-ai-mode Google SVP Nick Fox said AI features in Search now send billions of clicks to websites weekly, on top of the billions Search sends daily overall. Neither figure comes with a baseline, denominator, or published methodology, and no earlier version of the weekly AI-specific figure appears in Google's own posts before July 17, 2026. Individual sites see only impressions in Search Console, not the clicks Google cites, so the aggregate can't be checked against any site's own data. In plain terms: Google is stating a big company-wide total but not the underlying math, the same way a retailer might announce record sales without saying which products sold or to whom, so no individual site owner can check the number against their own traffic. Why it matters: A traffic claim practitioners can't reproduce from their own Search Console data isn't a metric they can act on, and the number that would actually change strategy, per-site AI referral clicks, still isn't published. Our take: I've made the case that AI usage numbers should be read as a demand signal, not a headline stat, but that reading only works when the methodology is visible, the way Anthropic published real methodology behind its Economic Index this summer. Google's number arrives with the methodology stripped out, which makes it closer to a marketing claim than a demand signal a practitioner can act on. - [Spotted by Search Engine Journal](https://www.searchenginejournal.com/google-puts-a-number-on-ai-search-clicks-without-the-data/582755/) - [Spotted by Search Engine Land](https://searchengineland.com/google-says-ai-search-features-sending-billions-of-clicks-to-websites-each-week-482599) ## A 'Top Stories' carousel rolls out inside Google AI Overviews for developing-news queries Status: Observed | Topics: ai-overviews-ai-mode, organic-search-core Search Engine Land reports a Top Stories carousel is now live inside AI Overviews for US mobile users on developing-news queries, surfacing timely articles and prioritizing a searcher's Preferred Sources when a trending story matches an outlet they've selected. The mechanism traces to a Google post from May 27, 2026 describing a 'prominent carousel' tied to Preferred Sources; that post uses 'Top Stories' only as an analogy, not this carousel's name, and doesn't confirm the scope Search Engine Land describes. In plain terms: This is a small news box that can appear alongside an AI-written summary when a story is still developing, showing a few real articles instead of just the AI's own paraphrase; if a reader has already flagged your site as a preferred source, this is one of the places that preference visibly pays off. Why it matters: A news carousel inside AI Overviews is a fresh visibility surface for timely content, and Preferred Sources status inside it rewards publishers a reader has already chosen over ones simply ranking well generically. Our take: Watch whether Google formalizes the 'Top Stories' name in its own documentation; until it does, treat scope claims like 'fully live' or 'US mobile only' as directional, and confirm inclusion by checking what Search Console's AI Overviews report shows rather than assuming visibility here. - [Spotted by Search Engine Land](https://searchengineland.com/top-stories-roll-out-in-google-ai-overviews-482615) - [Google (The Keyword): new ways to find your favorite sources](https://blog.google/products-and-platforms/products/search/original-high-quality-content-search/) ## Apple bans home-services, bail-bond, and crypto-ATM ads from its new Apple Maps ads product Status: Confirmed | Topics: platform-ecommerce, ads-paid Apple's advertising policy for its upcoming Apple Maps ads product, effective July 14, 2026, prohibits ad content promoting home services such as plumbing, electrical, locksmith, HVAC, pest control, roofing, or general contracting, along with bail bond services and cryptocurrency ATMs. Medical services ads get case-by-case review instead of an outright ban. Search Engine Journal reports a US and Canada launch this summer; Apple has not published a specific date. In plain terms: Apple Maps ads is a new paid placement inside Apple's map app that hasn't launched yet; this policy is the rulebook for what businesses can buy those ads before the product even goes live, and it rules entire categories out rather than just requiring extra verification the way Google does for similar businesses. Why it matters: Advertisers in home services, a vertical Google's Local Services Ads was built specifically to serve, need a different paid strategy on Apple Maps once it launches, since this policy closes the category off entirely rather than gating it behind verification the way Google does. Our take: The contrast with Google's Local Services Ads, which verifies and licenses home-services advertisers rather than banning the category outright, is the detail worth watching: if Apple holds this line at launch, it signals a narrower, higher-trust ad product rather than a Local Services Ads competitor, at least in this vertical. - [Apple Ads: Maps and sports programming policies](https://ads.apple.com/news-and-stocks-maps-and-sports-programming-policies) - [Spotted by Search Engine Journal](https://www.searchenginejournal.com/apple-maps-ads-ban-home-services/582542/) ## Shopify lets Collections combine multiple sources and target specific product variants Status: Confirmed | Topics: platform-ecommerce, product-feeds-shopping Shopify's Collections feature now supports combining automated rules, hand-picked products, exclusions, other collections, and app-sourced items within a single collection, replacing the prior either/or choice between automated and manual sourcing. Merchants can also build collections around specific variants, like a single size or color, that carry through to collection pages, storefront filters, and channels like Online Store and POS. Existing collections carry over automatically, though third-party or custom apps need API version 2026-07 to use the new capabilities. In plain terms: A 'collection' is Shopify's grouping of products for a category or sale page; until now merchants had to choose between rules-based (automated) or hand-picked (manual) collections, and this update lets a single collection mix both, plus target a specific variant, like just the medium size of a shirt, instead of the whole product. Why it matters: Variant-level and multi-source collections give merchants a native way to build precise merchandising segments, like in-stock items in one color, without the custom app logic that used to require. Our take: I've written about Shopify positioning Catalog as the substrate underneath agentic commerce, and this fits that pattern: every merchandising primitive that gets more flexible and rule-driven inside Shopify's data layer is one more reason build-versus-syndicate decisions tilt toward staying inside Shopify's infrastructure. - [Shopify Changelog](https://changelog.shopify.com/posts/collections-now-support-multi-source-and-variants) ## BigQuery adds IAM-based data governance tags for column-level security Status: Confirmed | Topics: ai-data-stack Google Cloud introduced IAM data governance tags in preview, a column-level security and classification system built on Identity and Access Management that replaces BigQuery's older, region-locked policy tags. Tags are defined once org-wide, in hierarchies up to five levels deep like PII, Financial, and CreditCardNumber, then attached to columns via schema JSON or SQL and enforced through masking or raw-access policies. Because the tags are global while enforcement stays regional, they also replicate automatically to secondary regions for disaster recovery. In plain terms: A 'policy tag' is a label BigQuery uses to say a column is sensitive and should be masked or restricted; the old version only worked within one geographic region, and the new version works company-wide while still enforcing rules locally in each region, closing a gap that made disaster-recovery setups awkward. Why it matters: Teams piping first-party or customer data into BigQuery for AI-visibility or personalization pipelines get a native way to classify and restrict sensitive columns without hand-rolled access scripts. Our take: This is the kind of unglamorous governance plumbing that decides whether a company can safely let an LLM agent query its warehouse directly; teams building retrieval or agent pipelines against BigQuery should treat this as the moment to classify PII columns properly rather than relying on dataset-level access alone. - [Google Cloud Blog: Data Analytics](https://cloud.google.com/blog/products/data-analytics/level-up-your-column-level-security-using-iam-data-governance-tags-in-bigquery/) ## Databricks adds Meta's Spark Muse 1.1 through Unity AI Gateway with centralized governance Status: Confirmed | Topics: ai-data-stack, llm-models-agents Databricks made Meta's Spark Muse 1.1 model available immediately through its new Model Provider Services, reachable via an OpenAI-compatible API and governed centrally through Unity AI Gateway. Unity Catalog permissions, rather than per-team API keys, now control access, while usage tracking captures token counts, latency, and cost attribution per team, and credentials for external providers stay inside Unity Catalog instead of scattered across systems. The capability is in preview across AWS, Azure, and GCP. In plain terms: Unity AI Gateway works like a single front desk that every team's AI requests pass through, so instead of each team holding its own API key for an outside model with nobody tracking total spend, one system logs who used what model, how much it cost, and enforces the same safety rules everywhere. Why it matters: Centralized model governance matters for any team running LLM-driven content, classification, or agent pipelines against Databricks-hosted data, since it replaces per-team key sprawl with one place to enforce guardrails and see real cost per workload. Our take: The direction worth tracking is model access becoming a data-platform permission rather than a developer credential; as more providers plug into gateways like this one, model choice for a given pipeline becomes a governance decision made by a platform team, not an individual engineer's API key. - [Databricks Blog](https://www.databricks.com/blog/metas-spark-muse-11-now-available-databricks-fully-governed-unity-ai-gateway) ## NVIDIA and Hugging Face let teams fine-tune diffusion models at scale directly from Diffusers Status: Confirmed | Topics: ai-data-stack, llm-models-agents NVIDIA integrated its NeMo Automodel training library with Hugging Face's Diffusers, letting teams run full fine-tuning or parameter-efficient LoRA training on Hub image and video models, including FLUX.1-dev, FLUX.2-dev, Qwen-Image, Wan 2.1, and HunyuanVideo, without converting checkpoints or writing custom training code. Training scales from a single GPU to multi-node clusters using sharding like FSDP2 and tensor parallelism. NVIDIA reports roughly 35.5 images per second fine-tuning FLUX.1-dev on eight H100 GPUs, rising to about 53.7 with LoRA. In plain terms: Fine-tuning means further training an existing image or video generator on your own examples so it reliably reproduces a specific look, like a house style or a signature product shot, instead of a generic result; this update removes the manual conversion work that used to sit between a Hugging Face model and NVIDIA's training software. Why it matters: Teams generating on-brand product imagery or video at scale now have a production path to fine-tune open diffusion models on their own catalog, instead of prompting a general-purpose model and hoping the brand look holds. Our take: Watch this less as a research story and more as a cost-curve story: as fine-tuning throughput on commodity GPU clusters improves, the case for training a narrow, on-brand image or video model in-house instead of licensing a closed one gets easier to make. - [Hugging Face Blog](https://huggingface.co/blog/nvidia/scale-diffusers-finetuning-nemo-automodel)