This post is the second half of a two-part argument. The first half examined llms.txt advertising and found it fails on delivery — the file almost never gets fetched, so the impression never happens. This half examines an advertising product where delivery is solved. The failure is one layer up. Disclosure: this site builds and operates agent-detection infrastructure. The verification gap described in the close is one this operation would benefit from commercially. The analysis is published because the argument follows from the evidence, not from the incentive.

In the early days of the web, “cloaking” was a dirty word. It conjured images of black-hat SEOs serving keyword-stuffed gibberish to search engine spiders while presenting a pristine, albeit often irrelevant, page to human users. It was a deception, a slight of hand designed to game the system. Today, as we stand on the precipice of the Agentic Web, the concept of cloaking is being reimagined, rehabilitated, and repurposed. We are moving away from deception and towards Agent Experience Optimization (AXO).

Cloaking—the practice of serving different content to search engine bots than to human users—has traditionally been considered one of the darkest “black hat” SEO tactics. Search engines like Google have historically penalized sites severely for showing optimized text to the crawler while displaying images or Flash to the user. However, as we transition into the era of Agentic AI, the definition of cloaking is undergoing a necessary evolution. We argue that “Agent Cloaking” is not only ethical but essential for the future of the web.

The ultimate form of “white hat cloaking” is Content Negotiation. It is the practice of serving different file formats based on the requestor’s capability. HTTP Accept Headers If a request includes Accept: application/json, why serve HTML? Human Browser: Accept: text/html. Serve the webpage. AI Agent: Accept: application/json or text/markdown. Serve the data. The “Headless SEO” Approach This approach creates the most efficient path for agents to consume your content without navigating the DOM. Instead of forcing the agent to: