AX監査レポート

https://paycom.com

August 12, 20263878ms response

71AX score / 100

良好

Readiness diagnosis

This site is mostly ready for AI agents. A few focused improvements can close the remaining gaps.

重大 0件

2 warnings

合格 29件

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

31 checks recorded

Passed vs. material gaps

Critical

Warnings

Passed

Discovery

Current constraint

6.2 / 13 weighted points

48%

Identity

15.4 / 22 weighted points

70%

Access

28.3 / 31 weighted points

91%

Agent Integration

12.7 / 24 weighted points

53%

User Experience

8.7 / 10 weighted points

87%

Start here

Top Priorities

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

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

構造化データ

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

JSON-LD found but no business schema (found: SoftwareApplication)
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)

llms.txt found with correct format

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

Contact/lead form with an email field is present

CTA buttons have descriptive labels

HTML semantic structure is well-formed

91% of images have alt text (21/23)

Sufficient text content available for AI extraction

6 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 3.9s — slower than agents prefer

Lean HTML payload (252KB)

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

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

paycom.com