AX監査レポート

https://gojabu.com

August 12, 20263413ms response

56AX score / 100

Needs work

Readiness diagnosis

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

重大 0件

6 warnings

合格 17件

Current constraintDiscovery18%

Five readiness layers

Readiness orbit

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

Evidence profile

23 checks recorded

Passed vs. material gaps

Critical

Warnings

Passed

Discovery

Current constraint

2.4 / 13 weighted points

18%

Identity

18.3 / 22 weighted points

83%

Access

23.9 / 31 weighted points

77%

Agent Integration

5.1 / 24 weighted points

21%

User Experience

6 / 10 weighted points

60%

Start here

Top Priorities

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

Very little HTML content found — page may depend on JavaScript rendering

クロール可能性

Review

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

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

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

Missing semantic HTML: <main>, <nav>, <header>, <footer>, <h1>

コンテンツ品質

Review

Explore the audit

Findings and fixes

クロール可能性

Performance

セキュリティと信頼

All Findings

robots.txt allows all major AI crawlers

Page returns HTTP 200

Very little HTML content found — page may depend on JavaScript rendering
Body text: 0 chars, Scripts: 7, 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.

No CAPTCHA or bot protection detected

Found 5 JSON-LD structured data blocks

Business schema found: Organization, Product

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.

API specification found at /api-docs

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

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.

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

No images found on page

Very little extractable text content

FAQ schema detected

No 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

Response time is 3.4s — slower than agents prefer

Lean HTML payload (9KB)

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

No privacy policy link detected

No terms of service link detected

gojabu.com

https://gojabu.com

Readiness orbit

Top Priorities

Findings and fixes

All Findings

Turn audit findings into an agent-ready funnel.

Related AX Scores