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, and mobile was 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 treating mobile as a nice-to-have to treating it as a ranking factor. AI agent readiness looks like it is at a similar early stage, and this article argues that it may move faster.

The m.example.com Era

Before responsive design, the web went through a phase of separate mobile interfaces. Facebook had m.facebook.com and Google had mobile.google.com. ESPN, BBC, Wikipedia and Amazon also built a second, simpler version of their site for phones. That worked for a few years, then became hard to maintain.

The problems were clear. Sites had two codebases, two sets of content and two URL structures. SEO suffered because Google had to work out which version to index, users shared mobile links that broke on desktop, and 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. By 2016, Google reported that 85% of pages in mobile search results met its mobile-friendly criteria. Responsive design had become a baseline expectation instead of a feature.

Being late had a measurable cost. 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.

Where We Are Now

AI agent readiness is in its own m.dot phase. Companies that see the shift are adding 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 growing fast. 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 again: one interface for humans, one for machines, two sets of documentation and two ways to discover what a service can do. It works for now, but maintaining two interfaces is likely to become as costly as maintaining two websites was.

The Convergence

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

Agent readiness may follow the same path. Separate agent APIs, bolted-on MCP servers and standalone llms.txt files look like symptoms of an early phase. A likely long-term pattern is one content layer with multiple consumers.

Much of the groundwork exists already. According to W3Techs, 53% of websites now use JSON-LD for structured data. Headless CMSs decoupled content from presentation years ago, and content negotiation lets the same URL serve HTML to browsers and markdown to agents. These are established web standards 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. These numbers come from a survey of executives, not from developer enthusiasm.

The Personal LLM Layer

Here the analogy goes further than responsive design did. Responsive design made one site work across screen sizes, but every visitor still got the same layout, the same content order and the same information hierarchy. The only variable was screen width.

With AI agents as intermediaries, the variable becomes the user: their preferences, their context and their history, instead of their device. Say you look at a product page through your personal LLM layer. It shows the specs that matter to you, in the format you prefer, compared against alternatives you have been considering. Someone else sees the same product data with a different presentation.

Parts of this already exist in products. 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 are 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. If agents take over more of these visits, the browser becomes one of several ways to render 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 are reasons to expect the agent transition to move faster.

Mobile required new infrastructure: touchscreens, app stores, mobile browsers and cellular networks that could handle real web browsing. The agent transition builds on infrastructure that already exists. APIs are widespread, structured data is on 53% of websites, and HTTP content negotiation is a 25-year-old spec. What is still missing is a change in mindset, 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, it has been three and a half years since ChatGPT (November 2022). MCP went from zero to 19,646 registered servers in sixteen months, and both ChatGPT and Claude support it. Many major IDEs support it too. The protocol layer appears to be converging quickly, though the table above shows only how the two timelines line up, not that agents will reach baseline sooner.

What to Do Now

If you were building a website in 2012, going responsive was the right move. The reason was not the Google penalty three years later. Mobile traffic was growing, and maintaining two separate sites was unsustainable. Companies that moved early got a better mobile experience, better SEO and lower maintenance costs.

The same logic applies today. You do not need to implement every protocol, but you can treat your content as data that several consumers will access through different interfaces. In practice, that means three levels of work:

The Pattern

The mobile shift followed a clear arc, and the agent shift may repeat it. 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 becomes too complex to maintain. For mobile, the answer was convergence on one content source with adaptive presentation.

Responsive design showed that one adaptive site beats separate experiences. For agents, the same idea goes one level deeper: the site adapts its content delivery to the consumer asking for it, and layout is only part of that.

Early responsive adopters gained a better mobile experience and lower maintenance costs. Sites that adopt one content source for humans and agents early may see similar savings, and the alternative is to keep maintaining a separate agent interface next to the main site.

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)