Google has been quietly scaling a program that pays publishers when their content feeds AI-generated search answers. Digiday, which surfaced the story, describes it as a "pay-per-value AI licensing scheme" — and the early read from critics is brutal: "the program looks less like a meaningful payout and more like a legal fig leaf."

For comms and digital PR teams, the stakes are straightforward. If your clients' coverage gets absorbed into an AI answer instead of driving a click, the value of a placement collapses unless someone pays for the underlying content. A licensing scheme that actually compensates publishers — at real rates, at scale — would go some way to fixing that. Google testing one is, on paper, the most significant development on this front to date.

Hold the champagne. This is a test, and tests at Google have a habit of quietly dying. Even if it survives, the framing matters. A "pay-per-value" model leaves Google deciding what the value is, which is not a negotiation most publishers will win. Critics quoted by Digiday already see the structure less as compensation and more as legal cover — a way for Google to point at checks written when antitrust and copyright scrutiny of AI training and AI answers keeps intensifying.

Still, the direction of travel matters. Publishers of all sizes have spent two years asking one question about AI search: will we ever get paid for content that appears in AI-generated answers? For the first time, the answer from Google is a qualified, cautious, small-scale maybe.

Whether users even want AI answers is a separate, uncomfortable question — one the industry is asking with increasing urgency as AI summaries spread across search products. A licensing scheme solves nothing if the format itself degrades the product or the traffic economics that fund the content being licensed.

For now: watch the rollout, discount the hype, and assume the payout numbers, if they ever become public, will disappoint. That is the pattern with platform compensation programs, and there is little here yet to suggest Google is breaking it.