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.

Model Context Protocol (MCP) servers turn Google Search Console from a place you click through into a place an AI assistant can actually query, slice, and reason about. Instead of exporting CSVs every time you want to look at content decay or quick-win opportunities, you ask your assistant — and the server pulls the live API data, runs the analysis, and reports back. The catch: there’s no official Google-built GSC MCP server yet. There’s an open issue on the google/mcp repo asking for one, but as of late April 2026 the entire space is community-built. That’s roughly 30+ open-source servers and a handful of hosted SaaS endpoints, all of varying quality, maintenance, and security posture.

For decades, the field of User Experience (UX) has been obsessively focused on the human primate. We mapped eye-tracking heatmaps to understand where human gaze lingered. We agonizingly optimized button colors to trigger dopamine hits. We designed for the thumb, the swipe, and the fleeting human attention span. But the web of 2026 is fundamentally different. The fastest-growing demographic of web users does not have eyes, thumbs, or dopamine receptors. They are autonomous AI agents.

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.