Rapport d'audit AX

https://clay.com

August 12, 20261374ms response

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

6 warnings

23 réussi

Current constraintAgent Integration33%

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

6.7 / 13 weighted points

51%

Identity

17.8 / 22 weighted points

81%

Access

25.7 / 31 weighted points

83%

Agent Integration

Current constraint

7.8 / 24 weighted points

33%

User Experience

7.3 / 10 weighted points

73%

Start here

Top Priorities

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

CAPTCHA or bot protection detected

Crawlabilité

Review

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

Données structurées

Review

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

Interaction avec l'agent

Review

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

Actionability

Review

2 buttons with vague labels (e.g., "Click here")

Actionability

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

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

MCP configuration found at /mcp.json

sitemap.xml found and valid

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

A form is present but has no obvious email field

Live chat / conversational widget detected

2 buttons 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: <header>
Add missing semantic HTML elements: <header>

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

Sufficient text content available for AI extraction

10 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

Limited contact information — add phone, email, and address

1 industry directory link found

Fast response time (1374ms)

HTML payload is on the heavier side (490KB)

Response is compressed (gzip)

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

Partial security headers (CSP only)

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"

Sitemap shows content updated within the last 6 months

Footer/copyright year is current

HTTPS enabled

SSL certificate valid

Privacy policy link found

Terms of service link found

clay.com

https://clay.com

Readiness orbit

Top Priorities

Findings and fixes

All Findings

Turn audit findings into an agent-ready funnel.

Related AX Scores