Publish for AI agents without touching your website

You can change what AI agents read on any page of your site, and publish new pages for them, without editing the human page, without a CMS integration and without an engineering ticket. The Agent Site CMS works on the agent-facing version of your site, which is produced from your human pages at fetch time and served to identified AI agents only.

Three views of every page

Open any URL on your site in the Agent Site CMS and you see three things side by side.

  1. The human page. What a person sees in a browser. Read-only here, because nothing in this tool touches it.
  2. What bots get today. The current agent-facing rendering of that page: the server-rendered text or slim HTML an AI agent receives when it fetches the URL. For most teams this is the first time they have seen their own site the way ChatGPT-User or Claude-User sees it, and the first thing they notice is what is missing.
  3. The editable bot version. The rendering you can change. Reorder sections so the answer comes first. Add a specifications table that on the human page lives in a PDF. Remove a promotion that expired. Add the three sentences that answer the question agents keep fetching this page to answer.

Save, review, publish. The next time an identified agent fetches that URL, it receives the new version. The human page is unchanged.

Net-new pages

The same tool publishes agent-only pages: pages that answer a question agents ask and that have no counterpart on the human site. Comparisons, FAQs with real answers, spec sheets as text, "is X safe" and "does X work with Y" pages. Each one is added to the bot-only sitemap on publish and carries a fallback, so a human who clicks a citation of it lands on the closest real page.

Per-platform versions

Agents from different platforms behave differently. One reads a page in full and cites it, another extracts a fact and cites nothing, a third needs a form left intact. The Agent Site CMS lets a page carry versions per platform, so the version served to OpenAI's agents can differ from the one served to Anthropic's or Amazon's, with the same facts in each.

Most pages need one version. The option exists for the pages where the logs show agents from one platform failing on a page that others read fine.

Review before publish

Every change is saved as a draft and reaches agents only when it is published, so legal, brand and product teams can review the bot version exactly as an agent will receive it. Nothing goes live to agents that has not been seen by a person with the authority to say so.

The rule the review enforces is the same-facts rule: the agent version may say nothing that is false on the human site. Same facts, cleaner format, bots only.

Why no engineering ticket

The agent site is served from a subdomain of your domain that identified AI agents are routed to by your CDN or WAF. It is not inside your CMS, your front end or your deployment pipeline. Publishing to it changes nothing in those systems, so the teams that own them are not in the loop for an edit, and the people who own the facts can act on what the logs show the same week.

That also means no integration project. The agent site reads your human pages over HTTP, like any visitor. It does not need a plugin for your CMS, a connector for your DXP, or access to your repository.

Closing the loop

Publishing is half the job. The same server logs that showed which pages agents were fetching, and failing on, show whether the new version is being read, by which agents, and how often. Recrawl varies by platform, from hours to weeks.

Where TollBit fits

The Agent Site CMS is TollBit's publishing surface on top of the bot CDN. TollBit is the origin for AI agent traffic on your domain, serves the robots.txt and bot-only sitemap agents read, resolves citation fallback, and shows reads in server logs from the same rail. Setup is two IT changes, forward server logs and point a subdomain. After that, publishing is a marketing or commerce task, not an engineering one.

Frequently asked questions

What happens to the human page when I edit the bot version? Nothing. The human page is fetched from your origin and never written to. Humans are never routed to the agent site.

What if the human page changes after I edited the bot version? The human page stays the source of truth. When it is republished, the refreshed page replaces the edited bot version until you review and re-apply the edit, so an edit never pins a stale price or claim.

Can marketing publish without engineering seeing it? Yes, within the approval flow your company sets. Engineering is involved once, at setup. After that the review step belongs to whoever owns the content.

Related