Informe de auditoría AX

https://pipekit.io

August 12, 2026458ms response

63AX 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

8 warnings

22 aprobado

Current constraintDiscovery12%

Five readiness layers

Readiness orbit

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

Evidence profile

30 checks recorded

Passed vs. material gaps

Critical

Warnings

Passed

Discovery

Current constraint

1.6 / 13 weighted points

12%

Identity

11.7 / 22 weighted points

53%

Access

31 / 31 weighted points

100%

Agent Integration

13.6 / 24 weighted points

57%

User Experience

4.7 / 10 weighted points

47%

Start here

Top Priorities

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

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

Datos estructurados

Review

Missing OpenGraph tags: og:image

Datos estructurados

Review

No form or direct contact path — agents have no way to convert here

Actionability

Review

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

Calidad del contenido

Review

Only 25% of images have alt text (7/28)

Calidad del contenido

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

No CAPTCHA or bot protection detected

Found 1 JSON-LD structured data block

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

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

Missing OpenGraph tags: og:image
<meta property="og:image" content="..." />

Missing meta tags: canonical link

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

API specification found at /openapi.json

sitemap.xml found and valid

Schema.org potentialAction defined — agents know what actions are available

Booking/scheduling integration detected

No form or direct contact path — agents have no way to convert here
Add an agent-usable conversion path — a contact form, a booking widget, or a Dashform AI funnel agents can complete on the visitor's behalf.

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

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

Sufficient text content available for AI extraction

Heading levels skip (e.g., h1 directly to h3)

2 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"
]

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 (458ms)

Lean HTML payload (31KB)

Response is compressed (gzip)

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

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

Security headers present (HSTS + Content-Security-Policy)

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

pipekit.io

https://pipekit.io

Readiness orbit

Top Priorities

Findings and fixes

All Findings

Turn audit findings into an agent-ready funnel.

Related AX Scores