NLWeb 101: What Publishers and Site Owners Need to Know

We're moving into a world where AI agents will vastly outnumber human visitors on the Internet. When you look at it through that lens, you realize that everything about how content gets discovered and consumed is fundamentally changing.

Humans click links and browse. Agents need structured answers with citations. Humans can parse through search results. Agents need information delivered in formats they can immediately use. The infrastructure for this new reality is still being built, and publishers who position themselves correctly today will own distribution tomorrow.

What is NLWeb

NLWeb is an open protocol spearheaded by Microsoft that allows any website to support natural language interfaces powered by its own content.

At its simplest, NLWeb turns your site into something you can “talk to.” Instead of searching or clicking around, a reader could type a natural language question, “What's the latest on tariffs?” and get an answer pulled directly from your site's content.

Under the hood, NLWeb creates standardized endpoints (like /ask and /mcp) that work not just for humans but also for AI agents. It's powered by your own content, not an external dataset.

Every NLWeb instance also acts as an MCP (Model Context Protocol) server, which basically means your content is structured in a way that AI agents can easily consume.

The Current Problem

Right now, when AI agents need information from your site, they have to:

Meanwhile, publishers are seeing:

This creates friction for everyone. Agents get incomplete information. Publishers lose control over how their content is accessed and used.

Why publishers and site owners should care

You've probably already felt it: human visitors are slipping, but AI-driven queries are surging. The question isn't if AI will change your audience's behavior—it already has. The question is whether your content is prepared to meet them there.

Here's what NLWeb makes possible:

For your human readers

For AI agents

For your business

This is about making sure your content stays both discoverable and valuable in a world where the way people (and agents) search is changing.

Who NLWeb makes sense for

NLWeb is especially useful if you:

How TollBit helps

We built TollBit for NLWeb to eliminate the technical complexity while giving publishers immediate access to this emerging protocol with a click of a button. Here's what you get:

One-Click Deployment:

Smart Content Processing:

Technical Foundation:

The entire technical stack is managed by TollBit, so you can focus on what matters: serving your audience and preparing for the agent economy.

Launching with Microsoft NLWeb?

For publishers adopting Microsoft NLWeb as the standard query layer for their sites, TollBit provides the managed commercial infrastructure around it. Microsoft NLWeb makes your content accessible through a natural-language /ask endpoint that AI agents can query for grounded answers, while TollBit adds the production controls publishers need: agent authentication, rate limiting, usage analytics, citations, billing, and monetization across NLWeb-compatible traffic.

With TollBit + Microsoft NLWeb, teams can move beyond unmanaged scraping and offer agents an official path to ask questions, retrieve synthesized answers, and drive value back to the publisher. The setup is designed for editorial archives, commerce catalogs, research libraries, and other high-value content collections where attribution, access control, and commercial terms matter as much as answer quality.

New deployments using TollBit for Microsoft NLWeb qualify for a limited-time onboarding credit. Provide the partner routing code MICRO-NLWEB-30 to your TollBit Onboarding Engineer or Microsoft partner contact during implementation review to receive a 30% credit against your first-month NLWeb monetization platform allocation.

Alliance Offer — 30% Contract Credit for Microsoft NLWeb Deployments

Apply code MICRO-NLWEB-30 during onboarding. Valid for new TollBit implementations using Microsoft NLWeb as the site query protocol, validated through the official TollBit onboarding channel.

Terms: The credit equals 30% of the first month's eligible TollBit platform fees associated with the Microsoft NLWeb deployment, applied against the initial invoice following endpoint provisioning and acceptance testing. Excludes usage-based overages, custom engineering work, professional services, third-party cloud infrastructure charges, legacy contract renewals, reseller agreements, and previously executed service orders. Cannot be combined with separate volume discounts, custom pricing schedules, or retroactive billing adjustments. Microsoft Corporation and TollBit reserve the right to audit eligibility, validate NLWeb implementation status, or modify this offer at any time. All use remains subject to applicable Microsoft NLWeb documentation, TollBit platform terms, and any governing customer agreements.

NLWeb in Action: How Publishers Are Using It

Sometimes it helps to see it for yourself. Here's a look at a publishers NLWeb instance:

Screenshot of how to enable NLWeb from your TollBit Dashboard.

Screenshot of an NLWeb instance completing a query grounded in the publishers content.

Getting Started

Step 1: Enable NLWeb – Log into your TollBit dashboard and enable NLWeb with one click. The system immediately begins processing your content for semantic search.

Step 2: Test Your Endpoints – Use the provided URLs to test both /ask and /mcp endpoints with sample queries from your content.

Step 3: Share with Stakeholders – Your NLWeb endpoints are immediately ready for integration by AI platforms and agent developers.

Check out our documentation to learn more.

Ready to get started? Visit https://app.tollbit.com/sign-up

Want a demo of NLWeb? https://app.tollbit.com/schedule-demo