The Responsive Design Moment for AI Agents

In 2011, most websites had two options for mobile: a stripped-down m.example.com, or nothing at all. Desktop was the real site. Mobile was an afterthought, a separate project with a separate team, often maintained by an intern. The idea that a single codebase could adapt to every screen size sounded ambitious. Ethan Marcotte had just coined the term "responsive web design" in A List Apart , but adoption was in single digits.

That transition took about eight years. From the iPhone launch in 2007 to Google's mobile-friendly ranking update in April 2015, the web went from "mobile is a nice-to-have" to "mobile is a ranking factor." Today, AI agent readiness is at the same inflection point. And it's moving faster.

The m.example.com Era

Before responsive design, the web went through a phase of separate mobile interfaces. Facebook had m.facebook.com. Google had mobile.google.com. ESPN, BBC, Wikipedia, Amazon. Everyone built a second, simpler version of their site for phones. It worked, kind of, for a few years. Then it became unmaintainable.

The problems were obvious. Two codebases, two sets of content, two URL structures. SEO suffered because Google had to figure out which version to index. Users shared mobile links that broke on desktop. Features lagged on mobile because resources were split. By 2013, the m.dot approach was already declining.

The adoption curve tells the story. In 2012, roughly 11% of the top 10,000 websites used responsive design, according to research by Guy Podjarny at Akamai. By 2015, after Google's "Mobilegeddon" update penalized non-mobile-friendly sites, adoption accelerated sharply. By 2016, Google reported that 85% of pages in mobile search results met their mobile-friendly criteria. Responsive wasn't a feature anymore. It was a baseline expectation.

The business impact of being late was real. Adobe reported that sites not optimized for mobile saw a 12% decline in organic mobile traffic after Mobilegeddon. Some sites lost up to 35% of mobile search visibility. Skinny Ties, a small retailer, saw iPhone revenue increase 377.6% after their responsive redesign. O'Neill Clothing saw a 65.7% increase in iPhone transactions. The companies that moved early won. The companies that waited paid.

Where We Are Now

AI agent readiness is in its own m.dot phase. Companies that recognize the shift are bolting on separate agent interfaces next to their existing websites. Stripe built an Agent Toolkit that lets AI agents create Payment Links and manage Stripe objects via function calling. Salesforce launched Agentforce, reporting 30% service case deflection and 88% faster resolution times. Sentry built full content negotiation across their docs, authenticated pages, and CLI tools.

The protocol ecosystem is exploding. Anthropic launched MCP in November 2024. Sixteen months later, there are 19,646 MCP servers listed in registries and the specification repo has 81,492 GitHub stars. OpenAI adopted MCP in March 2025. Google launched A2A in April 2025 with 50+ technology partners. The W3C published a draft WebMCP spec in March 2026. And 849 websites now serve an llms.txt file for AI discovery.

This is the m.dot phase. Two interfaces, one for humans, one for machines. Two sets of documentation. Two ways to discover what a service can do. It works, for now. But it won't scale, just like maintaining two separate websites didn't scale.

The Convergence

Responsive design solved the two-interface problem by making one interface adapt to its context. Media queries detected screen size. The same content reflowed to fit. No separate codebase, no separate URLs, no duplicate maintenance.

Something similar is going to happen with agent readiness. The separate agent APIs, the bolted-on MCP servers, the standalone llms.txt files are all symptoms of the early phase. The long-term pattern looks different: one content layer, multiple consumers.

The infrastructure is already being laid. 53% of websites now use JSON-LD for structured data, according to W3Techs. The headless CMS movement decoupled content from presentation years ago. Content negotiation lets the same URL serve HTML to browsers and markdown to agents. These aren't new inventions. They're established web standards being applied to a new audience.

Accenture's Technology Vision 2025 survey found that 78% of executives agree digital ecosystems will need to be built for AI agents as much as for humans over the next three to five years. 77% say AI agents will reinvent how their organization builds digital systems. This isn't developer enthusiasm. This is enterprise planning.

