Ops Lab Playbook: AI Visibility

Last updated: 2026-03-08

1. Purpose and when to use this

Use AI Visibility to understand how AI crawlers interact with your content, measure AI-referral traffic, score your pages for AI discoverability, submit URLs for faster indexing, and verify bot authenticity.

2. Included scenarios

1. AIV-01 Query AI crawler analytics: breakdown of crawler visits by bot name (GPTBot, ClaudeBot, Googlebot, Bingbot, etc.).
2. AIV-02 Query AI referrer attribution: traffic attribution from AI sources (ChatGPT, Perplexity, Claude, etc.).
3. AIV-03 Export AI visibility data (CSV): downloadable CSV export with ai_crawler dimension columns.
4. AIV-04 AI crawler with date range: date-bounded crawler analytics query.
5. AIV-05 Score content AI-readiness: evaluate pages on 10 readiness checks and return a weighted 0–100 score.
6. AIV-06 Get cached readiness scores: retrieve latest readiness scores from the most recent crawl run.
7. AIV-07 Submit URLs to IndexNow: push URLs to Google, Bing, Yandex, and Naver for faster indexing.
8. AIV-08 Verify bot authenticity: reverse-DNS + forward-DNS check to confirm a bot is who it claims to be.

3. UI workflow

1. Open https://app.10x.in/apps/ai-visibility.
2. Pick scenario from dropdown, configure mode (mock or live) and optional demo pack.
3. Fill in the handle and any required parameters (hostname, page data, bot user-agent, source IP).
4. Run request and inspect the response.

Readiness score interpretation

The AI-readiness score evaluates 10 checks per page:

IndexNow submission

IndexNow notifies search engines of URL changes for faster indexing. The platform handles key generation and provider-specific endpoint formatting.

Supported providers:

• Google: api.indexnow.org
• Bing: www.bing.com
• Yandex: yandex.com
• Naver: searchadvisor.naver.com

Bot verification

Bot verification uses a two-step DNS process:

1. Reverse-DNS: look up the hostname for the source IP.
2. Forward-DNS: resolve that hostname back to IP addresses.
3. Match check: verify the original IP appears in the forward-DNS results and the hostname matches expected domains for the claimed bot.

Known bot domains:

• GPTBot / ChatGPT-User → .openai.com
• ClaudeBot → .anthropic.com
• Googlebot → .googlebot.com, .google.com
• Bingbot → .search.msn.com
• Applebot → .apple.com
• Meta-ExternalAgent → .facebook.com, .meta.com

4. API workflow

Query crawler analytics

curl -H "Authorization: Bearer $JWT" \
  "https://ai.10x.in/v2/handles/{handle}/analytics?groupBy=ai_crawler&period=30d"

Score readiness

curl -X POST -H "Authorization: Bearer $JWT" \
  -H "Content-Type: application/json" \
  -d '{"pages":[{"url":"https://example.com","hasJsonLd":true,"metaDescriptionLength":155,"hasOgTags":true,"hasCanonical":true,"h1Count":1,"wordCount":850,"renderMode":"ssr","robotsBlocksAi":false,"hasSitemap":true,"hasLangAttr":true}]}' \
  "https://ai.10x.in/v2/handles/{handle}/site-intel/{hostname}/readiness-score"

Submit URLs

curl -X POST -H "Authorization: Bearer $JWT" \
  -H "Content-Type: application/json" \
  -d '{"urls":["https://example.com/page-1","https://example.com/page-2"],"providers":["google","bing"]}' \
  "https://ai.10x.in/v2/handles/{handle}/site-intel/{hostname}/submit-urls"

Verify bot

curl -X POST -H "Authorization: Bearer $JWT" \
  -H "Content-Type: application/json" \
  -d '{"userAgent":"Mozilla/5.0 (compatible; GPTBot/1.0; +https://openai.com/gptbot)","sourceIp":"20.15.240.64"}' \
  "https://ai.10x.in/v2/handles/{handle}/site-intel/verify-bot"

5. MCP tool access

External agents can use AI Visibility via MCP tools:

• ai_visibility_crawler_analytics — query crawler traffic
• ai_visibility_referrer_attribution — query AI referrer sources
• ai_visibility_readiness_score — score content readiness
• ai_visibility_submit_urls — submit URLs to IndexNow
• ai_visibility_verify_bot — verify bot authenticity

6. Failure modes and remediation

• Readiness score returns empty: ensure a crawl has completed and the summary.readinessScores field is populated.
• Submit-urls returns all error: verify IndexNow key is configured and target hostname is publicly accessible.
• Verify-bot returns verified=false for a known bot: the source IP may be from a CDN or proxy, not the bot's origin network.
• 400 invalid_json: verify submit/verify request bodies are valid JSON objects.
• 400 userAgent_required or 400 sourceIp_required: include both fields for bot verification.
• 401 unauthorized: verify JWT or PAT token.
• 403 forbidden: verify handle access and required scope.

7. Related links

• AI Visibility Overview
• Analytics Exports and Reconciliation
• Apps and MCP Tools