Отчёт AX Audit

https://gethealthkey.com

August 12, 20261710ms response

45AX score / 100

Слабо

Readiness diagnosis

This site is not ready for AI agents yet. Resolve the critical access and understanding gaps first.

2 критических

3 warnings

18 пройдено

Current constraintIdentity17%

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

2.7 / 13 weighted points

21%

Identity

Current constraint

3.8 / 22 weighted points

17%

Access

24.4 / 31 weighted points

79%

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.

CAPTCHA or bot protection detected

Индексируемость

Review

No JSON-LD structured data found

Структурированные данные

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

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

Качество контента

Review

Explore the audit

Findings and fixes

Индексируемость

Performance

Безопасность и доверие

All Findings

robots.txt allows all major AI crawlers

Page returns HTTP 200

Page content available without JavaScript

CAPTCHA or bot protection detected
Consider allowing AI crawlers to bypass bot protection. Options:
1. Whitelist known AI crawler IPs (OpenAI, Anthropic, Google publish their ranges)
2. Use robots.txt to signal crawler access
3. Configure your WAF/CDN to exempt verified bot traffic

No JSON-LD structured data found
Add JSON-LD structured data to your page <head>:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Your Business",
  "url": "https://yoursite.com",
  "description": "What your business does"
}
</script>

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.

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

Booking/scheduling integration detected

Contact/lead form with an email field is present

CTA buttons have descriptive labels

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

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

Sufficient text content available for AI extraction

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

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 1.7s — acceptable, could be faster

Lean HTML payload (286KB)

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

No HSTS or CSP headers detected
Add Strict-Transport-Security and Content-Security-Policy headers — they signal a well-maintained, trustworthy origin.

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"

Sitemap shows content updated within the last 6 months

Footer/copyright year is current

HTTPS enabled

SSL certificate valid

No privacy policy link detected

No terms of service link detected

gethealthkey.com

https://gethealthkey.com

Readiness orbit

Top Priorities

Findings and fixes

All Findings

Turn audit findings into an agent-ready funnel.

Related AX Scores