Check the path and the file together
Use the URL of the page you care about, including its path. Paste the current robots.txt content or the proposed rules you want to review. The tool shows the selected group, matching line and resulting rule decision.
This is a supplied-file analysis. A file you paste can differ from the file a provider receives; firewalls, redirects, headers, authentication and actual provider traffic are not tested.
Understand the rule selection
Specific user-agent groups take precedence over the wildcard group. Matching repeated groups are combined. For a path, the longest matching rule wins; Allow wins when equally specific Allow and Disallow rules match.
Paths are case-sensitive. Wildcards, end markers, encoded characters and query strings can change the result. The robots guide shows why a rule that appears broad may not apply to the path you intended.
Separate search discovery from training
OAI-SearchBot and GPTBot serve different documented purposes. Google-Extended is a robots control token rather than a separate HTTP user-agent and does not control Google Search indexing. User-triggered fetchers also need their own provider-specific interpretation.
Read the linked provider documentation next to each result. A displayed “Rule permits” does not mean that provider has successfully fetched the page.
Make one change you can verify
Save the current file and the intended rule change. Check a public page and a restricted path before deployment. After publishing, inspect the actual served robots.txt and use logs or an appropriate crawl test to establish network behavior.
Keep indexing declarations and canonical checks in the technical GEO audit; robots permission alone does not decide search indexing or citations.
Sources and further reading
Examples marked illustrative are not customer measurements.