Rapport d'audit AX

https://metricwire.com

August 12, 20262760ms 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 critique

5 warnings

20 réussi

Current constraintAgent Integration37%

Five readiness layers

Readiness orbit

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

Evidence profile

26 checks recorded

Passed vs. material gaps

Critical

Warnings

Passed

Discovery

5.7 / 13 weighted points

44%

Identity

14.2 / 22 weighted points

65%

Access

24.1 / 31 weighted points

78%

Agent Integration

Current constraint

9.0 / 24 weighted points

37%

User Experience

6.7 / 10 weighted points

67%

Start here

Top Priorities

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

CAPTCHA or bot protection detected

Crawlabilité

Review

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

Interaction avec l'agent

Review

1 button with vague labels (e.g., "Click here")

Actionability

Review

Missing semantic HTML: <main>

Qualité du contenu

Review

Only 50% of images have alt text (15/30)

Qualité du contenu

Review

Explore the audit

Findings and fixes

Crawlabilité

Performance

Sécurité et confiance

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

Business schema found: Organization, Organization

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

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

RSS/Atom feed detected

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

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

Contact/lead form with an email field is present

1 button with vague labels (e.g., "Click here")
Replace vague button text like "Click here" or "Submit" with descriptive labels like "Book a Demo" or "Get Started". Agents rely on button text to understand page actions.

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

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

Sufficient text content available for AI extraction

No 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.

Contact information detected (phone, address)

Response time is 2.8s — acceptable, could be faster

Lean HTML payload (399KB)

Response is compressed (br)

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

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 (HSTS only)

Content dates (dateModified/datePublished) present in schema

Sitemap content is 6–12 months old

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

HTTPS enabled

SSL certificate valid

Privacy policy link found

No terms of service link detected

metricwire.com

https://metricwire.com

Readiness orbit

Top Priorities

Findings and fixes

All Findings

Turn audit findings into an agent-ready funnel.

Related AX Scores