The Personal LLM Layer

Here's where the analogy goes further than responsive design ever did. Responsive made one site work across screen sizes, but the experience was still the same for everyone. Same layout, same content order, same information hierarchy. The only variable was screen width.

With AI agents as intermediaries, the variable becomes the user. Not their device, but their preferences, their context, their history. You're looking at a product page through your personal LLM layer. It shows you the specs that matter to you, in the format you prefer, compared against alternatives you've been considering. Someone else sees the same product data, completely different presentation. The underlying data is identical. The experience is not.

The pieces for this are already shipping. Apple Intelligence processes requests on-device and through Private Cloud Compute, acting as an intermediary for email, messages, and web content. Google's Deep Research browses the web autonomously and synthesizes findings into personalized reports. Microsoft Copilot remembers details across sessions. These aren't prototypes. They're shipping products on hundreds of millions of devices.

Bill Gates predicted in late 2023 that within five years, everyone will have a personal AI agent that replaces most website visits. "You'll never go to a search site again, you'll never go to a productivity site, you'll never go to Amazon," he said. That timeline is aggressive, but the direction is clear. The browser becomes one of many rendering layers for the same underlying data.

Faster Than Mobile

The mobile transition took about eight years from catalyst to baseline. iPhone launched in 2007. Responsive became standard around 2015-2016. There's reason to believe the agent transition will move faster.

Mobile required building entirely new infrastructure. Touchscreens, app stores, mobile browsers, cellular networks capable of real web browsing. The agent transition builds on infrastructure that already exists. APIs are everywhere. Structured data is on 53% of websites. HTTP content negotiation is a 25-year-old spec. The transport layer is done. What's needed is the mindset shift: from "my website is for browsers" to "my content is for any consumer that needs it."

The catalyst-to-baseline cycle for mobile was roughly eight years. For agents, we're three and a half years in since ChatGPT (November 2022), and the infrastructure is already more mature than mobile infrastructure was at the same point. MCP went from zero to 19,646 servers in sixteen months. Both ChatGPT and Claude support it. Every major IDE supports it. The protocol layer is converging faster than mobile browsers ever did.

What to Do Now

If you were building a website in 2012, the right move was to go responsive. Not because Google would penalize you three years later, but because mobile traffic was clearly growing and maintaining two separate sites was clearly unsustainable. The companies that moved early had a compounding advantage: better mobile experience, better SEO, lower maintenance costs.

The same logic applies today. You don't need to implement every protocol. But you should be thinking about your content as data that multiple consumers will access through different interfaces. Concretely:

The Pattern

Every major web platform shift follows the same arc. A new consumer appears (mobile browsers, AI agents). The first response is a separate interface (m.dot sites, bolted-on agent APIs). That works for a while, then collapses under its own complexity. The sustainable answer is always convergence: one content source, adaptive presentation.

Responsive design taught us that adapting to your audience is better than building separate experiences. The AI agent transition is the same lesson, applied one level deeper. It's not just "adapt your layout." It's "adapt your entire content delivery to the consumer asking for it."

The companies that figure this out first will have the same compounding advantage that early responsive adopters had. Everyone else will be maintaining their m.dot equivalent, wondering why their AI visibility keeps dropping.

Sources

• Ethan Marcotte: Responsive Web Design (A List Apart, May 2010) — The article that coined the term
• Imperva 2025 Bad Bot Report — Automated traffic exceeded 51% of all web traffic for the first time
• Accenture Technology Vision 2025 — 78% of executives say ecosystems must be built for AI agents as much as humans
• W3Techs: JSON-LD Usage Statistics — 53% of websites use JSON-LD structured data
• Model Context Protocol (MCP) Specification — Anthropic's open standard for AI tool integration
• Google A2A Protocol — Agent-to-Agent communication specification
• WebMCP Draft Specification (W3C, March 2026) — W3C community group draft for browser-native agent tools
• llms.txt Specification — Jeremy Howard's proposal for LLM-friendly content discovery