AX監査レポート

https://retellai.com

August 12, 20261302ms response

66AX score / 100

Needs work

Readiness diagnosis

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

重大 1件

5 warnings

合格 26件

Current constraintDiscovery42%

Five readiness layers

Readiness orbit

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

Evidence profile

32 checks recorded

Passed vs. material gaps

Critical

Warnings

Passed

Discovery

Current constraint

5.4 / 13 weighted points

42%

Identity

17.3 / 22 weighted points

79%

Access

26.4 / 31 weighted points

85%

Agent Integration

Current constraint

10.1 / 24 weighted points

42%

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

クロール可能性

Review

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

Actionability

Review

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

Actionability

Review

Missing semantic HTML: <header>

コンテンツ品質

Review

Only 8% of images have alt text (8/106)

コンテンツ品質

Review

Explore the audit

Findings and fixes

クロール可能性

Performance

セキュリティと信頼

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

Business schema found: Product

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

OpenGraph tags complete (title, description, image)

Meta tags complete (title, description, canonical)

llms.txt found with correct format

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 found at https://docs.retellai.com/sitemap.xml (declared in robots.txt)

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"
}

Booking/scheduling integration detected

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

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

Sufficient text content available for AI extraction

FAQ-like content found but no FAQ schema

3 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 (1302ms)

Lean HTML payload (388KB)

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

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

retellai.com

https://retellai.com

Readiness orbit

Top Priorities

Findings and fixes

All Findings

Turn audit findings into an agent-ready funnel.

Related AX Scores