AI Discovery

Keep the owner workflow simple: start with the Workspace-generated production snippet, add the well-known card if you want stronger generic-agent discovery, and treat everything else as optional.

Required

Use the Workspace-generated install path first

Direct installs: open Install & Test, copy the production snippet, and paste it before </body>.

Webflow-managed installs: Rover already deploys the required runtime bundle and head discovery tags for you. Re-open managed setup from Setup when you need to reconnect or republish.

Baseline discovery: when AI Task Access is enabled, the generated snippet already emits Rover's in-page discovery marker and inline agent-card hint.

Recommended

Publish the generated well-known card

If you do one extra thing beyond the snippet, make it the generated agent-card.json file from Workspace. Publish it at:

/.well-known/agent-card.json

This is the cleanest additional discovery surface because it stays generated from Workspace instead of asking site owners to invent schema by hand.

Optional

Add `service-desc` only if you control head tags or headers

Workspace also generates pointer surfaces that tell agents where the well-known card lives. Use one of these if you control HTML head output or server/CDN headers:

HTTP `Link` header

Link: </.well-known/agent-card.json>; rel="service-desc"; type="application/json"

This belongs in app server, CDN, or reverse-proxy header config.

HTML head tag

<link rel="service-desc" href="/.well-known/agent-card.json" type="application/json" />

This belongs in <head>, not in the Rover boot snippet.

Optional support only

Treat `llms.txt` as a supplement

Workspace can generate an llms.txt addendum, but Rover should already be discoverable from the production snippet and the well-known card. Use it only if you specifically want that extra machine-readable surface.

Webflow-managed sites

Required install: Rover handles the managed runtime deploy for you.

Advanced artifacts: only publish the generated well-known card, `service-desc`, or `llms.txt` if you also control the live origin, CDN, or another route to publish those files/headers.

Workspace split: use Setup for editing and Install & Test for the generated outputs and portable test config.

Related guides

Quick Start for the required production install path.

Install & Test to copy the generated snippet, test config JSON, and discovery artifacts.

Try on Other Sites for Helper, Console, Bookmarklet, and Live Test flows.