Informe de auditoría AX

https://tango.us

August 12, 20262991ms response

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

5 warnings

26 aprobado

Current constraintAgent Integration27%

Five readiness layers

Readiness orbit

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

Evidence profile

31 checks recorded

Passed vs. material gaps

Critical

Warnings

Passed

Discovery

7.8 / 13 weighted points

60%

Identity

18.6 / 22 weighted points

84%

Access

29 / 31 weighted points

94%

Agent Integration

Current constraint

6.6 / 24 weighted points

27%

User Experience

6 / 10 weighted points

60%

Start here

Top Priorities

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

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

Datos estructurados

Review

No llms.txt file found — AI agents cannot discover your services

Interacción con el agente

Review

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

Actionability

Review

Missing semantic HTML: <footer>

Calidad del contenido

Review

Only 76% of images have alt text (53/70)

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 3 JSON-LD structured data blocks

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

No llms.txt file found — AI agents cannot discover your services
Create a /llms.txt file at your site root:

# Your Business Name

> Brief description of your business.

## Services
- [Service 1](/service-1): Description
- [Service 2](/service-2): Description

See https://llmstxt.org for the full spec.

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

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

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

Priced offers found, but no clear checkout path for agents

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.

Live chat / conversational widget detected

Missing semantic HTML: <footer>
Add missing semantic HTML elements: <footer>

Only 76% of images have alt text (53/70)
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)

5 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, address)

2 industry directory links found

Response time is 3.0s — acceptable, could be faster

Lean HTML payload (211KB)

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

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"

Footer/copyright year is current

HTTPS enabled

SSL certificate valid

Privacy policy link found

Terms of service link found

tango.us

https://tango.us

Readiness orbit

Top Priorities

Findings and fixes

All Findings

Turn audit findings into an agent-ready funnel.

Related AX Scores