AX監査レポート

https://nomi.so

August 12, 2026993ms response

68AX score / 100

Needs work

Readiness diagnosis

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

重大 1件

4 warnings

合格 29件

Current constraintDiscovery33%

Five readiness layers

Readiness orbit

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

Evidence profile

34 checks recorded

Passed vs. material gaps

Critical

Warnings

Passed

Discovery

Current constraint

4.3 / 13 weighted points

33%

Identity

11.8 / 22 weighted points

54%

Access

26.4 / 31 weighted points

85%

Agent Integration

15.3 / 24 weighted points

64%

User Experience

10 / 10 weighted points

100%

Start here

Top Priorities

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

CAPTCHA or bot protection detected

クロール可能性

Review

JSON-LD found but no business schema (found: unknown)

構造化データ

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 1 JSON-LD structured data block

JSON-LD found but no business schema (found: unknown)
Add a business-specific schema type (LocalBusiness, Organization, Product, Service) to help AI agents understand what your business offers.

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

OpenGraph tags complete (title, description, image)

Meta tags complete (title, description, canonical)

JSON-LD schema missing @context or @type

llms.txt found but format is incorrect

llms-full.txt also found (two-file mode)

MCP configuration found at /.well-known/mcp.json, /mcp.json, /.mcp.json, /.well-known/mcp

AI agent plugin manifest found at /.well-known/ai-plugin.json, /.well-known/ai-agent.json

API specification found at /openapi.json

sitemap.xml found and valid

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

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

Priced offers found, but no clear checkout path for agents

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

CTA buttons have descriptive labels

HTML semantic structure is well-formed

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

Sufficient text content available for AI extraction

FAQ schema detected

1 social media link 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"
]

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

Fast response time (993ms)

Lean HTML payload (232KB)

Response is compressed (br)

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

Entry URL redirects before serving — adds latency for agents

Author/publisher identity declared in schema

No review/rating schema — agents can't surface your reputation

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"

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

nomi.so