Informe de auditoría AX

https://pantainsure.com

August 12, 20261024ms 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.

0 crítico

4 warnings

25 aprobado

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

29 checks recorded

Passed vs. material gaps

Critical

Warnings

Passed

Discovery

Current constraint

4.6 / 13 weighted points

36%

Identity

17.1 / 22 weighted points

78%

Access

26.4 / 31 weighted points

85%

Agent Integration

8.9 / 24 weighted points

37%

User Experience

8.7 / 10 weighted points

87%

Start here

Top Priorities

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

JSON-LD found but no business schema (found: InsuranceAgency, WebSite, WebPage)

Datos estructurados

Review

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

Actionability

Review

Explore the audit

Findings and fixes

Datos estructurados

Authoritativeness

All Findings

robots.txt allows all major AI crawlers

Page returns HTTP 200

Page content available without JavaScript

Cookie consent wall detected — may block AI crawlers

No CAPTCHA or bot protection detected

Found 3 JSON-LD structured data blocks

JSON-LD found but no business schema (found: InsuranceAgency, WebSite, WebPage)
Add a business-specific schema type (LocalBusiness, Organization, Product, Service) to help AI agents understand what your business offers.

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 /mcp.json, /.mcp.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

Direct contact link found, but no on-page form for agents

CTA buttons have descriptive labels

HTML semantic structure is well-formed

89% of images have alt text (8/9)

Sufficient text content available for AI extraction

No social media links found

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

Location or rating data found in schema — consider linking to Google Business Profile

Contact information detected (phone, email, address)

Fast response time (1024ms)

Lean HTML payload (77KB)

Response is compressed (br)

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

Author/publisher identity declared in schema

Review/rating schema found — agents can cite social proof

No HSTS or CSP headers detected
Add Strict-Transport-Security and Content-Security-Policy headers — they signal a well-maintained, trustworthy origin.

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

No terms of service link detected

pantainsure.com