AX-Audit-Bericht

https://mindsdb.com

August 12, 20261316ms response

66AX score / 100

Needs work

Readiness diagnosis

This site needs work before agents can use it reliably. Address the priority findings to improve readiness.

1 kritisch

6 warnings

25 bestanden

Current constraintDiscovery36%

Five readiness layers

Readiness orbit

The shape reveals where an agent journey breaks down, from finding the site to completing useful work.

Evidence profile

32 checks recorded

Passed vs. material gaps

Critical

Warnings

Passed

Discovery

Current constraint

4.6 / 13 weighted points

36%

Identity

15.5 / 22 weighted points

70%

Access

25.1 / 31 weighted points

81%

Agent Integration

12.9 / 24 weighted points

54%

User Experience

8 / 10 weighted points

80%

Start here

Top Priorities

Select the highest-impact Findings to include in your Fix Plan.

CAPTCHA or bot protection detected

Crawlbarkeit

Review

No Schema.org potentialAction — agents can't tell what they can do on your site

Actionability

Review

Missing semantic HTML: multiple <h1> tags (use only one)

Inhaltsqualität

Review

Only 49% of images have alt text (32/65)

Inhaltsqualität

Review

Explore the audit

Findings and fixes

Crawlbarkeit

Performance

Sicherheit & Vertrauen

All Findings

robots.txt allows all major AI crawlers

Page returns HTTP 200

Page content available without JavaScript

CAPTCHA or bot protection detected
Consider allowing AI crawlers to bypass bot protection. Options:
1. Whitelist known AI crawler IPs (OpenAI, Anthropic, Google publish their ranges)
2. Use robots.txt to signal crawler access
3. Configure your WAF/CDN to exempt verified bot traffic

Found 3 JSON-LD structured data blocks

Business schema found: Organization

Schema has 7 fields — consider adding more for better AI comprehension

OpenGraph tags complete (title, description, image)

Meta tags complete (title, description, canonical)

llms.txt found but format is incorrect

llms-full.txt also found (two-file mode)

MCP configuration found at /.well-known/mcp.json, /mcp.json, /.mcp.json, /.well-known/mcp

AI agent plugin manifest found at /.well-known/ai-plugin.json, /.well-known/ai-agent.json

API specification found at /openapi.json

Sitemap found but may not be valid XML

No Schema.org potentialAction — agents can't tell what they can do on your site
Add a potentialAction to your Schema.org JSON-LD so agents can act, e.g.:
"potentialAction": {
  "@type": "ReserveAction",
  "target": "https://yoursite.com/book"
}

No scheduling link found — agents can't book time with you directly

Priced offers found, but no clear checkout path for agents

A form is present but has no obvious email field

Live chat / conversational widget detected

CTA buttons have descriptive labels

Missing semantic HTML: multiple <h1> tags (use only one)
Add missing semantic HTML elements: multiple <h1> tags (use only one)

Only 49% of images have alt text (32/65)
Add descriptive alt attributes to all <img> tags. Example: <img alt="Description of image content" src="..." />

Sufficient text content available for AI extraction

FAQ schema detected

3 social media links found

Schema.org sameAs links found (cross-platform identity)

No Google Maps or Business Profile presence detected — AI agents may not verify your location
Claim your Google Business Profile at https://business.google.com and embed a Google Maps link or iframe on your page. AI agents use Google Maps data to verify business locations.

Limited contact information — add phone, email, and address

Fast response time (1316ms)

Lean HTML payload (190KB)

Response is compressed (br)

No caching headers — repeat agent fetches can't be revalidated

Entry URL redirects before serving — adds latency for agents

No author/publisher in schema — weak authorship signal
Add author and publisher to your Schema.org JSON-LD to establish credibility:
"publisher": { "@type": "Organization", "name": "Your Brand" }

No review/rating schema — agents can't surface your reputation

Partial security headers (CSP only)

No dateModified/datePublished in schema — agents can't judge freshness
Add dateModified/datePublished to your Schema.org JSON-LD so agents can judge freshness:
"dateModified": "2026-01-15"

Footer/copyright year is current

HTTPS enabled

SSL certificate valid

Privacy policy link found

Terms of service link found

mindsdb.com

https://mindsdb.com

Readiness orbit

Top Priorities

Findings and fixes

All Findings

Turn audit findings into an agent-ready funnel.

Related AX Scores