{"id":350830,"date":"2026-08-27T19:05:17","date_gmt":"2026-08-27T19:05:17","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/ai-visibility-checker\/"},"modified":"2026-08-30T01:25:07","modified_gmt":"2026-08-30T01:25:07","slug":"webxdevelop-ai-search-readiness-audit","status":"publish","type":"plugin","link":"https:\/\/tuk.wordpress.org\/plugins\/webxdevelop-ai-search-readiness-audit\/","author":15133296,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"1.2.0","stable_tag":"1.2.0","tested":"7.0.4","requires":"6.0","requires_php":"7.4","requires_plugins":null,"header_name":"WebXDevelop AI Search Readiness Audit","header_author":"WebXDevelop","header_description":"Audits your WordPress website for AI search readiness, including structured data, content quality, technical SEO, and trust signals, and provides actionable recommendations.","assets_banners_color":"","last_updated":"2026-08-30 01:25:07","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"","header_author_uri":"https:\/\/webxdevelop.com\/","rating":0,"author_block_rating":0,"active_installs":0,"downloads":48,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"1.0.0":{"tag":"1.0.0","author":"sppdeve","date":"2026-08-27 19:05:06","revision":3669423},"1.2.0":{"tag":"1.2.0","author":"sppdeve","date":"2026-08-30 01:25:07","revision":3671960}},"upgrade_notice":{"1.0.0":"<p>Initial release.<\/p>"},"ratings":[],"assets_icons":[],"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.0","1.2.0"],"block_files":[],"assets_screenshots":[],"screenshots":{"1":"AI Visibility dashboard showing the overall readiness score and category breakdown.","2":"Audit results showing detected strengths and improvement recommendations.","3":"Client-ready HTML report export."}},"plugin_section":[],"plugin_tags":[2353,1117,186,1121,167235],"plugin_category":[55],"plugin_contributors":[277950],"plugin_business_model":[],"class_list":["post-350830","plugin","type-plugin","status-publish","hentry","plugin_tags-ai","plugin_tags-schema","plugin_tags-seo","plugin_tags-structured-data","plugin_tags-technical-seo","plugin_category-seo-and-marketing","plugin_contributors-sppdeve","plugin_committers-sppdeve"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/s.w.org\/plugins\/geopattern-icon\/webxdevelop-ai-search-readiness-audit.svg","icon_2x":false,"generated":true},"screenshots":[],"raw_content":"<!--section=description-->\n<p>WebXDevelop AI Search Readiness Audit audits your WordPress website for AI search readiness.<\/p>\n\n<p>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.<\/p>\n\n<p>Get an actionable readiness score with recommendations for improving website structure, content clarity, and discoverability.<\/p>\n\n<p>All audits run locally on your WordPress installation. No website data is sent to external services.<\/p>\n\n<h3>Features<\/h3>\n\n<ul>\n<li>AI search readiness score out of 100<\/li>\n<li>AI Answerability score out of 100 (content structure \/ extractability)<\/li>\n<li>AI Crawler Access analyzer (robots.txt, HTTP headers, robots meta tags)<\/li>\n<li>Structured data detection<\/li>\n<li>Content quality analysis<\/li>\n<li>Technical SEO checks<\/li>\n<li>Trust signal evaluation<\/li>\n<li>Actionable improvement recommendations<\/li>\n<li>Client-friendly HTML audit reports<\/li>\n<\/ul>\n\n<h3>AI Answerability<\/h3>\n\n<p>A separate 0-100 score that estimates how easily a search engine or AI system\ncan extract clear answers from the homepage's existing content. It runs locally\non the HTML the plugin already retrieves and uses only simple, explainable\nheuristics \u2014 no AI API, no external service, no NLP library.<\/p>\n\n<p>It looks at:<\/p>\n\n<ul>\n<li>whether a single H1 is present;<\/li>\n<li>how many descriptive subheadings there are;<\/li>\n<li>question-style headings (\"What is...\", \"How does...\", \"How much...\");<\/li>\n<li>short, direct paragraphs vs. very long ones;<\/li>\n<li>definition-style sentences (\"X is a ...\");<\/li>\n<li>lists and data tables;<\/li>\n<li>FAQ-style content;<\/li>\n<li>vague headings such as \"Our Approach\", \"Why Us\" or \"Learn More\".<\/li>\n<\/ul>\n\n<h4>How the score works<\/h4>\n\n<p>The score starts at 0. Points are added for structures that make answers easy\nto extract (up to 100 when all are present) and subtracted for problems, then\nthe result is capped to 0-100:<\/p>\n\n<ul>\n<li>Single H1: +15 (multiple H1: +8)<\/li>\n<li>Three or more descriptive subheadings: +15 (one or two: +8)<\/li>\n<li>Three or more question-based headings: +20 (one or two: +12)<\/li>\n<li>Content lists: +10 (a short list: +6)<\/li>\n<li>A data table: +8<\/li>\n<li>Two or more definition-style sentences: +12 (one: +6)<\/li>\n<li>FAQ-style content: +10<\/li>\n<li>Mostly short, direct paragraphs: +10 (some: +5)<\/li>\n<li>Penalty - several very long paragraphs: -15 (one or two: -8)<\/li>\n<li>Penalty - vague headings: -4 each, down to -16<\/li>\n<li>Penalty - no headings at all: -20<\/li>\n<li>Penalty - very thin content (under 200 words): -15<\/li>\n<\/ul>\n\n<p>This is a structural readability heuristic only. It does not check whether the\ncontent is factually correct and does not predict whether any AI will cite it.\nIt is shown as its own dashboard section and does NOT change the main AI Search\nReadiness Score.<\/p>\n\n<h3>AI Crawler Access Analyzer<\/h3>\n\n<p>This tool reports whether well-known AI and search crawlers are technically\npermitted to reach your site. It reads three sources locally:<\/p>\n\n<ul>\n<li>your site's robots.txt (a single request to home_url('\/robots.txt'));<\/li>\n<li>the HTTP response headers of your homepage (X-Robots-Tag);<\/li>\n<li>the robots meta tags in your homepage HTML (for example\n and ).<\/li>\n<\/ul>\n\n<p>robots.txt is parsed with a proper User-agent-aware parser. A crawler-specific\ngroup correctly overrides the wildcard \"*\" group, empty \"Disallow:\" is treated\nas \"allow all\", and Allow \/ Disallow precedence follows the length-of-match\nrule used by Google. If robots.txt cannot be retrieved or read, the result is\nreported as \"Unable to determine\" \u2014 never as \"Blocked\".<\/p>\n\n<p>The crawlers covered include OAI-SearchBot, GPTBot and ChatGPT-User (OpenAI),\nClaudeBot, Claude-SearchBot, Claude-User and the legacy anthropic-ai token\n(Anthropic), PerplexityBot and Perplexity-User (Perplexity), Google-Extended\n(Google), Applebot-Extended (Apple), Meta-ExternalAgent (Meta), Amazonbot\n(Amazon), CCBot (Common Crawl) and Bytespider (ByteDance). The list is\nmaintained in code and each entry explains what the crawler is for.<\/p>\n\n<h4>What crawler access means<\/h4>\n\n<p>\"Access\" describes whether a crawler is allowed to request your pages. That is\nall it describes.<\/p>\n\n<h4>What it does NOT mean<\/h4>\n\n<ul>\n<li>It does not mean your content will be indexed, ranked, included or cited by\nany search engine or AI system. Those are separate decisions made by each\nplatform.<\/li>\n<li>\"noindex\" is not a crawler block. A crawler can be fully allowed to fetch a\npage that also carries a \"noindex\" directive; the plugin reports crawler\naccess and indexability separately.<\/li>\n<li>Google-Extended and Applebot-Extended are control tokens, not crawlers.\nListing them in robots.txt opts your content out of a specific AI use; it has\nno effect on normal search crawling. They are only honoured when named\nexplicitly, so a wildcard \"Disallow: \/\" does not opt you out of them.<\/li>\n<\/ul>\n\n<h4>Why some site owners intentionally block crawlers<\/h4>\n\n<p>Blocking AI crawlers can be a deliberate choice \u2014 to keep content out of AI\ntraining datasets, to reduce crawl bandwidth, or for content-licensing reasons.\nThe plugin does not lower your score for blocking crawlers and does not\nrecommend allowing a crawler unless there is a clear reason to.<\/p>\n\n<h4>Scoring<\/h4>\n\n<p>The AI Crawler Access analyzer is informational only. It does not change the\n0-100 AI Search Readiness Score. Crawler access is a policy decision rather\nthan a readiness defect, and a permissive robots.txt is not automatically\n\"better\", so folding it into the score would be misleading.<\/p>\n\n<h3>What it checks<\/h3>\n\n<h4>Content Quality (30 points)<\/h4>\n\n<ul>\n<li>Homepage content length<\/li>\n<li>Heading structure<\/li>\n<li>Image alt text usage<\/li>\n<li>Internal linking<\/li>\n<li>Service page depth<\/li>\n<li>FAQ availability<\/li>\n<li>Blog freshness signals<\/li>\n<li>Author information<\/li>\n<\/ul>\n\n<h4>Trust Signals (25 points)<\/h4>\n\n<ul>\n<li>About page detection<\/li>\n<li>Contact information<\/li>\n<li>Phone, email, and address signals<\/li>\n<li>Author profiles<\/li>\n<li>Author expertise information<\/li>\n<\/ul>\n\n<h4>Schema (25 points)<\/h4>\n\n<ul>\n<li>JSON-LD structured data<\/li>\n<li>Microdata<\/li>\n<li>RDFa<\/li>\n<li>Organization schema<\/li>\n<li>LocalBusiness schema<\/li>\n<li>Person schema<\/li>\n<li>FAQPage schema<\/li>\n<li>Article schema<\/li>\n<\/ul>\n\n<h4>Technical SEO (20 points)<\/h4>\n\n<ul>\n<li>robots.txt availability<\/li>\n<li>XML sitemap detection<\/li>\n<li>noindex tags<\/li>\n<li>canonical URLs<\/li>\n<li>Indexability checks<\/li>\n<\/ul>\n\n<h3>Privacy<\/h3>\n\n<p>WebXDevelop AI Search Readiness Audit processes website information locally within your WordPress installation.<\/p>\n\n<p>The plugin does not collect personal data or send website content to external services.<\/p>\n\n<p>Audit results are stored locally in your WordPress database.<\/p>\n\n<!--section=installation-->\n<ol>\n<li>Upload the <code>webxdevelop-ai-search-readiness-audit<\/code> folder to the <code>\/wp-content\/plugins\/<\/code> directory.<\/li>\n<li>Activate the plugin through the 'Plugins' screen in WordPress.<\/li>\n<li>Navigate to Tools &gt; AI Visibility.<\/li>\n<li>Click \"Run Audit\" to analyze your website.<\/li>\n<\/ol>\n\n<!--section=faq-->\n<dl>\n<dt id=\"does%20this%20plugin%20improve%20ai%20rankings%3F\"><h3>Does this plugin improve AI rankings?<\/h3><\/dt>\n<dd><p>No. This plugin does not guarantee rankings or placement in AI search results. It analyzes website signals and provides recommendations that may help search engines and AI systems understand your content.<\/p><\/dd>\n<dt id=\"does%20this%20plugin%20use%20external%20apis%3F\"><h3>Does this plugin use external APIs?<\/h3><\/dt>\n<dd><p>No. The plugin performs audits locally inside your WordPress installation and does not send website data to external services.<\/p><\/dd>\n<dt id=\"does%20this%20plugin%20replace%20seo%20plugins%3F\"><h3>Does this plugin replace SEO plugins?<\/h3><\/dt>\n<dd><p>No. WebXDevelop AI Search Readiness Audit is designed as an auditing and recommendation tool. It can be used alongside existing SEO plugins.<\/p><\/dd>\n\n<\/dl>\n\n<!--section=changelog-->\n<h4>1.2.0<\/h4>\n\n<ul>\n<li>Added AI Answerability: a separate 0-100 score estimating how easily a search\nengine or AI system can extract clear answers from the homepage, based on\nheadings, question phrasing, paragraph length, lists, tables and definitions.<\/li>\n<li>Fully local heuristic \u2014 no AI API, external service or new dependency.<\/li>\n<li>Shown as its own dashboard section; does not change the main score.<\/li>\n<li>Added PHPUnit unit tests for the answerability heuristics.<\/li>\n<\/ul>\n\n<h4>1.1.0<\/h4>\n\n<ul>\n<li>Added the AI Crawler Access analyzer: robots.txt, X-Robots-Tag headers and\nrobots meta tags are checked to report whether known AI and search crawlers\nare allowed, blocked, or \"unable to determine\".<\/li>\n<li>Added a User-agent-aware robots.txt parser (crawler-specific groups override\nthe wildcard group; correct Allow \/ Disallow precedence).<\/li>\n<li>The audit now makes a single robots.txt request, shared by the technical and\ncrawler checks.<\/li>\n<li>The AI Crawler Access analyzer is informational and does not change the\n0-100 score.<\/li>\n<li>Added PHPUnit unit tests for the crawler parser and decision logic.<\/li>\n<\/ul>\n\n<h4>1.0.0<\/h4>\n\n<ul>\n<li>Initial release.<\/li>\n<li>Added AI search readiness scoring.<\/li>\n<li>Added schema, content, technical SEO, and trust signal audits.<\/li>\n<li>Added HTML report export.<\/li>\n<\/ul>","raw_excerpt":"Audit your website&#039;s AI search readiness with structured data, SEO, content, and trust signal checks.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/tuk.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/350830","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/tuk.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/tuk.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/tuk.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=350830"}],"author":[{"embeddable":true,"href":"https:\/\/tuk.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/sppdeve"}],"wp:attachment":[{"href":"https:\/\/tuk.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=350830"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/tuk.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=350830"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/tuk.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=350830"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/tuk.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=350830"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/tuk.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=350830"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/tuk.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=350830"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}