AX監査レポート

https://onelocal.com

August 12, 20263518ms 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.

重大 0件

3 warnings

合格 25件

Current constraintAgent Integration38%

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

6.2 / 13 weighted points

48%

Identity

17.0 / 22 weighted points

77%

Access

27.7 / 31 weighted points

89%

Agent Integration

Current constraint

9.1 / 24 weighted points

38%

User Experience

6 / 10 weighted points

60%

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>, multiple <h1> tags (use only one)

コンテンツ品質

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

Business schema found: Organization

Schema has 7 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

Embedded conversion target declared — agents can act on the funnel's conversion URL
Conversion URL: https://calendly.com/onelocal2026/book-a-demo-with-onelocal

Booking/scheduling integration detected

Priced offers found, but no clear checkout path for agents

Direct contact link found, but no on-page form for agents

Live chat / conversational widget detected

Missing semantic HTML: <main>, <header>, multiple <h1> tags (use only one)
Add missing semantic HTML elements: <main>, <header>, multiple <h1> tags (use only one)

100% of images have alt text (166/166)

Sufficient text content available for AI extraction

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

12 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, email, address)

Response time is 3.5s — slower than agents prefer

HTML payload is on the heavier side (642KB)

Response is compressed (br)

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

Review/rating schema found — agents can cite social proof

Partial security headers (HSTS 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"

Footer/copyright year is current

HTTPS enabled

SSL certificate valid

Privacy policy link found

Terms of service link found

onelocal.com