NLWeb Is Microsoft’s Bet That Every Website Will Eventually Need to Be Readable by Agents, Not Just Humans

The sharp version: if HTML helped websites talk to browsers, NLWeb is Microsoft’s argument that the next layer is helping websites talk to agents. That should make the whole publishing and web-product ecosystem sit up straight.

Why NLWeb matters

At Microsoft Build 2025, Microsoft introduced NLWeb, which it said could play a role similar to HTML for the agentic web. The company later explained that NLWeb is an open project designed to make it simple to give websites a natural language interface using the model of your choice and your own data.

That is a very ambitious framing.

And ambitious framings are worth paying attention to when they point at infrastructure.

Why this is bigger than “chat on your site”

It is easy to misread NLWeb as “put a chatbot on a webpage.”

That is too shallow.

Microsoft also said every NLWeb endpoint is an MCP server, allowing websites to make their content discoverable and accessible to AI agents if they choose.

That changes the story completely.

Now the question is not only:

1. can a user chat with your site

It becomes:

1. can agents understand your site
2. can agents retrieve your site’s knowledge cleanly
3. can your content participate in the wider agent ecosystem
4. what happens if competitors become easier for agents to work with than you are

That is not a UX tweak. That is web architecture pressure.

Why this should make publishers and product teams nervous

The web has long been optimized for human reading, navigation, and attention capture. If more of the traffic and decision flow becomes agent-mediated, then the businesses that win may be the ones that are easiest for agents to query, interpret, and act on.

That puts pressure on:

1. content structure
2. schema and metadata
3. API and protocol design
4. discoverability for machine consumers

Weakly structured sites may still look fine to human visitors while becoming second-rate participants in an agentic ecosystem.

That is the kind of shift people notice too late.

Why the “open project” framing matters

Microsoft is not only selling a product here. It is trying to shape a standard-like direction for the web. If enough sites adopt agent-readable conversational layers and MCP-compatible endpoints, then being absent from that layer may eventually feel like not having responsive design in a mobile era.

That sounds dramatic.

It is also how platform transitions tend to start:

1. first optional
2. then helpful
3. then expected
4. then table stakes

NLWeb is early, but the direction is obvious.

And once the direction is obvious, planning starts early for the teams paying attention. The rest usually wait until agent-readable infrastructure stops sounding optional and starts showing up in procurement, platform strategy, and traffic outcomes.

The real takeaway

NLWeb matters because it suggests the web may increasingly need to serve two audiences at once:

1. humans who browse
2. agents that query, summarize, route, and act

Once that becomes normal, a lot of old website assumptions break.

And the companies that adapt first will likely get a visibility and workflow advantage that late adopters struggle to claw back.

Sources

• Microsoft Build 2025: The age of AI agents and building the open agentic web
• Microsoft Source: Introducing NLWeb