Google is reportedly paying some publishers when their content feeds an AI answer, and the ai contribution pilot is administered through Search Console rather than through a contract.
Update (2026-10-01): Two corrections since this post went out. First, Google has described the pilot itself. A June 18, 2026 post on Google’s public policy blog, by Markham Erickson, vice president of government affairs and public policy, says Google is "piloting a new way to partner with websites whose content meaningfully contributes to the freshness and factuality of generative AI responses through the process of grounding." It says "partner," not "pay," and gives no amounts. Our earlier line that Google had published nothing was wrong. Second, this is no longer a one-source story. The Information reported on September 29 that Google is paying about 100 publishers, with reported amounts from under $1,000 over several months to more than $1 million a year. We cover those numbers in a separate post.
That second half is the story. Every AI content deal before this one required a negotiation, which means a lawyer, and an audience large enough that Google or OpenAI thought you were worth approaching. A widget in a tool you already have open requires neither.
Two weeks ago we published the AI citation premium, which found that licensed publishers get substantially better treatment in AI answers and that five groups take 69 percent of the benefit. The conclusion there was blunt: the premium is real and it is not available to most publishers, because most publishers will never be offered a deal. This pilot is the first mechanism that points the other way.
When we first published, it was a story with one source. See the update above.
What the ai contribution pilot reportedly does
Digiday reported it on 14 September under the headline "Google rolls out pay-per-value AI licensing program to publishers," by Jessica Davies and Sara Guaglione.
The mechanics, as reported: enrolled publishers see an earnings widget inside Google Search Console showing a monthly figure with some history. Payment covers content that contributes to AI-generated responses in AI Overviews, AI Mode and Gemini. Publishers can opt out at any time. Payments go to a bank account, and the amount received may differ from the displayed estimate because of tax deductions and payment thresholds.
The sign-up surface, from a screenshot published by Search Engine Land, reads: "Start earning with AI contribution pilot. Accumulate earnings when your content contributes significantly to AI-generated responses in participating products."
Google’s confirmation, as rendered by Digiday, describes it as an early-stage learning pilot to test how best to reward high-quality content, on top of the traffic and tools it already provides. Payment is reported to be based more on value than on raw usage, meaning Google pays when it judges content to have contributed meaningfully rather than counting appearances.
How the figure is calculated is not disclosed anywhere. Digiday says so directly.
Digiday reports Google approached at least dozens of publishers, while noting it could not get final confirmation of the number, and that the program has widened well beyond news publishers toward smaller and mid-sized outlets. Two publisher executives, both anonymous, described early payments as "peanuts" against advertising revenue and as "lowball numbers" that do not clear a threshold worth opting in for.
Why the delivery mechanism matters more than the money
Take the "peanuts" quote seriously and the program still matters, because the interesting variable is not the amount. It is who can reach it.
An AI licensing deal is a negotiated instrument. Someone has to want your content enough to open a conversation, and you need counsel to read what you are signing. That structure selects for scale by design, which is exactly what our citation-premium piece measured: a concentrated benefit flowing to a small number of large groups.
A Search Console widget selects for nothing. Every site owner already has the account. There is no minimum traffic threshold reported, no contract to review, no counterparty to find. If the pilot ever opens past its invited set, an association publishing forty articles a year would be enrolled the same way the Guardian would be.
That is a genuinely different distribution model, and it is worth separating from the question of whether the current payouts are meaningful. Small amounts flowing automatically to many publishers and large amounts flowing by contract to a few are different systems, and only one of them ever reaches the readers of this site.
Worth noting the counterweight, though. Payment "when your content contributes significantly" is a judgment Google makes, by a method it does not publish, reported in a figure you cannot audit. Publishers have spent two decades with exactly that arrangement on the advertising side. The mechanism is familiar, and so is the asymmetry.
Three headlines, one source
This is the part to hold onto, because the story is being read as better established than it is.
Search Engine Land and Search Engine Roundtable both covered it on 14 September. Both are by Barry Schwartz, and both attribute the Google statement to Digiday. That is one reporter relaying one source, not two outlets confirming a third. Neither obtained independent Google comment.
Google has published little. Its public policy blog described the pilot on June 18 (see the update above), but there is nothing on Search Central and no help-center article. We checked the Search Console help documentation for the generative AI performance report, which is the closest existing surface, and it covers impressions only. It does not mention contribution, earnings or payment.
No Google spokesperson is named or titled anywhere. The confirmation is Digiday’s rendering of a statement from an unnamed source, which is normal practice and still worth knowing before you quote it as "Google said."
The June 2026 Google post that gets cited alongside this, "New opportunities, control and insights for website owners" by Mrinalini Loew, is about opt-out controls and whether a site helps ground generative responses. It contains no payment or revenue-share element at all. It should not be read as Google having announced compensation in June.
What does exist as near-primary evidence: Barry Schwartz’s screenshots of the Search Console interface, plus Google’s June 18 policy post.
And the precursor is a good reminder of how long this was visible. Schwartz spotted a reference to an "AI contribution report" in Search Console on 13 April 2026 and wrote that he had no idea what it looked like, guessing it resembled Bing Webmaster Tools’ AI performance reporting. He had no way to know money was involved. It sat in the open for five months.
What is not confirmed, and is being repeated anyway
Four claims are circulating that no source supports. Worth knowing which is which if you are briefing a client.
That the program is invite-only. Digiday describes Google approaching publishers. It never says enrollment is closed or gated, and no source uses the term.
That publishers must accept program terms to start earning. Not in Digiday. The Search Console screenshot shows a sign-up surface, which implies an affirmative action, but a terms-acceptance requirement is nobody’s reporting.
That Google pays only for content that contributed while the answer was being generated. This phrasing appears in none of Digiday, Search Engine Land or Search Engine Roundtable.
That links or fact-checks appended after the answer do not qualify. Same. It may come from help documentation that Schwartz screen-captured but did not transcribe, and he has said he cannot access the supporting docs because he is not in the pilot. Until someone reads them, it is not reportable.
One small correction while we are here, because it changes the meaning. Digiday’s headline says "pay-per-value," not "pay-per-use." The two URLs in circulation resolve to the same article, and the value-versus-usage distinction is the entire structure of the program.
This is not the same as paying per answer
A framing has emerged that Google and Cloudflare have independently converged on the AI answer as the billable event. It is tidy and it does not hold up.
Cloudflare does not bill per answer. Pay Per Crawl charges per request, returning HTTP 402 with a price header when a crawler does not present payment intent, and Cloudflare’s own documentation still describes it as being in closed beta. It is not generally available.
"Pay Per Use" is Cloudflare’s phrase for a direction, not a product. Its 1 July post says "we’re starting to shape Pay Per Crawl into Pay Per Use," and follows with "we want to be honest that this is an experiment." The concrete per-answer example in that post is a partner arrangement where publishers can be paid when their content appears in Ceramic.ai’s results. That is Ceramic’s model, not Cloudflare’s product.
Cloudflare’s other July announcement is about blocking, not paying. The default flip that took effect on 15 September, which we covered in the Cloudflare AI crawler default, blocks Training and Agent crawlers on ad-bearing pages for newly onboarding domains. Different mechanism, different problem.
And attribution-weighted payment is not new. ProRata’s Gist has been splitting revenue with shares allocated by each source’s contribution to a response for a while now. Perplexity’s publisher program is an advertising revenue share. TollBit prices per crawl. The units in this market are per crawl, per query, revenue share and flat licensing, and no two of them agree.
Google’s own pilot is not strictly per-answer either. What is reported is a monthly aggregate figure derived from a judgment about value, by an undisclosed method. That is not a discrete billable event.
The accurate version is less satisfying and more useful: nobody has settled on what the billable unit is, several companies are running incompatible experiments, and the one that reaches a small publisher without a negotiation is the one to watch.
What to do about it this week
Open Search Console and look. If an AI contribution entry is there, you are in the pilot and you have information almost nobody has. If it is not, that is also worth knowing, because it tells you how narrow the invited set currently is. This takes two minutes and is the only first-hand data available to anyone right now.
Do not change anything else. There is no documented eligibility criterion to optimize for, no published calculation to target, and no threshold to clear. Anyone selling you AI contribution optimization this month is selling you a guess about an undisclosed formula.
Keep your crawler policy decision separate from this. Whether to allow Google-Extended and the various AI crawlers is a decision about your content and your traffic, and the possibility of a small monthly payment does not settle it. Our AI crawler access audit is the framework for that call and it has not changed.
If you are in it, record what you see. Screenshot the figure monthly. If the calculation is never published, a time series of what you were actually paid against what you actually published is the only evidence anyone will have about how this works.
The thing worth watching is not the payout. It is whether the pilot opens past its invited set, because a payment route with no negotiation in it is the first structural answer anyone has offered to the problem we described two weeks ago.
Frequently Asked Questions
What is Google’s AI contribution pilot?
A reported program that pays publishers when their content contributes to AI-generated responses in AI Overviews, AI Mode and Gemini. It is administered through Google Search Console, where enrolled publishers see an earnings widget with a monthly figure.
Has Google officially announced it?
No. As of 15 September 2026 there is no Google blog post, no Search Central announcement and no help-center documentation. The public record is one Digiday report from 14 September plus screenshots of the Search Console interface.
Is the reporting well sourced?
It is single-sourced. Search Engine Land and Search Engine Roundtable both covered it the same day, but both are by the same reporter and both attribute the Google statement to Digiday. No Google spokesperson is named anywhere.
How much does it pay?
Unknown, and the calculation is not disclosed. Two publisher executives quoted anonymously by Digiday described early payments as “peanuts” relative to ad revenue and as “lowball numbers.”
How do I know if I am in it?
Open Google Search Console and look for an AI contribution entry. There is no other way to check, and no published eligibility criteria.
Can I apply?
No application process has been reported. Digiday describes Google approaching publishers directly.
Is this the same as an AI licensing deal?
No, and the difference is the point. A licensing deal is negotiated, requires counsel, and in practice goes to large publishers. This runs through a tool every site owner already has, with no contract reported.
Does taking payment mean giving up my crawler settings?
Nothing in the reporting connects the two, and publishers can reportedly opt out at any time. Treat your crawler policy as a separate decision.
Does Cloudflare pay per answer too?
No. Pay Per Crawl bills per request and Cloudflare’s documentation still describes it as closed beta. Cloudflare has said it is “starting to shape Pay Per Crawl into Pay Per Use” and called that an experiment. The per-answer example in its own post is a partner’s model, not Cloudflare’s product.
Is anyone else paying per citation?
Not on those terms. ProRata’s Gist allocates revenue by each source’s contribution to a response, Perplexity runs an advertising revenue share, and TollBit prices per crawl. There is no industry standard billable unit.
Should I optimize for this?
No. There is no published formula to optimize against. Keep doing the things that get content cited, which we cover in [writing for AI citation](/search-engine-optimization-seo/writing-for-ai-citation/).
What would make this a bigger story?
Google publishing documentation, the pilot opening beyond an invited set, or a named publisher going on the record with figures. Any one of those would move this from a single report to a program.
