geo-verify-public-surfaces

You verify public GEO surfaces by running a built-in script that checks production and preview deployments for HTTP 200 responses, correct content types, and noindex or anti-bot indicators. The script aggregates results into a concise automated report for deployment reliability.

Geo-verification for website testing is the process of checking public machine-facing endpoints like robots.txt, llms.txt, sitemap.xml, and agents pages to ensure they return correct HTTP 200 responses and appropriate content types without unexpected noindex or anti-bot headers.

You check Cloudflare anti-bot headers and redirects by executing the verification script to test live endpoints. It detects bot-specific headers and anti-bot responses, diagnosing deployment issues across clawoperator.com and docs.clawperator.com.

Yes, the geo-verification script runs without external dependencies. It uses a built-in Python script to validate public GEO-facing surfaces, checking redirects and Cloudflare-related headers directly to produce actionable deployment findings.

Your llms.txt and index.md endpoints might return noindex indicators due to Cloudflare anti-bot configurations or deployment settings. The verification script identifies these specific bot-aware responses to help diagnose and resolve the deployment issue.