AX 감사 보고서

https://bun.sh

August 12, 2026731ms response

59AX score / 100

Needs work

Readiness diagnosis

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

0개 심각

5 warnings

21개 통과

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

26 checks recorded

Passed vs. material gaps

Critical

Warnings

Passed

Discovery

Current constraint

2.4 / 13 weighted points

18%

Identity

12.3 / 22 weighted points

56%

Access

29 / 31 weighted points

94%

Agent Integration

6.7 / 24 weighted points

28%

User Experience

8.7 / 10 weighted points

87%

Start here

Top Priorities

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

Missing OpenGraph tags: og:title, og:description, og:image

구조화된 데이터

Review

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

구조화된 데이터

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

Business schema found: Organization

Schema has 3 fields — consider adding more for better AI comprehension

Missing OpenGraph tags: og:title, og:description, og:image
<meta property="og:title" content="..." />
<meta property="og:description" content="..." />
<meta property="og:image" content="..." />

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)

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 documentation links found

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

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

95% of images have alt text (20/21)

Sufficient text content available for AI extraction

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

Fast response time (731ms)

Lean HTML payload (283KB)

Response is compressed (br)

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

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

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

bun.sh

https://bun.sh

Readiness orbit

Top Priorities

Findings and fixes

All Findings

Turn audit findings into an agent-ready funnel.

Related AX Scores