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.

An AI Overview once reported that the cat on tamethebots.com held a job title. The cat’s name was Odd. The role was invented. The citation pointed to a plain-text file with no schema, no author field, and no inbound links — a file that had been live for roughly two weeks. That detail circulated widely. Less widely circulated: whether anyone else could reproduce it, where it came from, and what, precisely, it proves.

Imagine a rate card that does not yet exist. For $250 per month, your product appears in the recommended-tools section of a documentation site’s llms.txt, which is parsed by coding agents at the moment a developer asks what library to use. The agent fetches the file, reads the description string, and your product lands in context at the exact instant the decision is made. This is a coherent-sounding product. Adjacent versions are already being sold: paid brand mentions in AI Overviews, sponsored inclusions in AI-generated listicles, and placement in curated “agent context” resources. DiNardi’s audit in Search Engine Land found placements at $250 per mention, with PBN-style inventory selling at 10–15x backlink rates. The rate card for llms.txt is merely the logical next step.

In the Pre-Agentic Web, “Mobile First” was the undisputed law. For over a decade, SEOs and developers optimized for the thumb, the swipe, and the 375px viewport. But as we transition into the era of Agentic Traversal, the “Inference Window” is shifting the architecture back toward the desktop. The bottom line for 2026: Every major AI agent uses a desktop browser. If you want your site to be navigable by autonomous agents, you must prioritize your desktop layout—specifically at widths between 1024px and 1440px.

How the Popover API, Navigation API, Invoker Commands, View Transitions, and other new browser APIs change the game for AI agent interaction — and how to use them to make your site agent-friendly. Agentic browsers are here. ChatGPT Atlas, Perplexity Comet, Chrome’s Auto Browse, Vercel’s agent-browser — the list grows every month. But while plenty of ink has been spilled on the agent side of the equation, there’s been surprisingly little attention paid to a question that matters just as much: how do modern web platform APIs affect what agents can and can’t do on your site?

At least 60 SEO-related MCP servers now exist as of March 2026, spanning the full spectrum from keyword research to local SEO to AI visibility tracking. The ecosystem has matured rapidly since mid-2025: seven major SEO platforms have shipped official MCP servers (Ahrefs, Semrush, SE Ranking, DataForSEO, Serpstat, SimilarWeb, and Google Analytics), while Google Search Console alone has attracted 20+ community implementations. The most important finding for practitioners: official MCP servers from Ahrefs and Semrush are now remote-hosted with OAuth, meaning zero local setup — a significant usability leap. However, several third-party servers scrape data without authorization and should be avoided. Below is every SEO MCP server found, organized by category, with honest assessments of each.

In the modern web ecosystem, the concept of a “visitor” has irrevocably fractured. We are no longer simply hosting websites for human beings clicking through graphical interfaces. The transition to the Agentic Web implies that a massive—and growing—percentage of our traffic consists of autonomous agents, headless browsers, conversational AI crawlers, and algorithmic validation tools. In this new paradigm, understanding exactly how these entities interact with your server is not just a matter of curiosity; it is a foundational requirement for Agentic SEO.

The web architectural landscape is experiencing a profound transition from deterministic human browsing to semantic-driven, autonomous traversal. For thirty years, the HTML <meta> tag has lived in the <head> of our documents, an invisible set of instructions read only by browsers and search engine crawlers. We used them to set the character encoding, to define the viewport for mobile devices, and to whisper desperate pleas to Googlebot in the form of name="keywords".

The web architectural landscape is experiencing a profound transition from deterministic human browsing to semantic-driven, autonomous traversal. Agentic browsers—such as ChatGPT Atlas, Perplexity Comet, Opera Neon, and open-source frameworks operating on protocols like the Model Context Protocol (MCP)—do not “see” the web in the biological sense. Instead, they ingest, tokenize, and process the underlying code, Document Object Model (DOM), Accessibility Tree, and visual viewport streams. flowchart TD A[Static HTML page] --> B[HTML/DOM parse] B --> C1[Raw DOM & attributes] B --> C2[DOM-to-text extraction<br/>textContent-like / innerText-like] B --> D[Accessibility mapping<br/>roles, names, states] A --> E[Rendered pixels] E --> F[OCR / vision text recognition] C1 --> G[Agent context builder] C2 --> G D --> G F --> G G --> H[Agent actions / navigation / summaries] This transition fundamentally alters the surface area for search engine optimization, content governance, and web security. Because agents parse information that human users never visually render, a severe semantic divergence emerges between the user viewport and the agent context window. This divergence is the foundation of Agentic Cloaking.

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).