Every guide is mapped 1:1 to an active check key so you can move from warning to fix without guesswork.
Content Signals let you publish machine-readable AI usage preferences in robots.txt. This check is optional, but if you use it, the syntax needs to be valid and aligned with your actual crawl policy.
Open guide
This check is about consistency. Scavo compares page-level opt-out directives, wildcard robots behavior, and `/llms.txt` so you can catch mixed signals before they create visibility drift or internal confusion.
Open guide
Link headers give agents a lightweight way to discover machine-readable resources such as API catalogs and service descriptions. If you advertise them, they need to resolve cleanly.
Open guide
Serving Markdown or plain text when a client explicitly asks for it can make content cheaper and easier for AI systems to parse. It is optional, but the request should never break your route.
Open guide
If agents or third-party clients need OAuth to access your service, they should be able to discover the correct authorization metadata without guessing endpoints by hand.
Open guide
If your service exposes machine-usable tools, APIs, or agent endpoints, discovery documents can tell clients what exists before they start guessing. Broken discovery docs create more friction than having none at all.
Open guide
Web Bot Auth lets bots prove who they are with signed HTTP requests and published keys. It is optional for most sites, but if you use it, the key directory must be valid and public.
Open guide