Google is quietly paying publishers when their work feeds AI answers. Nobody has seen the formula.

What happened

Digiday reported on Sept. 14, 2026 that Google has been "quietly scaling" a pay-per-value licensing program for publishers. The mechanism runs through Search Console. The trigger, per the report, is when a publisher's content contributes significantly to an AI-generated answer — in Gemini, in AI Overviews, or in AI Mode.

That is the confirmed part. Here is what is not confirmed: the payout formula, the rate, the size of any check written so far, which publishers are in, and whether this is a test or a general rollout. None of that appears in the available reporting.

This is the first time Google has attached a payment to an AI citation rather than to a click — and that is the whole story, because everything publishers earn from Search today is priced per click.

Why the mechanism matters more than the money

For twenty years the deal was simple. Google took your content, showed a snippet, sent a visitor. You monetized the visitor. AI Overviews broke the second half of that sentence without touching the first.

A pay-per-value model changes the unit of account. You are no longer paid for traffic you receive. You are paid for contribution you make. If that sounds better, note what it also means: Google decides what "significant contribution" is, measures it in its own console, and reports the result to you. There is no third-party audit in anything that has been reported.

The context makes the timing legible. PPC Land reported that publishers spent $113 million in a single month buying back their own search traffic through paid ads. That is what the referral collapse looks like on a P&L. A licensing payment is Google answering a problem Google created.

What this is not

It is not a licensing deal in the sense of the OpenAI or Amazon agreements signed over the past two years. Those are negotiated contracts with terms, floors and durations. This is a program with a dashboard.

It is not a replacement for referral revenue. Nobody has published a number that would let you compare the two. Anyone telling you the rate this week is guessing.

It is not a settlement of the copyright question. The New York Times case against OpenAI and Microsoft is still at summary judgment. A voluntary Google payment does not concede that anything was owed.

And it is not the only lever moving. A Sept. 10 briefing from The Agent Watch says that starting Sept. 15, Cloudflare will let site owners set separate permissions for AI bots — crawl for training, answer queries, or act as agents — with ad-supported sites defaulting to open for search, closed for training and agents. If you sit behind Cloudflare, your default posture may change this week whether you touch anything or not.

The trap

A payment tied to citation frequency rewards content that AI systems find easy to summarize. Clean structure. Explicit facts. Extractable answers.

That is the opposite of what builds a durable audience. A newsletter people open because of the writer, a podcast people finish because of the host — those get cited less. If you optimize for the payout, you are optimizing to be a good input, and inputs get commoditized.

What to do about it

1. Open Search Console this week and look for any licensing or attribution surface. If it is there for you, screenshot it with the date.
2. Do not restructure anything yet. There is no confirmed rate. You cannot model revenue against an unknown number.
3. Check your Cloudflare bot settings before Sept. 15. Know your default before it is chosen for you.
4. If you have an existing AI license with any vendor, ask your lawyer whether accepting Google payments conflicts with an exclusivity clause.
5. Track AI Overview citations of your work manually for 30 days. When a rate appears, you will have a baseline to check it against.
6. Keep referral traffic and licensing revenue as separate lines. Blending them hides which one is dying.