AX 감사 보고서

https://coveragecat.com

August 12, 20263274ms 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.

0개 심각

7 warnings

22개 통과

Current constraintAgent Integration35%

Five readiness layers

Readiness orbit

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

Evidence profile

29 checks recorded

Passed vs. material gaps

Critical

Warnings

Passed

Discovery

5.4 / 13 weighted points

42%

Identity

10.5 / 22 weighted points

48%

Access

27 / 31 weighted points

87%

Agent Integration

Current constraint

8.4 / 24 weighted points

35%

User Experience

6.7 / 10 weighted points

67%

Start here

Top Priorities

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

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

구조화된 데이터

Review

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

Actionability

Review

Missing semantic HTML: <header>, multiple <h1> tags (use only one)

콘텐츠 품질

Review

Response is not compressed (no gzip/brotli)

Performance

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 1 JSON-LD structured data block

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

Missing meta tags: meta description

JSON-LD schema missing @context or @type

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

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

A form is present but has no obvious email field

CTA buttons have descriptive labels

Missing semantic HTML: <header>, multiple <h1> tags (use only one)
Add missing semantic HTML elements: <header>, multiple <h1> tags (use only one)

100% of images have alt text (6/6)

Sufficient text content available for AI extraction

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

No 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"
]

Google Maps / Business Profile presence detected

Contact information detected (phone, email, address)

1 industry directory link found

Response time is 3.3s — slower than agents prefer

Lean HTML payload (73KB)

Response is not compressed (no gzip/brotli)
Enable gzip or Brotli compression on your server/CDN to cut transfer size for agents and crawlers.

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"

Footer/copyright year is current

HTTPS enabled

SSL certificate valid

Privacy policy link found

Terms of service link found

coveragecat.com

https://coveragecat.com

Readiness orbit

Top Priorities

Findings and fixes

All Findings

Turn audit findings into an agent-ready funnel.

Related AX Scores