Agent policy

Our browsers identify themselves with a user-agent containing the string AgentReadyGo/1.0. The technical checks (homepage, robots.txt, sitemap) use the same identifier.

One audit is a few dozen page views, spread over several minutes, at a pace comparable to an attentive human visitor. Advertising, analytics, video and font requests are blocked at the browser level, which reduces the load further.

• No purchase, no payment, no order.
• No account creation, no password entry.
• No card number, bank details, or real personal data ever entered.
• No attempt to bypass a CAPTCHA or any anti-bot protection.
• No content modification, no review or contact message ever submitted.
• An order form may be filled in to reach the checkout page, never to confirm anything, and only ever with the address agentreadygo-audit@example.com — a reserved domain that cannot receive mail. No real person’s details are ever entered.
• No access to any private or authenticated area.

These limits are enforced in code — network-level blocking of payment domains, refusal of clicks on irreversible actions, filtering of sensitive fields — not merely by instructions given to the model.

Faced with a consent banner, the agent always picks the most privacy-preserving option available (decline, or essential cookies only) before any other.

If you want your site excluded, add the following directive to your robots.txt and contact us for a permanent exclusion:

User-agent: AgentReadyGo
Disallow: /

Note that broadly blocking AI agents mechanically degrades your Discoverability score — that is precisely one of the signals this product measures.

A rule naming AgentReadyGo stops us. A rule addressed to * does not, and you are entitled to know that before you buy, because it is a choice we made rather than something the standard settles.

The Robots Exclusion Protocol does not say that it binds only search indexers, and we do not claim it does. Our reason is narrower and practical: nearly every hosted storefront ships a default robots.txt that disallows /cart, /checkout and similar paths for all user agents, because those pages are worthless to a search index. Reading those defaults as a refusal would make it impossible to answer the one question a merchant orders this audit to have answered — whether an agent can complete a purchase — on the majority of stores, while the merchant has explicitly asked us to look.

So on the interactive path of an audit we follow directives that name us, and we do not treat a generic directive as an exclusion. Everything else on this page still holds: we identify ourselves, we keep to a human browsing pace, we never buy, never authenticate, and never attempt to defeat an anti-bot protection. If you would rather we stayed out entirely, the directive above naming AgentReadyGo does exactly that, and we honour it.