AX監査レポート

https://render.com

August 12, 20261304ms response

74AX score / 100

良好

Readiness diagnosis

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

重大 0件

3 warnings

合格 30件

Current constraintDiscovery36%

Five readiness layers

Readiness orbit

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

Evidence profile

33 checks recorded

Passed vs. material gaps

Critical

Warnings

Passed

Discovery

Current constraint

4.6 / 13 weighted points

36%

Identity

19 / 22 weighted points

86%

Access

30.3 / 31 weighted points

98%

Agent Integration

11.0 / 24 weighted points

46%

User Experience

8.7 / 10 weighted points

87%

Start here

Top Priorities

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

llms.txt found but format is incomplete

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

Review

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

Actionability

Review

No form or direct contact path — agents have no way to convert here

Actionability

Review

Explore the audit

Findings and fixes

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

Actionability

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

Business schema found: Organization

OpenGraph tags complete (title, description, image)

Meta tags complete (title, description, canonical)

llms.txt found but format is incomplete
Your llms.txt should have: # Title, > description blockquote, ## Sections, and [links](url). See https://llmstxt.org for the full spec.

llms-full.txt also found (two-file mode)

MCP configuration found at /.well-known/mcp.json, /.well-known/mcp

API documentation links found

API specification found at /openapi.json

Sitemap found at https://render.com/sitemap-index.xml (declared in robots.txt)

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

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

Priced offers found, but no clear checkout path for agents

No form or direct contact path — agents have no way to convert here
Add an agent-usable conversion path — a contact form, a booking widget, or a Dashform AI funnel agents can complete on the visitor's behalf.

CTA buttons have descriptive labels

HTML semantic structure is well-formed

81% of images have alt text (44/54)

Sufficient text content available for AI extraction

5 social media links found

Schema.org sameAs links found (cross-platform identity)

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.

Limited contact information — add phone, email, and address

Fast response time (1304ms)

Lean HTML payload (368KB)

Response is compressed (gzip)

Caching headers present (Cache-Control/ETag/Last-Modified)

Author/publisher identity declared in schema

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"

Footer/copyright year is current

HTTPS enabled

SSL certificate valid

Privacy policy link found

Terms of service link found

AX監査レポート

render.com

AX監査レポート

https://render.com

August 12, 20261304ms response

74AX score / 100

良好

Readiness diagnosis

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

重大 0件

3 warnings

合格 30件

Current constraintDiscovery36%

Five readiness layers

Readiness orbit

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

Evidence profile

33 checks recorded

Passed vs. material gaps

Critical

Warnings

Passed

Discovery

Current constraint

4.6 / 13 weighted points

36%

Identity

19 / 22 weighted points

86%

Access

30.3 / 31 weighted points

98%

Agent Integration

11.0 / 24 weighted points

46%

User Experience

8.7 / 10 weighted points

87%

Start here

Top Priorities

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

llms.txt found but format is incomplete

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

Review

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

Actionability

Review

No form or direct contact path — agents have no way to convert here

Actionability

Review

Explore the audit

Findings and fixes

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

Actionability

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

Business schema found: Organization

OpenGraph tags complete (title, description, image)

Meta tags complete (title, description, canonical)

llms.txt found but format is incomplete
Your llms.txt should have: # Title, > description blockquote, ## Sections, and [links](url). See https://llmstxt.org for the full spec.

llms-full.txt also found (two-file mode)

MCP configuration found at /.well-known/mcp.json, /.well-known/mcp

API documentation links found

API specification found at /openapi.json

Sitemap found at https://render.com/sitemap-index.xml (declared in robots.txt)

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

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

Priced offers found, but no clear checkout path for agents

No form or direct contact path — agents have no way to convert here
Add an agent-usable conversion path — a contact form, a booking widget, or a Dashform AI funnel agents can complete on the visitor's behalf.

CTA buttons have descriptive labels

HTML semantic structure is well-formed

81% of images have alt text (44/54)

Sufficient text content available for AI extraction

5 social media links found

Schema.org sameAs links found (cross-platform identity)

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.

Limited contact information — add phone, email, and address

Fast response time (1304ms)

Lean HTML payload (368KB)

Response is compressed (gzip)

Caching headers present (Cache-Control/ETag/Last-Modified)

Author/publisher identity declared in schema

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"

Footer/copyright year is current

HTTPS enabled

SSL certificate valid

Privacy policy link found

Terms of service link found

https://render.com

Readiness orbit

Top Priorities

Findings and fixes

All Findings

Turn audit findings into an agent-ready funnel.

render.com

https://render.com

Readiness orbit

Top Priorities

Findings and fixes

All Findings

Turn audit findings into an agent-ready funnel.