AX監査レポート

https://signnow.com

August 12, 20262896ms response

62AX score / 100

Needs work

Readiness diagnosis

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

重大 1件

6 warnings

合格 23件

Current constraintDiscovery37%

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

Current constraint

4.8 / 13 weighted points

37%

Identity

13.1 / 22 weighted points

60%

Access

25.1 / 31 weighted points

81%

Agent Integration

10.7 / 24 weighted points

45%

User Experience

8 / 10 weighted points

80%

Start here

Top Priorities

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

CAPTCHA or bot protection detected

クロール可能性

Review

No robots.txt file found

クロール可能性

Review

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

構造化データ

Review

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

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

Review

No sitemap.xml found

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

Review

Explore the audit

Findings and fixes

クロール可能性

Performance

セキュリティと信頼

All Findings

No robots.txt file found
Create a robots.txt file at your site root. For AI-friendly access:

User-agent: GPTBot
Allow: /

User-agent: ClaudeBot
Allow: /

User-agent: Google-Extended
Allow: /

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

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

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

Page mentions MCP support but no MCP endpoint found

API documentation links found

No sitemap.xml found
Create a /sitemap.xml file listing all your important pages. Also declare it in robots.txt:
Sitemap: https://yoursite.com/sitemap.xml

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

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

Contact/lead form with an email field is present

Live chat / conversational widget detected

CTA buttons have descriptive labels

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

83% of images have alt text (53/64)

Sufficient text content available for AI extraction

FAQ schema detected

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

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

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)

4 industry directory links found

Response time is 2.9s — acceptable, could be faster

HTML payload is on the heavier side (587KB)

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

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

signnow.com

https://signnow.com

Readiness orbit

Top Priorities

Findings and fixes

All Findings

Turn audit findings into an agent-ready funnel.

Related AX Scores