What agents see: the side-by-side preview
The preview fetches your URL twice — once as an agent, once as a browser — and tells you which world each one gets.
How the side-by-side works
Enter any URL of your store and press Preview. Rebilder fetches the page twice, one after the other: first as an agent would — with the Accept: text/markdown header and an honest rebilder-preview user agent — then as a regular browser. The two requests are sequential on purpose, to be gentle on your server.
Each side panel shows the HTTP status, content type, response size, an approximate token count (characters ÷ 4 — the rough industry heuristic, labeled “approx”), and the first stretch of the response body.
The verdict line
- Green: “Your store serves agents markdown” — with the token savings when both fetches succeed, e.g. “~328 tokens instead of ~22,789” on Rebilder’s reference capture.
- Amber: “Agents currently get your full HTML — install the gateway to serve them clean markdown.”
- Gray: the agent-side request failed, so no verdict could be made.
Why some URLs error
Because Rebilder’s servers fetch the URL you type, the preview only reaches public store pages:
- Only
https://URLs, on the standard port — plain http and custom ports are rejected. - Private or internal hosts are blocked: localhost, private IP addresses, and raw IPv6 addresses cannot be previewed. Use your store’s public domain.
- URLs with embedded credentials (user:pass@) are rejected.
- The page must answer within 5 seconds, with a 2xx status, in at most 3 redirects — and every redirect hop is re-checked against the same rules.