Google-Extended robots.txt checker, no signup

Check Google-Extended without blocking Googlebot by accident.

Paste your robots.txt and review whether Googlebot stays open for Google Search while Google-Extended, GPTBot, OAI-SearchBot, Applebot, PerplexityBot, and CCBot are handled as separate policy choices.

Fast answer

Use separate rules for Googlebot and Google-Extended.

If you want normal Google Search traffic, do not blanket-block User-agent: * or Googlebot just because you want to restrict certain AI-use controls. Use a separate Google-Extended rule and run this checker before publishing.

  • Use this page for: google extended robots txt checker, Google-Extended robots.txt, block Google-Extended not Googlebot, and Google-safe robots.txt reviews.
  • Output: copyable audit report with crawler status, sitemap note, and policy risk summary.
  • Next step: if the pasted rules are wrong, open the Google robots.txt generator and generate a cleaner draft.
Check Google-Extended rules Generate safer rules Read Google-Extended guide
Search-safe Warns if Googlebot appears fully blocked.
AI-use policy Shows whether Google-Extended is allowed, blocked, or partially restricted.
Copy report Use the audit as a launch note before changing robots.txt.

Google-Extended robots.txt checker

Runs in browser
Generate fixed rules
Google-Extended audit report 

          

        

      


      

        
Crawler access summary

        
The checker parses common robots.txt groups and reports whether important crawler tokens are allowed, blocked, partially restricted, or allowed by default.

        

          

            Status
            
Waiting

            
Run the checker to review Googlebot and Google-Extended rules.

          

        

        

          

            
              

                Crawler
                Use case
                Status
                Why it matters
              

            
            
              
Run the checker to see results.

            
          

        

      


      

        
Recommendations

        

          

            
Keep Googlebot open for Search

            
If public Google Search traffic matters, confirm Googlebot is not fully blocked before publishing the file.

          

          

            
Document the policy date

            
Record when you changed Google-Extended, GPTBot, or OAI-SearchBot rules so future traffic changes have context.

          

        

      


      

        
Google-safe robots.txt review path

        

          

            1. Check
            
Paste the current file

            
Run the checker and confirm Googlebot is not blocked by wildcard or explicit rules.

          

          

            2. Separate
            
Review Google-Extended alone

            
Treat Google-Extended as an AI-use control, not a substitute for Googlebot search crawling.

          

          

            3. Publish
            
Copy the report

            
Use the copied audit report in a pull request, support ticket, launch note, or client handoff.

          

        

      


      

        
Google-Extended robots.txt checker FAQ

        
Is Google-Extended the same as Googlebot?

        
No. Googlebot is the crawler token associated with Google Search crawling. Google-Extended is a separate product token for certain AI-use controls.

        
Should every site block Google-Extended?

        
No. It is a policy decision. The safer technical rule is to decide separately and avoid blocking Googlebot by accident.

        
What if the checker says Googlebot is blocked?

        
Review the exact group that matched Googlebot. If organic Google Search matters, generate a cleaner draft and retest before publishing.