Is Google paying publishers for AI Overviews? For a small group of sites, yes: Google is running something called the AI contribution pilot, a program that pays publishers when their content contributes to answers in AI Overviews, AI Mode, Gemini and other AI features, and the whole thing lives inside Search Console. The sign-up screens became public on 14 September 2026. I have spent the morning separating what Google has actually said from what is being repeated, because most of the coverage blurs the two.
What is Google’s AI contribution pilot?
The confirmed core is thin but real. In a public policy post from 18 June 2026, Google said it 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”. That post never uses the name “AI contribution”, never mentions payment amounts, and never mentions Search Console. It sits alongside Google’s other paid content programs: a News AI pilot with over 200 publications, press-content payments to more than 5,500 European publications, and News Showcase with around 2,800 partners.
The name and the mechanics come from the product itself. Screenshots of the Search Console sign-up screen, first published by Digiday, carry the exact strings “Start earning with AI contribution pilot” and “Accumulate earnings when your content contributes significantly to AI-generated responses in participating products”. The panel lists four functions: accrue earnings, manage participation, track earnings, and track payments, with a note that payments “may differ from your estimated earnings due to tax deductions or local payment thresholds”. Participation is managed in Search Console settings, including cancelling.
Everything else in circulation is reporting, not confirmation. Digiday’s sources say “at least dozens” of publishers were approached, that the pilot skews toward small and mid-size sites beyond news, that payment follows the value contributed rather than a flat license, and that one participating executive called the returns small and the system “quite black box”. None of that is on a Google page. Treat it as sourced reporting with the usual error bars.
How do I know if my site is in the pilot?
You almost certainly are not, and you can check in two places. First, open Search Console settings for your property. Pilot sites get an AI contribution entry there; everyone else sees nothing, and there is no application form. Second, there is a tell I have not seen anyone else point out: Google’s own help center already has a topic reserved for this program at support.google.com/webmasters/topic/16987401, and it renders empty. I loaded it while writing this, on 15 September 2026, and got a bare Search Console Help shell with no articles in it. The documentation exists in Google’s doc tree but is only visible to participants. When that page fills in publicly, the pilot has stopped being a pilot.
The doc-tree link was actually spotted back on 13 April 2026, months before anyone had screenshots, which tells you how long this has been moving.
How does this relate to the generative AI performance report?
The pilot pays for contribution to AI answers, and by no coincidence Search Console just learned to measure exactly that. The generative AI performance report finished rolling out to every property worldwide on 31 August 2026. It is the closest thing a non-pilot site has to the data the pilot presumably pays on, and I broke down its counting rules in how AI Mode traffic shows up in Search Console. Two of its limits matter here. It reports impressions for AI Overviews and AI Mode but does not split out clicks per surface, so even a pilot participant could not reconcile a payout against usage from this report alone. And its page dimension is the canonical URL, which means canonical mistakes on your site would misattribute whatever contribution Google measures. If you have duplicate-cluster problems, they just acquired a hypothetical price tag.
There is also a tension nobody in the coverage has raised. Search Console ships a control to limit your content’s use in generative AI surfaces, and I covered the mechanics in how to keep content out of AI Overviews. A site that applies those exclusions is, by definition, contributing nothing for the pilot to pay. Blocking and earning are opposite ends of the same setting, and sites that blanket-blocked AI surfaces in 2025 have quietly picked a side of it.
What should I check today if I am not in the pilot?
Three things, in order. Check Search Console settings for an AI contribution entry, so you know your actual status rather than assuming. Open the generative AI performance report and note your AI Overviews and AI Mode impressions, because that volume is your only proxy for whether Google’s AI surfaces use you at all; if you want to see what lands on the site side, I wrote up tracking AI Overview traffic in GA4. And review any AI exclusions you set defensively last year, not to reverse them, but to make sure they still reflect a decision rather than a default someone copied from a blog post.
I am not treating this as a revenue event for any site I manage. Digiday’s participating publisher called the money peanuts, and an early-stage pilot Google describes only as a “learning” exercise can vanish in a quarter. What I am treating it as: confirmation that Google now has plumbing to meter, attribute and pay for content used in AI answers, per property, inside the same console where we already work. That plumbing existing is a bigger fact than the current payout attached to it.
Sources
- Google public policy post, supporting the information ecosystem, 18 June 2026, for the grounding-partnership pilot confirmation and the other paid program figures
- Google Search Console Help, reserved AI contribution topic, loaded 15 September 2026 and empty for non-participants
- Google Search Console Help, the generative AI performance report, for the 31 August 2026 worldwide rollout and the report’s counting rules
- Digiday, Google rolls out pay-per-value AI licensing program to publishers, for the sign-up screenshots, the verbatim panel strings and the publisher-side reporting