Multiple crawler groups
Use wildcard, Googlebot, Bingbot, GPTBot or a custom user agent.
Configure crawler groups, path rules and sitemap declarations.
robots.txt output
User-agent: *
Crawler access control
Robots.txt is a public file at the site root that tells compliant crawlers which paths may or may not be fetched. Rules are grouped by User-agent and may declare sitemap locations.
It is not access control and does not reliably prevent indexing. Protect sensitive content with authentication and use noindex or removal responses for search-result control.
Use wildcard, Googlebot, Bingbot, GPTBot or a custom user agent.
Maintain rules per group and flag invalid paths or full-site blocking.
Add and deduplicate one or more absolute sitemap URLs.
One broad Disallow can block an entire site or critical resources, while invalid syntax may simply be ignored.
Set clear boundaries for admin, search parameters and low-value paths.
Flag full-site blocks, invalid paths, duplicate groups and unsupported directives.
Publish the canonical sitemap endpoints in the same root file.
All configuration is processed locally in the browser and is never stored.
Choose a common user agent or enter the exact crawler token.
Maintain Allow and Disallow paths for each group.
Add complete HTTPS sitemap URLs and remove duplicates.
Copy or download the file and serve it from /robots.txt.
Not always. A linked URL may still appear without a snippet. Use noindex on a crawlable page or remove the page when indexing must stop.
No. It is public. Protect private areas with authentication, authorization and network controls.
Googlebot does not support Crawl-delay in robots.txt. Manage crawl behavior through site performance, response status and Search Console.
Major crawlers generally use the longest matching rule. Avoid relying on ambiguous equal-length conflicts.
At the protocol and host root, for example https://example.com/robots.txt.
After publishing, check the real response, group parsing and path behavior.