Could Microsoft kill the web browser at Build? Everything developers need to know about the NLWeb Protocol
Microsoft's NLWeb Protocol aims to transform how websites respond to user queries by allowing natural language interactions. Announced at Build 2025, this open-source project seeks to integrate AI capabilities directly into web properties. The upcoming Build 2026 event will reveal whether NLWeb is ready for broader adoption or remains an experimental concept.
- ▪NLWeb stands for Natural Language Web and allows websites to respond to natural language queries.
- ▪The protocol was introduced by Microsoft at Build 2025 and is designed to enhance AI interactions with web content.
- ▪NLWeb operates on top of the Model Context Protocol (MCP), connecting website content to AI systems.
TechRadar publishes from United Kingdom and files mainly under tech. We currently carry 1,301 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | TechRadar |
| Canonical URL | https://www.techradar.com/pro/could-microsoft-kill-the-web-browser-at-build-everything-developers-need-to-know-about-the-nlweb-protocol |
| Publication time | Fri, 29 May 2026 21:25:00 +0000 |
| Retrieval time | 2026-05-29T21:31:38.746Z |
| Last seen | 2026-05-29T21:31:38.746Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | fShu20YaO6lu |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Pro Could Microsoft kill the web browser at Build? Everything developers need to know about the NLWeb Protocol Features By Ritoban Mukherjee published 29 May 2026 Making every website queryable by AI agents When you purchase through links on our site, we may earn an affiliate commission. Here’s how it works. (Image credit: Microsoft/O'Reilly) Jump To: What is it? How does it work? What to expect What does it mean? Copy link Facebook X Whatsapp Reddit Pinterest Flipboard Threads Email Share this article 0 Join the conversation Follow us Add us as a preferred source on Google Newsletter Subscribe to our newsletter The web browser has been the default interface for accessing online information for decades, but AI search is starting to change that assumption.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at TechRadar.