AX監査レポート

https://wrike.com

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

3 warnings

合格 28件

Current constraintDiscovery48%

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

6.2 / 13 weighted points

48%

Identity

19.2 / 22 weighted points

87%

Access

21.9 / 31 weighted points

71%

Agent Integration

13.1 / 24 weighted points

54%

User Experience

7.3 / 10 weighted points

73%

Start here

Top Priorities

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

CAPTCHA or bot protection detected

クロール可能性

Review

SPA framework detected with minimal server-rendered content — page may depend on JavaScript rendering

クロール可能性

Review

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

Actionability

Review

Explore the audit

Findings and fixes

クロール可能性

Performance

セキュリティと信頼

All Findings

robots.txt allows all major AI crawlers

Page returns HTTP 200

SPA framework detected with minimal server-rendered content — page may depend on JavaScript rendering
Body text: 261556 chars, Scripts: 70, Noscript: none
Ensure critical content is rendered in the initial HTML response (server-side rendering). AI crawlers typically do not execute JavaScript. Consider using SSR, SSG, or pre-rendering.

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

Business schema found: Product, Organization

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

Page mentions MCP support but no MCP endpoint found

API documentation links found

sitemap.xml found and valid

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

CTA buttons have descriptive labels

HTML semantic structure is well-formed

90% of images have alt text (60/67)

Sufficient text content available for AI extraction

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

5 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, address)

Response time is 2.1s — acceptable, could be faster

Large HTML payload (1256KB)

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

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

wrike.com

https://wrike.com

Readiness orbit

Top Priorities

Findings and fixes

All Findings

Turn audit findings into an agent-ready funnel.

Related AX Scores