WebXDevelop AI Search Readiness Audit

Description

WebXDevelop AI Search Readiness Audit audits your WordPress website for AI search readiness.

The plugin analyzes technical SEO, structured data, content quality, and trust signals that may help search engines and AI systems better understand your website content.

Get an actionable readiness score with recommendations for improving website structure, content clarity, and discoverability.

All audits run locally on your WordPress installation. No website data is sent to external services.

Features

• AI search readiness score out of 100
• AI Answerability score out of 100 (content structure / extractability)
• AI Crawler Access analyzer (robots.txt, HTTP headers, robots meta tags)
• Structured data detection
• Content quality analysis
• Technical SEO checks
• Trust signal evaluation
• Actionable improvement recommendations
• Client-friendly HTML audit reports

AI Answerability

A separate 0-100 score that estimates how easily a search engine or AI system
can extract clear answers from the homepage’s existing content. It runs locally
on the HTML the plugin already retrieves and uses only simple, explainable
heuristics — no AI API, no external service, no NLP library.

It looks at:

• whether a single H1 is present;
• how many descriptive subheadings there are;
• question-style headings (“What is…”, “How does…”, “How much…”);
• short, direct paragraphs vs. very long ones;
• definition-style sentences (“X is a …”);
• lists and data tables;
• FAQ-style content;
• vague headings such as “Our Approach”, “Why Us” or “Learn More”.

How the score works

The score starts at 0. Points are added for structures that make answers easy
to extract (up to 100 when all are present) and subtracted for problems, then
the result is capped to 0-100:

• Single H1: +15 (multiple H1: +8)
• Three or more descriptive subheadings: +15 (one or two: +8)
• Three or more question-based headings: +20 (one or two: +12)
• Content lists: +10 (a short list: +6)
• A data table: +8
• Two or more definition-style sentences: +12 (one: +6)
• FAQ-style content: +10
• Mostly short, direct paragraphs: +10 (some: +5)
• Penalty – several very long paragraphs: -15 (one or two: -8)
• Penalty – vague headings: -4 each, down to -16
• Penalty – no headings at all: -20
• Penalty – very thin content (under 200 words): -15

This is a structural readability heuristic only. It does not check whether the
content is factually correct and does not predict whether any AI will cite it.
It is shown as its own dashboard section and does NOT change the main AI Search
Readiness Score.

AI Crawler Access Analyzer

This tool reports whether well-known AI and search crawlers are technically
permitted to reach your site. It reads three sources locally:

• your site’s robots.txt (a single request to home_url(‘/robots.txt’));
• the HTTP response headers of your homepage (X-Robots-Tag);
• the robots meta tags in your homepage HTML (for example
  and ).

robots.txt is parsed with a proper User-agent-aware parser. A crawler-specific
group correctly overrides the wildcard “*” group, empty “Disallow:” is treated
as “allow all”, and Allow / Disallow precedence follows the length-of-match
rule used by Google. If robots.txt cannot be retrieved or read, the result is
reported as “Unable to determine” — never as “Blocked”.

The crawlers covered include OAI-SearchBot, GPTBot and ChatGPT-User (OpenAI),
ClaudeBot, Claude-SearchBot, Claude-User and the legacy anthropic-ai token
(Anthropic), PerplexityBot and Perplexity-User (Perplexity), Google-Extended
(Google), Applebot-Extended (Apple), Meta-ExternalAgent (Meta), Amazonbot
(Amazon), CCBot (Common Crawl) and Bytespider (ByteDance). The list is
maintained in code and each entry explains what the crawler is for.

What crawler access means

“Access” describes whether a crawler is allowed to request your pages. That is
all it describes.

What it does NOT mean

• It does not mean your content will be indexed, ranked, included or cited by
  any search engine or AI system. Those are separate decisions made by each
  platform.
• “noindex” is not a crawler block. A crawler can be fully allowed to fetch a
  page that also carries a “noindex” directive; the plugin reports crawler
  access and indexability separately.
• Google-Extended and Applebot-Extended are control tokens, not crawlers.
  Listing them in robots.txt opts your content out of a specific AI use; it has
  no effect on normal search crawling. They are only honoured when named
  explicitly, so a wildcard “Disallow: /” does not opt you out of them.

Why some site owners intentionally block crawlers

Blocking AI crawlers can be a deliberate choice — to keep content out of AI
training datasets, to reduce crawl bandwidth, or for content-licensing reasons.
The plugin does not lower your score for blocking crawlers and does not
recommend allowing a crawler unless there is a clear reason to.

Scoring

The AI Crawler Access analyzer is informational only. It does not change the
0-100 AI Search Readiness Score. Crawler access is a policy decision rather
than a readiness defect, and a permissive robots.txt is not automatically
“better”, so folding it into the score would be misleading.

What it checks

Content Quality (30 points)

• Homepage content length
• Heading structure
• Image alt text usage
• Internal linking
• Service page depth
• FAQ availability
• Blog freshness signals
• Author information

Trust Signals (25 points)

• About page detection
• Contact information
• Phone, email, and address signals
• Author profiles
• Author expertise information

Schema (25 points)

• JSON-LD structured data
• Microdata
• RDFa
• Organization schema
• LocalBusiness schema
• Person schema
• FAQPage schema
• Article schema

Technical SEO (20 points)

• robots.txt availability
• XML sitemap detection
• noindex tags
• canonical URLs
• Indexability checks

Privacy

WebXDevelop AI Search Readiness Audit processes website information locally within your WordPress installation.

The plugin does not collect personal data or send website content to external services.

Audit results are stored locally in your WordPress database.