{"id":387265,"date":"2026-10-30T21:50:32","date_gmt":"2026-10-30T21:50:32","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/siteverdict-site-health-consent-accessibility-checker\/"},"modified":"2026-10-30T21:50:23","modified_gmt":"2026-10-30T21:50:23","slug":"siteverdict","status":"publish","type":"plugin","link":"https:\/\/wordpress.org\/plugins\/siteverdict\/","author":23586326,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"1.0.0","stable_tag":"1.0.0","tested":"7.1.4","requires":"6.2","requires_php":"7.4","requires_plugins":null,"header_name":"SiteVerdict \u2013 Site Health, Consent & Accessibility Checker","header_author":"BharatFare Travel and Technologies Ltd","header_description":"Scan your own pages for cookie-consent and tracking issues, speed problems, quick accessibility (WCAG 2.2 AA) checks, SEO basics and AI-search readiness. Plain-English fixes for WordPress, plus an llms.txt generator. Local checks work with no external calls.","assets_banners_color":"","last_updated":"2026-10-30 21:50:23","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"https:\/\/siteverdict.webrevenuescan.com\/wordpress","header_author_uri":"https:\/\/siteverdict.webrevenuescan.com","rating":0,"author_block_rating":0,"active_installs":0,"downloads":46,"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":"siteverdict","date":"2026-10-30 21:50:23","revision":3776073}},"upgrade_notice":{"1.0.0":"<p>First release.<\/p>"},"ratings":[],"assets_icons":[],"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.0"],"block_files":[],"assets_screenshots":[],"screenshots":{"1":"Report with overall grade, scores by area and plain-English fixes.","2":"Cookie consent and tracking findings with WordPress-specific fix steps.","3":"AI crawler table showing which AI search and training bots are allowed.","4":"llms.txt generator.","5":"Settings &amp; privacy tab with the opt-in for cloud checks.","6":"Dashboard widget with grade and top issues."}},"plugin_section":[262246],"plugin_tags":[1953,16626,131785,186,151481],"plugin_category":[34,55],"plugin_contributors":[289853],"plugin_business_model":[],"class_list":["post-387265","plugin","type-plugin","status-publish","hentry","plugin_section-dashboard-widgets","plugin_tags-accessibility","plugin_tags-cookie-consent","plugin_tags-gdpr","plugin_tags-seo","plugin_tags-site-health","plugin_category-accessibility","plugin_category-seo-and-marketing","plugin_contributors-siteverdict","plugin_committers-siteverdict"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/s.w.org\/plugins\/geopattern-icon\/siteverdict.svg","icon_2x":false,"generated":true},"screenshots":[],"raw_content":"<!--section=description-->\n<p>SiteVerdict checks your own WordPress site the way a visitor, a search engine and an AI assistant see it, then tells you in plain English what to fix and where to click in WordPress.<\/p>\n\n<p><strong>Runs on your server. No account needed.<\/strong> All the checks below work locally: the plugin loads your own pages from your own server. Nothing is sent to any outside service unless you choose to turn on the optional cloud checks.<\/p>\n\n<h4>What makes it different<\/h4>\n\n<p>SiteVerdict is a site-health checker, not an llms.txt plugin. The llms.txt builder is one small optional tool inside it. The core of the plugin is the combination of cookie-consent and tracking-tag detection, a WCAG 2.2 AA quick check, speed, SEO and AI-crawler checks, each explained with the exact WordPress screen or plugin setting that fixes it. It runs entirely on your own server with no account, and the checks are designed for WordPress specifically (Media Library alt text, Settings &gt; Reading, consent-plugin detection, robots.txt handled by WordPress).<\/p>\n\n<h4>What it checks<\/h4>\n\n<ul>\n<li><strong>Cookie consent &amp; tracking<\/strong> \u2013 finds Google Analytics, Google Tag Manager, Meta Pixel, Hotjar, Microsoft Clarity, TikTok, LinkedIn and other tags in your pages; detects common consent plugins (Complianz, CookieYes, Cookiebot, Real Cookie Banner, Borlabs, GDPR Cookie Compliance, iubenda and more); warns when tags load without a banner or may fire before consent; checks for Google Consent Mode v2 signals.<\/li>\n<li><strong>Speed<\/strong> \u2013 server response time, page caching, compression, render-blocking scripts and styles, very large HTML, images without width\/height (layout shift) and missing lazy loading.<\/li>\n<li><strong>Accessibility (WCAG 2.2 AA quick check)<\/strong> \u2013 page language, title, image alt text (in pages and in your Media Library), form labels, links and buttons without names, heading structure, disabled zoom, iframe titles, positive tabindex, autoplaying sound, duplicate IDs.<\/li>\n<li><strong>SEO basics<\/strong> \u2013 title and meta description, canonical, noindex, \"Discourage search engines\" setting, permalinks, XML sitemap, robots.txt, Open Graph tags, multiple H1s.<\/li>\n<li><strong>AI-search readiness<\/strong> \u2013 shows which AI crawlers (OAI-SearchBot, ChatGPT-User, GPTBot, ClaudeBot, Claude-SearchBot, PerplexityBot, Google-Extended and more) your robots.txt allows or blocks, separating AI <em>search<\/em> bots from <em>training<\/em> bots; checks for structured data, llms.txt and enough server-rendered text.<\/li>\n<li><strong>Site health<\/strong> \u2013 HTTPS and common security headers.<\/li>\n<\/ul>\n\n<h4>What you get<\/h4>\n\n<ul>\n<li>A score and grade (A\u2013F) for each area, plus an overall grade.<\/li>\n<li>Every issue explained in plain English with <strong>\"How to fix in WordPress\"<\/strong> steps that point to the exact screen (for example Settings &gt; Reading, Media &gt; Library) and common plugins.<\/li>\n<li>A <strong>dashboard widget<\/strong> with your grade and top three issues.<\/li>\n<li>A result in <strong>Tools &gt; Site Health<\/strong>.<\/li>\n<li>An <strong>llms.txt generator<\/strong>: builds a draft from your published pages, posts (and WooCommerce categories, if present), lets you edit it, and serves it at \/llms.txt without writing files, or lets you download it.<\/li>\n<\/ul>\n\n<h4>Optional cloud checks (opt-in)<\/h4>\n\n<p>Some things can only be tested in a real browser \u2013 for example which cookies appear before and after a visitor clicks \"Accept\", Core Web Vitals, or a full accessibility test of the rendered page. If you want those, you can opt in on the Settings tab and add a SiteVerdict API key. See \"External services\" below for exactly what is sent. Cloud checks are off by default and the plugin is fully useful without them.<\/p>\n\n<h4>SiteVerdict Pro add-on (optional, paid)<\/h4>\n\n<p>A separate add-on plugin, not required for anything on this page, adds scheduled scans, email reports, whole-site crawls, score history and white-label PDF reports for agencies. All features of this free plugin stay free and unlocked.<\/p>\n\n<h4>Important<\/h4>\n\n<p>Automated checks find common problems but cannot prove full compliance with WCAG, PECR, GDPR or any other law. SiteVerdict is not legal advice.<\/p>\n\n<h3>External services<\/h3>\n\n<p>This plugin can connect to the <strong>SiteVerdict API<\/strong> (https:\/\/api.webrevenuescan.com), operated by BharatFare Travel and Technologies Ltd (UK). It is used only for the optional cloud checks.<\/p>\n\n<ul>\n<li><strong>When:<\/strong> only when an administrator has ticked \"I agree to send my home page address to the SiteVerdict API\", saved an API key, and then runs a scan. The plugin starts the cloud checks (POST \/v1\/jobs\/{check}) and, while an administrator views the report, asks for their results (GET \/v1\/jobs\/{job_id}). It is never contacted otherwise \u2013 not on activation, not by visitors, and not in the background (unless the separate Pro add-on is installed and scheduled scans are turned on).<\/li>\n<li><strong>What is sent:<\/strong> the public address of your home page, the names of the checks you selected, and your API key. No WordPress user data, visitor data, passwords or database content are sent. The service then loads that public page like a normal visitor.<\/li>\n<li><strong>Terms of service:<\/strong> https:\/\/siteverdict.webrevenuescan.com\/terms<\/li>\n<li><strong>Privacy policy:<\/strong> https:\/\/siteverdict.webrevenuescan.com\/privacy<\/li>\n<\/ul>\n\n<p><strong>Tag signatures are not connections.<\/strong> The plugin contains lists of script addresses and code fragments (for example googletagmanager.com, connect.facebook.net, hotjar, clarity) that it looks for <em>inside your own pages' HTML<\/em> to detect which tracking tags your site uses. These strings are detection signatures only: the plugin never requests, loads or contacts Google, Meta, Hotjar, Microsoft or any other tag provider.<\/p>\n\n<p>All local checks make HTTP requests only to your own site (loopback requests to your home page, the pages you list, \/robots.txt and \/llms.txt).<\/p>\n\n<!--section=installation-->\n<ol>\n<li>In WordPress go to Plugins &gt; Add New, search for \"SiteVerdict\", then click Install Now and Activate. (Or upload the plugin zip under Plugins &gt; Add New &gt; Upload Plugin.)<\/li>\n<li>Go to Tools &gt; SiteVerdict and click <strong>Run scan now<\/strong>.<\/li>\n<li>Open each area, read the issues and follow the \"How to fix in WordPress\" steps.<\/li>\n<li>Optional: add more pages to scan under the <strong>Settings &amp; privacy<\/strong> tab.<\/li>\n<li>Optional: create an llms.txt under the <strong>llms.txt<\/strong> tab.<\/li>\n<\/ol>\n\n<!--section=faq-->\n<dl>\n<dt id=\"does%20the%20plugin%20send%20my%20data%20anywhere%3F\"><h3>Does the plugin send my data anywhere?<\/h3><\/dt>\n<dd><p>No, not by default. Local checks only request pages from your own site. The optional cloud checks send only your home page address (plus your API key and chosen checks) to the SiteVerdict API, and only after you opt in. See \"External services\".<\/p><\/dd>\n<dt id=\"will%20it%20slow%20down%20my%20site%3F\"><h3>Will it slow down my site?<\/h3><\/dt>\n<dd><p>No. Nothing runs for visitors. Scans only run when an administrator clicks the button. The only front-end code is a tiny check that serves \/llms.txt if you enabled it.<\/p><\/dd>\n<dt id=\"does%20it%20make%20my%20site%20legally%20compliant%3F\"><h3>Does it make my site legally compliant?<\/h3><\/dt>\n<dd><p>No tool can do that on its own. SiteVerdict finds common technical issues (for example trackers without a cookie banner or images without alt text) and explains how to fix them. It is not legal advice; ask a qualified adviser if you are unsure.<\/p><\/dd>\n<dt id=\"is%20this%20a%20full%20wcag%20audit%3F\"><h3>Is this a full WCAG audit?<\/h3><\/dt>\n<dd><p>No. It is a quick, automated check of common WCAG 2.2 AA failures that can be detected from the HTML. Things like colour contrast, keyboard traps and meaningful alt text need a rendered-page test (available as a cloud check) and a human review.<\/p><\/dd>\n<dt id=\"why%20does%20it%20say%20my%20trackers%20may%20fire%20before%20consent%20when%20i%20have%20a%20cookie%20banner%3F\"><h3>Why does it say my trackers may fire before consent when I have a cookie banner?<\/h3><\/dt>\n<dd><p>The local check reads the HTML your server sends. If a tracking script is a normal script tag and is not marked as blocked by your consent tool, it may run before the visitor chooses. Some consent tools block scripts in a way that cannot be seen in the HTML; the optional cloud check tests in a real browser to confirm.<\/p><\/dd>\n<dt id=\"should%20i%20block%20ai%20crawlers%3F\"><h3>Should I block AI crawlers?<\/h3><\/dt>\n<dd><p>That is a business choice. SiteVerdict separates AI <em>search<\/em> bots (which fetch pages to answer questions and can send you visitors) from AI <em>training<\/em> bots. Many sites allow search bots and block training bots.<\/p><\/dd>\n<dt id=\"what%20is%20llms.txt%3F%20do%20i%20need%20it%3F\"><h3>What is llms.txt? Do I need it?<\/h3><\/dt>\n<dd><p>llms.txt is an optional, emerging convention: a short Markdown file listing your most useful pages for AI tools. It does no harm, takes a minute, and not every AI provider uses it yet.<\/p><\/dd>\n<dt id=\"the%20scan%20says%20it%20could%20not%20load%20my%20page.\"><h3>The scan says it could not load my page.<\/h3><\/dt>\n<dd><p>Your server could not make a request to itself (a \"loopback request\"). Check Tools &gt; Site Health for loopback errors, or ask your host. Security plugins and HTTP authentication on staging sites are common causes.<\/p><\/dd>\n<dt id=\"does%20it%20work%20on%20multisite%3F\"><h3>Does it work on multisite?<\/h3><\/dt>\n<dd><p>Yes, per site. Each site administrator runs their own scan. Uninstalling removes data from every site.<\/p><\/dd>\n<dt id=\"what%20data%20does%20the%20plugin%20store%3F\"><h3>What data does the plugin store?<\/h3><\/dt>\n<dd><p>Your settings, the last report, and your llms.txt (all in the WordPress options table). Deleting the plugin from the Plugins screen removes all of it.<\/p><\/dd>\n\n<\/dl>\n\n<!--section=changelog-->\n<h4>1.0.0<\/h4>\n\n<ul>\n<li>First release: local checks for cookie consent and tracking, speed, accessibility (WCAG 2.2 AA quick check), SEO basics, AI-search readiness and security headers.<\/li>\n<li>Plain-English WordPress fixes for every issue.<\/li>\n<li>Dashboard widget and Site Health integration.<\/li>\n<li>llms.txt generator served at \/llms.txt.<\/li>\n<li>Optional, opt-in SiteVerdict API cloud checks.<\/li>\n<\/ul>","raw_excerpt":"Check cookie consent, speed, accessibility (WCAG 2.2 AA), SEO and AI-search readiness, with plain-English WordPress fixes and an llms.txt generator.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/387265","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=387265"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/siteverdict"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=387265"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=387265"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=387265"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=387265"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=387265"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=387265"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}