Find published dossiers by topic, company, product or technology.

Showing 1–20 of 227 dossiers

A preregistered field experiment finds Google’s AI search reduces publisher clicks

The study moves the AI-search traffic debate beyond observational correlations: participants were randomly assigned to current Google Search, a version with AI features hidden, or AI Mode-only search during ordinary browsing. It is still a preprint and does not establish effects for every query or publisher.

ChatGPT Atlas can still surface blocked URLs unless publishers use noindex

Blocking OAI-SearchBot is not a complete removal signal for ChatGPT Atlas. OpenAI says a disallowed page can still appear as a link and title when the URL is learned elsewhere and judged relevant; publishers that want to suppress that result need a crawlable noindex directive, while GPTBot remains the separate training control.

Chrome Web Store now defaults publishers to two extension slots and is retiring Featured badges

Chrome extension publishers now face individualized publication caps, with two slots as the default for new or low-history accounts. Existing extensions remain published, increases can be requested, and Google is also retiring the Featured badge while making recent reviews more important to ratings.

beehiiv has turned newsletter recommendations into a unified paid-and-organic growth marketplace

beehiiv has documented the economics and guardrails behind its rebuilt Recommendation Network, including the 20% fee on paid recommendations, verified-subscriber charging, quality-based auto-pause rules and more granular control over recommendation slots and partner selection.

Meta’s approved U.S. teen settlement makes daily limits and nighttime blocks default on Instagram and Facebook

The settlement has crossed from proposed agreement to approved operating constraint. Meta now says the two-hour limit counts activity across Facebook, Instagram and detected multiple accounts, while teens also gain controls for non-algorithmic feeds and autoplay; most terms are required to remain in place for ten years.

Google Cloud is making every Application Integration run execute under an explicit identity

The migration turns integration identity from an implicit platform detail into an operational dependency. Teams may need new run-as accounts and `Service Account User` grants not only for runtimes but also for editors, publishers, approvers and deployment automation.