The EU AI Act became enforceable on 2 August 2026. Most ecommerce teams have spent the summer worrying about AI labelling requirements on their product pages. The regulation that actually binds them shipped in April 2024, inside the Google Merchant Center feed spec — not from Brussels. The EU Act’s text-labelling duty almost certainly does not apply to your product descriptions. The rule that does apply has been live for over two years, and most stores are quietly non-compliant. This article is a companion to the technical breakdown of AI watermarking and Article 50, which covers mechanism and the three-layer regulatory structure in full. Read that first or after — you can follow this piece either way.

A writer drafts a 1,200-word analysis piece. The ideas are entirely their own — the structure, the argument, the research. They run the draft through Claude to catch awkward phrasing and tighten two passages. Then they publish. The published text now carries an imperceptible, statistically embedded mark indicating that a language model processed it. The ideas have not changed. The mark cannot be seen by any reader, cannot be read by any tool without Anthropic’s private key, and cannot be stripped without degrading the text. Nothing about who thought what has been recorded.

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.

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.

The web architectural landscape is experiencing a profound transition from deterministic human browsing to semantic-driven, autonomous traversal. In previous analyses, such as Agentic Cloaking: Introducing AXO (Part 1) and Level 0 Agentic Cloaking with Static Web Content, we established the foundational concepts of serving specialized content to agents versus humans. However, before you can effectively cloak or route content, you must first answer a critical question: Who—or what—is actually requesting this page?

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 our previous analysis, Effect of Nofollow on LLM Training, we established a grim reality for the privacy-conscious webmaster: AI training bots do not respect the rel="nofollow" attribute. For two decades, nofollow was the gentlemen’s agreement of the web. It was a digital “Do Not Enter” sign that search engines like Google and Bing respected to manage authority flow (PageRank) and combat spam. It was a protocol built for an era of retrieval, where the primary value of a link was the endorsement it carried. If you didn’t want to endorse a site, you added the tag, and the “juice” stopped flowing.