AX監査レポート

https://zscaler.com

August 12, 20261888ms response

58AX 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

合格 23件

Current constraintAgent Integration34%

Five readiness layers

Readiness orbit

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

Evidence profile

27 checks recorded

Passed vs. material gaps

Critical

Warnings

Passed

Discovery

5.1 / 13 weighted points

39%

Identity

13.0 / 22 weighted points

59%

Access

24.7 / 31 weighted points

80%

Agent Integration

Current constraint

8.3 / 24 weighted points

34%

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

JSON-LD found but no business schema (found: SiteNavigationElement, ImageObject, ImageObject, ImageObject, ImageObject, ImageObject, ImageObject, ImageObject, ImageObject, ImageObject, ImageObject, ImageObject, ImageObject, ImageObject, ImageObject, ImageObject, ImageObject, ImageObject, ImageObject, ImageObject, ImageObject, ImageObject, ImageObject, ImageObject, ImageObject, ImageObject, ImageObject, ImageObject, ImageObject, ImageObject, ImageObject, ImageObject, ImageObject, ImageObject, ImageObject, ImageObject, ImageObject, ImageObject, ImageObject, ImageObject, ImageObject, ImageObject, ImageObject, ImageObject, ImageObject, ImageObject, ImageObject, ImageObject, Report, Report, Report, Report, WebSite)

構造化データ

Review

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

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

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

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

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

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

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

A form is present but has no obvious email field

CTA buttons have descriptive labels

HTML semantic structure is well-formed

98% of images have alt text (47/48)

Sufficient text content available for AI extraction

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

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

Response time is 1.9s — acceptable, could be faster

Lean HTML payload (371KB)

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

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

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"

Sitemap shows content updated within the last 6 months

Footer/copyright year is current

HTTPS enabled

SSL certificate valid

Privacy policy link found

No terms of service link detected

zscaler.com

https://zscaler.com

Readiness orbit

Top Priorities

Findings and fixes

All Findings

Turn audit findings into an agent-ready funnel.

Related AX Scores