Agent Experience (AXP)

Agent Experience sits inside AI Visibility. For each page SearchChamp has already crawled on your site, it can generate a rendition: a clean markdown version of that page — the same facts, better structured, without the navigation, cookie banner, and script-driven furniture an AI crawler has to wade through in your rendered HTML.

A rendition is your page said more clearly. It is never a different page — that's enforced by an automated check before anything is published, not just a house style. See How renditions are checked.

We make no claim about how this affects citations. Independent studies of comparable mechanisms measured no effect on AI citations, and SearchChamp won't tell you otherwise. What it does is give agents a cleaner, verifiably equivalent representation of your pages, then measure what actually happens on your site — see Measuring impact.

If your plan or your crawl state doesn't qualify, the Agent Experience tab says which one it is rather than showing an empty list.

Turn it on and generate renditions

How renditions are checked

Every rendition is checked against its own source page by an automated equivalence review before it can be served. The review reads each statement in the rendition and classifies it as:

• supported — the claim is present in the source page;
• added — the claim is not in the source page;
• contradicted — the claim conflicts with the source page.

An added or contradicted statement above the severity floor rejects the whole rendition. A rejected rendition is stored so you can read it and the reviewer's reason in the app, and it is never written to the serving path — there's no code path that publishes an unjudged or rejected rendition. A truncated review response counts as a rejection, never a pass.

The two ways renditions can be served

Once renditions exist, you separately choose whether and how to serve them. Neither channel is on until you turn it on.

(a) The agent bundle — no acknowledgment required. SearchChamp publishes your active renditions to its own CDN under an opaque, per-site path: a bundle index plus one markdown file per page. Nothing is installed on your infrastructure. You decide what to do with the path — link it from your own robots.txt or llms.txt, download the export bundle, or point a small worker at it. If you never link it, nothing changes about how your site behaves.

(b) The crawler middleware — opt-in, and gated behind a risk disclosure. A small snippet you install on your own edge (Cloudflare or Vercel). For mapped AI crawler user agents only, and only while this channel is enabled, it answers on your existing URLs with the rendition instead of the rendered page. Any other visitor — a person, a search engine, an unmapped bot — passes straight through to your origin, untouched. If the rendition can't be fetched for any reason, the snippet fails open to your original page.

Both channels serve renditions with a noindex directive and a canonical pointer back to the original page, so a rendition never competes with your page in classic search.

Before you enable the middleware channel

Enabling channel (b) requires reading and acknowledging a risk disclosure first — the toggle is rejected outright without a current acknowledgment. Your acknowledgment is stored with who accepted it, when, and which version. If the disclosure changes materially, you're asked to accept it again before the channel can be re-enabled.

The disclosure covers, in summary:

1. Serving different content to a crawler than to a person is something search engines can treat as cloaking if it isn't kept honest — the equivalence check exists to keep you inside the line, but you're enabling a response that varies by user agent, and you own that decision for your domain.
2. The middleware runs on your infrastructure, not SearchChamp's. You can remove the snippet at any time, independently of anything SearchChamp does.
3. Renditions are served noindex with a canonical pointer back to your original page.
4. The master kill-switch (below) deletes every published rendition and invalidates the CDN — serving stops within about 60 seconds, and the snippet falls back to your original page automatically whenever a rendition is unavailable.
5. There's no evidence serving renditions increases how often AI engines cite you. The impact panel exists so you can see what actually happens on your own site rather than take that on faith.

Channel (a), the agent bundle, doesn't require this acknowledgment.

The kill-switch

One control stops everything. Firing the master kill-switch disables both channels, deletes every published object under your site's serving path, and invalidates the CDN for it, in a single awaited action. Published renditions carry a 60-second cache lifetime, so the worst case for an edge that hasn't yet seen the invalidation is about 60 seconds.

If the delete or the invalidation fails, you'll see an error — it's never reported as a silent success.

Measuring impact

The impact panel is the only claim this feature makes, and it's a claim about your site, not about the feature in general.

It compares two equal-length windows — one before your first activation, one after — and reports, per engine:

• your citation rate, from citations already recorded by AI Visibility; and
• your integrity issue rate, from the brand-accuracy checks already running against those same answers.

Both are computed from data already stored — nothing is back-filled, estimated, or modelled.

Each window needs a minimum of 7 days of data on each side. Below that, the panel reports insufficient data and says why — it won't compare a three-day "before" against a thirty-day "after" and hand you a number that looks authoritative and means nothing. An empty window is never rendered as a zero.

And it will tell you when nothing changed. SearchChamp doesn't claim that serving renditions increases AI citations, and the panel is built to report a null result as readily as a positive one — if your rates are flat on both sides of activation, that's what you'll see.

Plan availability

Agent Experience requires a Business plan or above, a connected site, and a completed audit crawl. It isn't available on a trial.

FAQs

Is Agent Experience active on my site right now? Only if you've turned on the master switch and generated renditions. It's off by default for every site until you enable it — nothing is generated or served on your behalf.

If I only turn on the agent bundle, does that change what a normal visitor or search engine sees? No. The bundle publishes to SearchChamp's own CDN at an opaque path; it doesn't touch your site's responses at all unless you separately link to it. Only the middleware channel (b) changes what your own URLs return, and only to mapped AI crawler user agents.

What happens if I turn off the master switch after enabling serving? Use the kill-switch to stop serving and delete published renditions immediately; turning off the master switch on its own stops new generation but doesn't retroactively unpublish what's already served — use the kill-switch for that.

Will enabling this get me more AI citations? There's no evidence it will, and SearchChamp doesn't claim it does. The impact panel measures your own before/after citation and integrity-issue rates so you can see the real effect on your site rather than take a marketing claim on faith.

Related articles

• AI Visibility reference
• Track AI crawlers
• llms.txt Generator