Citebee AI Readiness

Citebee AI Readiness is a lightweight plugin for Generative Engine Optimization (GEO). It runs exactly three checks — the ones that decide whether AI search engines can understand and cite your content — and turns the result into a score plus an actionable fix list. Paste a URL, get an answer in seconds, no configuration required.

1. Does robots.txt block AI crawlers? (weight 40)

Fetches the target site’s robots.txt and evaluates each mainstream AI crawler individually — GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-SearchBot, PerplexityBot, Google-CloudVertexBot and CCBot — as Allowed, Blocked or Not specified. The parser handles the tricky cases correctly: consecutive User-agent lines that share one rule group, and wildcard User-agent: * combined with Disallow: /, which blocks the entire site.

2. Does an llms.txt exist, and is it well formed? (weight 30)

Looks for llms.txt in the site root. If it exists, the plugin validates the basic structure: a # title line, a > one-line site definition directly below it, and at least one [link text](URL) Markdown link — telling you exactly which parts are missing.

3. Does the homepage emit basic Schema markup? (weight 30)

Retrieves the front page HTML, extracts every <script type="application/ld+json"> block (fault tolerant, supports @graph and nested arrays), walks the parsed object to collect @type values, and reports the four GEO-critical types: Organization, WebSite, WebPage, and Article (matching BlogPosting and similar aliases). Every type detected is listed.

What you get

• A single 0-100 GEO readiness score (weighted 40 + 30 + 30).
• Green / yellow / red status per check, with concrete findings such as “GPTBot is blocked”, “no llms.txt found” or “no Organization Schema detected”.
• Actionable suggestions for every failing item: how to drop a Disallow rule, how to complete the three-part llms.txt, how to emit Organization / WebSite JSON-LD.
• Every run is stored in a custom table, so past reports can be reopened or deleted for side-by-side comparison.

Privacy and performance

• No data is sent to third parties. Audits use the WordPress HTTP API against the URL you enter and its /robots.txt and /llms.txt; results stay in your own database.
• All output is escaped with esc_html / esc_url / wp_kses_post, queries use $wpdb->prepare, the form is protected by a Nonce, and record deletion asks for confirmation.
• No dependencies, no external SDK, and the whole plugin folder stays under 30 KB.

Who should use it

Site owners and webmasters who want to know whether ChatGPT, Claude, Perplexity and other AI engines can actually reach and interpret their pages — and, more importantly, what to fix if they cannot.