ExampleThis is a report for the fictional store yourstore.example. Some checkpoints show fix code — the rest are blurred.
Get a report for your site
yourstore.example·Analysis: May 4, 2026
E-commerceWooCommerce
Confidence: 91%

Detected cart, product pages and payment module.

D
Your score:0/100points
FAgent ProtocolsFDiscoveryFStructured DataCSemanticsFSecurity

Your site doesn't talk to AI.

Several categories need urgent fixes. You're trailing the competition.

Checked 38 checkpoints · Skipped 12 checkpoints not applying to e-commerce pages
Checked
Skipped
View skipped (12)
WebMCP declarative
Easy

No WebMCP declarative (toolname/tooldescription on forms)

AI assistant prompt

Paste into Cursor, Claude Code or Windsurf

Fix: No declarative WebMCP (toolname/tooldescription on forms) on a WooCommerce e-commerce site. Check the form configuration in the WooCommerce admin panel and confirm the required fields are filled in. Verify the product template in the product management section and make sure the required WebMCP attributes are present. You may need to add code to template files or activate the right system hooks.
<!-- WebMCP declarative — add toolname + tooldescription to forms. No JS required. -->

<form action="/search" method="GET"
  toolname="search"
  tooldescription="Search products in the catalog by name, category or SKU.">
  <input type="text" name="q" required />
  <button type="submit">Search</button>
</form>

<form action="/contact" method="POST"
  toolname="contact"
  tooldescription="Send a message to customer support. Required fields: email, message.">
  <input type="email" name="email" required />
  <textarea name="message" required></textarea>
  <button type="submit">Send</button>
</form>

<form action="/login" method="POST"
  toolname="login"
  tooldescription="Authenticate the user. Required fields: email, password.">
  <input type="email" name="email" required />
  <input type="password" name="password" required />
  <button type="submit">Sign in</button>
</form>
WebMCP imperative
Medium

No WebMCP imperative (navigator.modelContext.registerTool)

Fix locked

Purchase a fix code package to reveal the fix and prompt

Buy fix code →
A2A Agent Card
Hard

No A2A Agent Card (/.well-known/agent.json)

Fix locked

Purchase a fix code package to reveal the fix and prompt

Buy fix code →
MCP Server Card
Medium

No MCP Server Card (3 locations checked)

Fix locked

Purchase a fix code package to reveal the fix and prompt

Buy fix code →
agents.json
Hard

No agents.json

Fix locked

Purchase a fix code package to reveal the fix and prompt

Buy fix code →
Content Comprehension Score
Medium

Available after unlocking the report by email

robots.txt exists
Easy

robots.txt is missing or unreachable

AI assistant prompt

Paste into Cursor, Claude Code or Windsurf

Fix: Missing or unreachable robots.txt on a WooCommerce site. Make sure robots.txt is created and visible in the root of your store. Log into the WooCommerce admin panel and add or edit robots.txt under SEO settings so it contains the right rules for crawlers. Verify the file is reachable at https://yourstore.example/robots.txt after publishing.
# AI agent access — replace or extend your robots.txt with the directives below.
# Each AI bot must be allowed explicitly to ensure crawlable content.

User-agent: *
Allow: /

User-agent: GPTBot
Allow: /

User-agent: ClaudeBot
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: ChatGPT-User
Allow: /

User-agent: Google-Extended
Allow: /

User-agent: CCBot
Allow: /

User-agent: Anthropic-AI
Allow: /

User-agent: Claude-Web
Allow: /

User-agent: Bytespider
Allow: /

User-agent: Cohere-AI
Allow: /

User-agent: Applebot-Extended
Allow: /

User-agent: Amazonbot
Allow: /

User-agent: Meta-ExternalAgent
Allow: /

User-agent: FacebookBot
Allow: /

User-agent: OmgiliBot
Allow: /

User-agent: Diffbot
Allow: /

# Place this file at https://yourstore.example/robots.txt
robots.txt allows AI bots
Easy

robots.txt unreachable — cannot verify

sitemap.xml exists
Easy

sitemap.xml is missing

Fix locked

Purchase a fix code package to reveal the fix and prompt

Buy fix code →
sitemap.xml is valid XML
Easy

sitemap.xml unreachable — cannot validate

llms.txt exists
Easy

llms.txt is missing — AI agents have no instructions

Fix locked

Purchase a fix code package to reveal the fix and prompt

Buy fix code →
llms.txt has enough content
Easy

llms.txt unreachable

Meta robots doesn't block AI
Easy

Meta robots blocks indexing — AI agents will skip the site

Fix locked

Purchase a fix code package to reveal the fix and prompt

Buy fix code →
WAF doesn't block AI bots

Site reachable for crawler (HTTP 200)

Link Headers RFC 8288
Easy

No Link Headers (RFC 8288) — api-catalog / service-desc absent

Fix locked

Purchase a fix code package to reveal the fix and prompt

Buy fix code →
Content-Signal directives
Easy

robots.txt unreachable

JSON-LD exists

JSON-LD present (1 block, 1 schema: WebSite)

Schema.org Product
Easy

No Schema.org Product — AI doesn't understand your products

Fix locked

Purchase a fix code package to reveal the fix and prompt

Buy fix code →
Product — required fields
Medium

No Product schema — cannot inspect fields

BreadcrumbList
Easy

No BreadcrumbList — AI cannot navigate the hierarchy

Fix locked

Purchase a fix code package to reveal the fix and prompt

Buy fix code →
Organization schema
Easy

No Organization schema — AI doesn't know who you are

AI assistant prompt

Paste into Cursor, Claude Code or Windsurf

