I Made My Website Charge AI Agents A Penny Per Page, Then I Watched Claude Pay It via @sejournal, @suganthan
All Paid Media PPC News Social MediaAdvertising Video Advertising Columns Ask A PPC ExpertNEW PPC Pulse Webinar ChatGPT Ads Or GEO: What To Buy, What To Earn Audit where ChatGPT places your brand, then get the rule for when Ads win, when GEO wins, and when running both beats either one. Digital Marketing All Digital Marketing Analytics & Data Ecommerce Lead Generation Content Marketing Social Platforms Google YouTube Reddit LinkedIn TikTokNEW WordPress Other CMS Platforms Webinar Tactical Solutions For The Biggest AI Search Measurement Challenges Walk away with a prioritized set of AI search visibility metrics and the tactical steps to start reporting on them. SEJ Live Webinars Rundowns PodcastNEW Ebooks All Resources Webinar A New Place To Look: Where Your Next AI Citations & Clicks Come From Learn how to turn real customer language into AEO insights, FAQ content, and measurable AI citations and clicks with CallTrackingMetrics. Suganthan Mohanadasan 6 hours ago ⋅ 15 min read Suganthan Mohanadasan Co-founder at Snippet Digital Bio Follow Google is paying some publishers when their content helps generate its AI answers. Barry Schwartz covered it at Search Engine Roundtable on September 14, following Digiday’s report that morning. Google confirmed the program to Digiday. It’s called the AI contribution pilot. Publishers who accept the terms get an earnings figure in Search Console each month. What they don’t get is a breakdown of how Google calculated it. Google pays when it decides a page contributed significantly to an answer while it was being generated in AI Overviews, AI Mode, or the Gemini app. If the page only gets linked after the answer has been written, it doesn’t qualify. I’m not in the pilot. According to Digiday, Google has approached at least dozens of publishers, with smaller publishers showing more interest than the larger ones. One executive familiar with it described it as a black box. Barry had actually found the help page back in April, but it wasn’t clear then what the feature did. The sign-up screen publishers in the pilot see in Search Console. Image published by Search Engine Land on 14 September 2026. I’ve been testing a different approach on my own site since August. My page sets a price before an agent reads it. If the agent wants access, it pays. On the morning of September 15, five payments went through. Each one settled on a blockchain and has a public transaction hash. One came from Claude Code, running on my machine and using a wallet I’d set up for it. To be clear, all the payments so far have come from my own agents. No search crawler is turning up and paying me. The payments also use testnet USDC, which means the tokens have no real monetary value. But the payment process works. An agent requests a page, checks the price, pays and receives the content. Cloudflare is building products around that same idea, and I wanted to understand how it works before it becomes another setting in a dashboard. On August 4, during Agents Week, Cloudflare announced Wallets and opened handle reservations. Claiming a handle is free. I suspect plenty of people grabbed theirs the way we grab usernames: quickly, before someone else gets there, with a vague intention of reading the details later. If you did that, this is the kind of thing those wallets are being built for. As of September 15, though, reserving a handle gets you a page displaying the name and a notification when Wallets becomes available. Cloudflare’s documentation explicitly says a reserved handle can’t yet send, receive, or hold funds. The other part is the Monetization Gateway, which will let sites charge agents for access to resources. Cloudflare announced it on July 1, and access is still through the waitlist linked from that announcement. So the products are announced, but you can’t yet use a reserved wallet handle to run this whole process. My demo shows what that process looks like today using x402. The site charges one cent per page; my agent pays, and spending limits control what it can buy. It’s the same general arrangement Cloudflare describes for Virtual Wallets. The arrangement between search engines and websites used to be fairly straightforward. Search engines crawled your content, showed it in their results, and sent visitors back. Publishers got traffic. Search engines got something useful to show their users. AI answers have changed that arrangement. An agent can read your page, use the information in its response, and answer the user without sending them to your site. I’ve spent months looking at what these systems actually fetch. There’s plenty of crawling. The traffic coming back often doesn’t reflect it. Publishers have responded in different ways, partly depending on how much negotiating power they have. Smaller sites often block AI crawlers. I understand why. If someone is taking your content and you’re getting little in return, blocking them is a reasonable response. But it comes with a trade-off: restricting access can also reduce your visibility in training datasets and AI answers. Large publishers can negotiate licensing deals. News Corp, the Financial Times and Reddit all have agreements with AI companies. According to Press Gazette’s reporting on 4 September, People Inc.’s chief executive told investors that blocking crawlers through Cloudflare had helped bring AI companies to the negotiating table. Google’s pilot offers another approach: paying publishers according to the value their content contributes to AI answers. In that same Press Gazette piece, Cloudflare said it was moving its own default approach from pay per crawl towards pay per use, with pilots involving Ceramic.ai and You.com. Its reasoning was that fetching a page doesn’t prove the content was actually used. Using a page to answer a question is a stronger indication of value than simply downloading it. But it’s also something the website owner can’t independently observe. Once my page has left my server, I can’t see whether it influenced an answer. With pay per use, I’m relying on the platform to tell me what happened and what it was worth. With pay per crawl, I can check the request and the payment myself. Google’s eligibility rules make this particularly clear. As Barry Schwartz explains, contributing during answer generation can earn a payment. Being linked afterwards doesn’t. The publisher sees the total, without the calculation behind it. Blocking earns nothing directly. Individual licensing agreements don’t scale to millions of small websites. Revenue-sharing arrangements leave the platform deciding how much to pay. Putting a price into the request gives a site a standard way to sell access. An agent can accept that price and receive the content, with a receipt for the transaction. There’s no need to negotiate a separate commercial agreement with every buyer.
Source: Search Engine Journal
This article has been carefully curated and reformatted for educational and informational purposes. Full credit goes to the original publisher.
📚 Visit more helpful articles on Joab Peters Blog
No comments