AX 감사 보고서

https://firehydrant.com

August 12, 20261012ms 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개 심각

8 warnings

19개 통과

Current constraintDiscovery17%

Five readiness layers

Readiness orbit

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

Evidence profile

27 checks recorded

Passed vs. material gaps

Critical

Warnings

Passed

Discovery

Current constraint

2.2 / 13 weighted points

17%

Identity

12.3 / 22 weighted points

56%

Access

29.3 / 31 weighted points

95%

Agent Integration

7.4 / 24 weighted points

31%

User Experience

6.7 / 10 weighted points

67%

Start here

Top Priorities

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

No robots.txt file found

크롤 가능성

Review

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

구조화된 데이터

Review

No sitemap.xml found

에이전트 상호작용

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

크롤 가능성

Performance

보안 및 신뢰

All Findings

No robots.txt file found
Create a robots.txt file at your site root. For AI-friendly access:

User-agent: GPTBot
Allow: /

User-agent: ClaudeBot
Allow: /

User-agent: Google-Extended
Allow: /

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: website)
Add a business-specific schema type (LocalBusiness, Organization, Product, Service) to help AI agents understand what your business offers.

Schema has 3 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.

API documentation links found

No sitemap.xml found
Create a /sitemap.xml file listing all your important pages. Also declare it in robots.txt:
Sitemap: https://yoursite.com/sitemap.xml

RSS/Atom feed detected

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

Missing semantic HTML: <h1>
Add missing semantic HTML elements: <h1>

Only 35% of images have alt text (7/20)
Add descriptive alt attributes to all <img> tags. Example: <img alt="Description of image content" src="..." />

Sufficient text content available for AI extraction

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

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 (1012ms)

Lean HTML payload (253KB)

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"

Footer/copyright year is current

HTTPS enabled

SSL certificate valid

Privacy policy link found

No terms of service link detected

firehydrant.com

https://firehydrant.com

Readiness orbit

Top Priorities

Findings and fixes

All Findings

Turn audit findings into an agent-ready funnel.

Related AX Scores