Fix: No Organization schema in the structured data for the product page in WooCommerce. To fix this, update the product page template by adding the appropriate JSON-LD structured data. Edit the `product.tpl` file in the `templates` directory of your theme. Make sure it contains the organization data such as name, address, logo and other relevant info. You can use [schema.org/Organization](https://schema.org/Organization) as a guide. After the change, test the page using Google's Structured Data Testing Tool to confirm the schema is implemented correctly.
<!-- Add to <head> on every page (especially homepage). -->
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "yourstore.example",
  "url": "https://yourstore.example",
  "logo": "https://yourstore.example/logo.png",
  "description": "Replace with a short description of your business.",
  "contactPoint": {
    "@type": "ContactPoint",
    "email": "[email protected]",
    "contactType": "customer support",
    "availableLanguage": ["pl", "en"]
  },
  "sameAs": [
    "https://www.facebook.com/your-page",
    "https://www.linkedin.com/company/your-company"
  ]
}
</script>
FAQ schema
Medium

No FAQPage schema — AI cannot answer questions directly

Fix locked

Purchase a fix code package to reveal the fix and prompt

Buy fix code →
AggregateRating / Reviews
Medium

No AggregateRating — AI doesn't know product ratings

Fix locked

Purchase a fix code package to reveal the fix and prompt

Buy fix code →
SSR — content visible without JS

Content visible without JS (30,796 chars)

Heading hierarchy H1→H2→H3
Medium

No H1 tag — AI doesn't know what the page is about

AI assistant prompt

Paste into Cursor, Claude Code or Windsurf

Fix: No H1 tag on the product page — AI cannot understand what the page is about. Check the product template in WooCommerce — usually located under /templates/. Make sure the H1 contains the right product title (e.g. "products in a doghouse — gift for a dog lover") to improve heading hierarchy and SEO indexing.
<!DOCTYPE html>
<html lang="pl">
<head>
    <meta charset="UTF-8">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <title>Your product — gift for an enthusiast</title>
</head>
<body>
    <!-- Main heading for the page indicating the product title -->
    <h1>Your product</h1>
    
    <!-- Other content of the page can go here -->
    
</body>
</html>
Semantic HTML5 tags

Semantic HTML: header, nav, footer

ARIA landmarks
Easy

No ARIA landmarks or semantic HTML5 (main + nav)

Fix locked

Purchase a fix code package to reveal the fix and prompt

Buy fix code →
Alt text coverage ≥ 90%

All 6 images have alt (6 described, 0 decorative)

Language tag (html lang=)

Language declared: lang="pl"

Link text quality

Link text is informative

Answer Capsules (Q&A blocks)
Easy

No Q&A blocks (Answer Capsules)

Fix locked

Purchase a fix code package to reveal the fix and prompt

Buy fix code →
Meta description (50–160 chars)

Meta description correct (140 chars)

HTTPS + SSL expiry > 30 days

HTTPS + SSL valid (expires in 310 days)

HSTS header
Hard

No HSTS header — HTTP downgrade possible

AI assistant prompt

Paste into Cursor, Claude Code or Windsurf

Fix: No HSTS header — HTTP downgrade is possible. To enable HSTS on a WooCommerce-based site, log into the admin panel. Go to "Settings" > "Security". Enable HTTP Strict Transport Security (HSTS) and set the right parameters such as max-age. Make sure all assets on the page load over HTTPS. After saving, test the site to confirm the HSTS header is delivered.
server {
    listen 443 ssl; # Listen for HTTPS traffic
    server_name yourstore.example; # Your domain name

    ssl_certificate /path/to/fullchain.pem; # Path to your SSL certificate
    ssl_certificate_key /path/to/privkey.pem; # Path to your SSL private key

    # Enable HTTP Strict Transport Security (HSTS) with a max-age of 31536000 seconds (1 year)
    add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always; # Enforce HSTS

    # Other config...

    location / {
        # Serve your content here
    }
}

<VirtualHost *:443>
    ServerName yourstore.example  # Your domain name

    SSLEngine On  # Enable SSL

    SSLCertificateFile /path/to/fullchain.pem  # Path to your SSL certificate
    SSLCertificateKeyFile /path/to/privkey.pem  # Path to your SSL private key

    # Enable HTTP Strict Transport Security (HSTS) with a max-age of 31536000 seconds (1 year)
    Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains"  # Enforce HSTS

    # Other config...

    DocumentRoot /var/www/html  # Path to your website files
</VirtualHost>

# Note: After implementing HSTS, make sure to test your site functionality thoroughly.
# It's recommended to clear your browser cache or test in an incognito window after changes. 
Content-Security-Policy
Hard

No Content-Security-Policy — XSS risk

Fix locked

Purchase a fix code package to reveal the fix and prompt

Buy fix code →
X-Content-Type-Options
Hard

No X-Content-Type-Options: nosniff

Fix locked

Purchase a fix code package to reveal the fix and prompt

Buy fix code →
X-Frame-Options
Hard

No X-Frame-Options — clickjacking risk

Fix locked

Purchase a fix code package to reveal the fix and prompt

Buy fix code →
Referrer-Policy
Hard

No Referrer-Policy

Fix locked

Purchase a fix code package to reveal the fix and prompt

Buy fix code →

Skipped checkpoints (12)

Checkpoints not evaluated — not relevant to your industry or experimental.

Your turn

This is what a report looks like. See yours in 60 seconds.

The report above is for a fictional site. Enter your website URL — analysis, score, and specific fixes for your CMS. No signup.

Check your site
Result in 60 secondsNo signupFree report preview