Google launched WebMCP.
Cloudflare launched Markdown for Agents.
On the surface, these sound like developer updates. Underneath, they represent something much bigger:
The internet is being refactored for AI agents that don’t browse, they just execute.
And if you’re responsible for digital strategy, ecommerce, CX, or brand infrastructure, this is not a “tech team” story. This is a competitive positioning story.
WebMCP (Web Model Context Protocol) is Google’s move toward structured, tool-based interaction between websites and AI agents.
Today, when an AI agent wants to complete a task on a website, book a flight, submit a form, configure a product, it has to do a few things:
That’s brittle. Expensive. Error-prone.
WebMCP changes that dynamic.
Instead of forcing agents to reverse-engineer your interface, websites can expose structured “tools”, clearly defined actions with parameters.
Instead of an agent clicking around your UI trying to figure out how to “Request a Quote,” your site just exposes:
Tool: request_quote
Inputs: product_id, quantity, contact_info
Output: confirmation_id
Now the agent doesn’t “browse.”
It calls a capability. Period.
This is the difference between:
And that’s honestly a really big deal.
Cloudflare’s release may sound simpler, but it’s equally important.
Agents don’t need styled HTML. They need clean, structured, semantic content.
Cloudflare now allows websites to serve clean markdown versions of pages to AI agents. When an agent requests content, Cloudflare can convert HTML into markdown on the fly.
Because HTML is built for rendering. Markdown is built for meaning.
For agents, markdown is:
This reduces token usage, lowers compute cost, and improves reliability. If you don’t think that agents will prioritize systems that clean it up for them your crazy.
Translation: AI systems can consume your content more efficiently, and more accurately.
That’s not an SEO tweak. That’s a machine-readability shift.
This Is Infrastructure for an Agent-Acting Web
For the last 25 years, the web was optimized for:
But we are moving into a phase where, AI agents will:
Not as a novelty. As a default behavior. When that happens, the winning sites won’t just look better.
They’ll expose cleaner capabilities.
This isn’t about ripping and replacing your stack tomorrow. That would be too easy honestly.
It’s about thinking differently, asking better questions and making sure you make them actionable and efficient.
If your content is:
Agents will struggle.
It will be all about semantic and capability optimization.
Start mapping:
If these are business-critical actions, how might they eventually be exposed as structured tools?
WebMCP makes this direction explicit.
Brands should begin identifying which core interactions should become machine-callable services.
Cloudflare’s markdown approach highlights something we’ve been saying for a while:
Content is no longer just persuasion.
It’s infrastructure.
If your knowledge center, product detail pages, FAQs, and thought leadership aren’t cleanly structured, you’re limiting how effectively AI systems can retrieve and cite them.
Structured publishing isn’t a trend. It’s table stakes for machine discovery now.
We’ve spent decades optimizing for:
The next layer is Agent Experience.
How easily can a non-human system do any of the following:
That’s not science fiction. It’s infrastructure being deployed right now.
What will your digital ecosystem be?
A brochure?
Or a system?
The shift is already underway.
The brands that treat this as a developer curiosity will lag behind the ones who treat it as strategic mandate for learning and implementation.
Here’s the part that matters strategically.
When agents start acting on behalf of consumers, the brand with:
Will win the battle for screen space in ChatGPT, etc. Their systems will be more interoperable.
Brands that invest should so so in areas related to:
This dramatically improves the systems that agents interact with.
We don’t see WebMCP and Markdown for Agents as isolated features.
We see them as signals.
Interface-first
to
Infrastructure-first.
Built together. Not bolted on later.
We’d love to hear how others are preparing for a web where agents don’t scroll…
They execute. Share your thoughts.
