AX監査レポート

https://plai.io

August 12, 20261335ms response

64AX score / 100

Needs work

Readiness diagnosis

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

重大 0件

4 warnings

合格 24件

Current constraintDiscovery31%

Five readiness layers

Readiness orbit

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

Evidence profile

28 checks recorded

Passed vs. material gaps

Critical

Warnings

Passed

Discovery

Current constraint

4 / 13 weighted points

31%

Identity

14.7 / 22 weighted points

67%

Access

29.7 / 31 weighted points

96%

Agent Integration

10.8 / 24 weighted points

45%

User Experience

4.7 / 10 weighted points

47%

Start here

Top Priorities

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

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

エージェントインタラクション

Review

Missing semantic HTML: <main>, <header>, <footer>

コンテンツ品質

Review

Only 15% of images have alt text (23/156)

コンテンツ品質

Review

Explore the audit

Findings and fixes

エージェントインタラクション

Actionability

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

Business schema found: Organization

Schema has 6 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 found at https://www.plai.io/sitemap.xml (declared in robots.txt)

Embedded conversion target declared — agents can act on the funnel's conversion URL
Conversion URL: https://calendly.com/d/cprv-cjf-x8h

Booking/scheduling integration detected

Contact/lead form with an email field is present

CTA buttons have descriptive labels

Missing semantic HTML: <main>, <header>, <footer>
Add missing semantic HTML elements: <main>, <header>, <footer>

Only 15% of images have alt text (23/156)
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

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

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

Limited contact information — add phone, email, and address

Fast response time (1335ms)

Lean HTML payload (99KB)

Response is compressed (gzip)

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

Entry URL redirects before serving — adds latency for agents

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

No HSTS or CSP headers detected
Add Strict-Transport-Security and Content-Security-Policy headers — they signal a well-maintained, trustworthy origin.

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

plai.io

https://plai.io

Readiness orbit

Top Priorities

Findings and fixes

All Findings

Turn audit findings into an agent-ready funnel.

Related AX Scores