AX監査レポート

https://nexu.mx

August 12, 20263411ms 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件

5 warnings

合格 25件

Current constraintAgent Integration50%

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

11.8 / 22 weighted points

54%

Access

26.3 / 31 weighted points

85%

Agent Integration

Current constraint

12.1 / 24 weighted points

50%

User Experience

6.7 / 10 weighted points

67%

Start here

Top Priorities

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

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

構造化データ

Review

Missing semantic HTML: <nav>, multiple <h1> tags (use only one)

コンテンツ品質

Review

Explore the audit

Findings and fixes

構造化データ

Authoritativeness

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

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

API specification found at /openapi.yaml

sitemap.xml found and valid

RSS/Atom feed detected

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

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

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

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

95% of images have alt text (60/63)

Sufficient text content available for AI extraction

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

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

Google Maps / Business Profile presence detected

Contact information detected (phone, email)

Response time is 3.4s — slower than agents prefer

Lean HTML payload (194KB)

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

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

Partial security headers (CSP only)

Content dates (dateModified/datePublished) present in schema

Sitemap content hasn't changed in over a year

No current year found — the site may look stale to agents

HTTPS enabled

SSL certificate valid

No privacy policy link detected

No terms of service link detected

nexu.mx