GEO & llms.txt Readiness Auditor avatar

GEO & llms.txt Readiness Auditor

Pricing

from $40.00 / 1,000 domain auditeds

Go to Apify Store
GEO & llms.txt Readiness Auditor

GEO & llms.txt Readiness Auditor

Audit which AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Googlebot, and 30+ more) your site allows or blocks, validate your llms.txt, and score AI-citability — with an exact prioritized fix list. Non-scraper, reads public well-known files.

Pricing

from $40.00 / 1,000 domain auditeds

Rating

0.0

(0)

Developer

Geo

Geo

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

11 hours ago

Last modified

Share

GEO & llms.txt Readiness Auditor — which AI crawlers your site allows or blocks

Find out — per domain — whether GPTBot, OAI-SearchBot, ClaudeBot, Claude-SearchBot, PerplexityBot, Googlebot and 18+ other AI crawlers can reach and cite your content, whether your llms.txt is valid, and whether your pages carry the on-page signals AI answer engines need. You get a GEO-readiness verdict, a score, and an exact prioritized fix list — per domain. Non-scraper: it reads only public well-known files (robots.txt, llms.txt, sitemap.xml) and one page's <head>, one polite request each, honoring robots.txt.

What makes it different

Most checkers just say a token is "present/absent." This one tiers crawler compliance, so you learn the truth:

  • A Disallow: PerplexityBot or Bytespider in robots.txt won't actually stop them — those operators are documented ignoring robots.txt (only a WAF will) — so we flag "ineffective block."
  • It separates AI-search/citation bots (blocking them = you vanish from ChatGPT/Claude/Perplexity/Google AI answers — a P0 error) from training bots (blocking them is a legitimate choice) from opt-out tokens (Google-Extended, Applebot-Extended — directives, not crawlers).

Use cases

  • Audit your own sites/subdomains before/after a robots.txt or CDN change.
  • Agencies: batch-audit a client portfolio and hand over a fix list.
  • Catch the silent killer: a noindex, a JS-only page, or an accidental AI-search block that's costing you citations.

Input

domains (required, your sites) · auditPath (page to check, default /) · verifyToken (optional — put <meta name="geo-audit-verify" content="TOKEN"> on the page to mark ownership_verified) · timeoutSecs.

{ "domains": ["yourbrand.com", "docs.yourbrand.com"], "auditPath": "/" }

The 16 checks (per domain)

HTTPS/200 + redirect chain · AI-search crawlers not blocked (P0) · ineffective-block flag (gray-zone/non-compliant crawlers) · training opt-out tokens · sitemap present/valid/referenced · content in raw HTML (no-JS, P0) · noindex/nosnippet (P0) · AI opt-out meta (noai) · schema.org JSON-LD · canonical · title + meta description · Open Graph · semantic structure (single H1, <main>/<article>) · freshness dates · llms.txt presence + validity · llms-full.txt. → weighted score + READY / NEEDS_WORK / NOT_READY verdict + top_fixes.

Pricing (pay-per-event) & cost example

EventPriceWhen
domain-audited (primary)$0.04per domain fully audited
issue-found$0.01per fix-worthy issue flagged (capped at 8/domain)

A clean domain costs $0.04; a domain with 4 issues, $0.08; a badly-misconfigured one, at most $0.12. Measured platform compute is <$0.001/domain (<3% of revenue). Compare: brand-tracker SaaS runs $25–99/mo per domain; this is per-audit and pennies.

Integrate

Schedule it (weekly), then use Apify webhooks/API/MCP/Make/n8n to alert on any domain whose geo_ready_verdict drops or whose search_bots_blocked > 0.

Limitations

  • Audits one page per domain (the root or your auditPath) — not a full crawl.
  • robots.txt matching uses the standard longest-prefix rule; unusual wildcard patterns may under-report.
  • Intended for domains you own or are authorized to audit; it reads public files with a single polite request and honors robots.txt. Compliance tiering reflects publicly documented crawler behavior and can change.