Waiting
Run the live checker to review public /robots.txt.
Paste your robots.txt and review Googlebot, Google-Extended, OAI-SearchBot, GPTBot, Applebot, PerplexityBot, and CCBot status in one report. Use this when you searched for a googlebot robots.txt checker, google robots.txt checker, or a way to test robots.txt for Googlebot.
A safe review starts by checking whether User-agent: Googlebot or a wildcard User-agent: * group blocks public pages. Then check whether the file has a Sitemap: line and whether Google-Extended or training-use crawlers are handled separately.
Enter a public domain to fetch /robots.txt, check whether Googlebot is blocked, confirm sitemap presence, and review Google-Extended, OAI-SearchBot, GPTBot, Applebot, PerplexityBot, and CCBot separately. This endpoint does not fetch arbitrary paths.
Live Googlebot robots.txt check report Status: waiting Action: enter a public domain and run the live check.
Run the live checker to review public /robots.txt.
| Live check | Status | Detail |
|---|---|---|
| Run the live Googlebot checker to see results. | ||
If Google Search visibility matters, live /robots.txt should not fully block Googlebot or all public paths.
Review Google-Extended, OAI-SearchBot, GPTBot, and other crawler rules separately from normal Google Search crawling.
The checker parses common robots.txt groups and reports whether important crawler tokens are allowed, blocked, partially restricted, or allowed by default.
Run the checker to review Googlebot robots.txt access.
| Crawler | Use case | Status | Why it matters |
|---|---|---|---|
| Run the checker to see results. | |||
If public Google Search traffic matters, confirm Googlebot is not fully blocked by wildcard or explicit rules.
Use Google-Extended as a separate AI-use policy decision instead of turning off Googlebot.
| Step | Action | Pass condition |
|---|---|---|
| 1. Paste | Paste the current or draft robots.txt into this Googlebot checker. | Googlebot is not fully blocked for public pages. |
| 2. Review | Check wildcard rules, explicit Googlebot groups, private path blocks, and Sitemap presence. | Private paths are blocked without accidentally blocking search crawling. |
| 3. Separate | Review Google-Extended, GPTBot, and other crawler policies as separate choices. | Google-Extended policy does not imply Googlebot blocking. |
| 4. Publish | Copy the report, generate safer rules if needed, and verify the live /robots.txt returns HTTP 200. |
The final live file is documented and easy to retest. |
No. It only checks the pasted robots.txt rules. Indexing also depends on crawlability, content quality, canonical signals, internal links, HTTP status, noindex rules, and Google systems.
Only when you intentionally want broad crawling restrictions. If you want normal Google Search visibility, review broad wildcard blocks very carefully.
Use the Google robots.txt generator to create a cleaner draft, then retest before publishing.