Informe de auditoría AX

https://sunsama.com

August 12, 20261837ms response

60AX score / 100

Needs work

Readiness diagnosis

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

1 crítico

5 warnings

22 aprobado

Current constraintDiscovery31%

Five readiness layers

Readiness orbit

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

Evidence profile

28 checks recorded

Passed vs. material gaps

Critical

Warnings

Passed

Discovery

Current constraint

4 / 13 weighted points

31%

Identity

17.1 / 22 weighted points

78%

Access

25.7 / 31 weighted points

83%

Agent Integration

8.0 / 24 weighted points

33%

User Experience

5.3 / 10 weighted points

53%

Start here

Top Priorities

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

CAPTCHA or bot protection detected

Rastreabilidad

Review

JSON-LD found but no business schema (found: SoftwareApplication)

Datos estructurados

Review

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

Actionability

Review

Missing semantic HTML: <main>, <nav>, <header>, <footer>, <h1>

Calidad del contenido

Review

Only 34% of images have alt text (63/188)

Calidad del contenido

Review

Explore the audit

Findings and fixes

Rastreabilidad

Performance

Seguridad y confianza

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 1 JSON-LD structured data block

JSON-LD found but no business schema (found: SoftwareApplication)
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

No MCP server or AI agent endpoint detected — agents cannot interact with your business
Set up a Model Context Protocol (MCP) server so AI agents can interact with your business directly. This allows agents to book appointments, check availability, and more.

With Dashform, you can add MCP support to your website in minutes — no coding required.

Alternatively, create /.well-known/ai-plugin.json for ChatGPT plugin compatibility.

sitemap.xml found and valid

RSS/Atom feed detected

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

Contact/lead form with an email field is present

CTA buttons have descriptive labels

Missing semantic HTML: <main>, <nav>, <header>, <footer>, <h1>
Add missing semantic HTML elements: <main>, <nav>, <header>, <footer>, <h1>

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

Sufficient text content available for AI extraction

5 social media links found

No Schema.org sameAs links — AI agents cannot verify your identity across platforms
Add sameAs to your Schema.org JSON-LD:
"sameAs": [
  "https://twitter.com/yourbrand",
  "https://linkedin.com/company/yourbrand"
]

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

Contact information detected (phone, email)

Response time is 1.8s — acceptable, could be faster

Lean HTML payload (104KB)

Response is compressed (br)

Caching headers present (Cache-Control/ETag/Last-Modified)

Entry URL redirects before serving — adds latency for agents

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"

No current year found — the site may look stale to agents

HTTPS enabled

SSL certificate valid

Privacy policy link found

Terms of service link found

sunsama.com

https://sunsama.com

Readiness orbit

Top Priorities

Findings and fixes

All Findings

Turn audit findings into an agent-ready funnel.

Related AX Scores