Отчёт AX Audit

https://iotflows.com

August 12, 20261587ms 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 критических

7 warnings

20 пройдено

Current constraintAgent Integration14%

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

4 / 13 weighted points

31%

Identity

17.0 / 22 weighted points

77%

Access

27.7 / 31 weighted points

89%

Agent Integration

Current constraint

3.4 / 24 weighted points

14%

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

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

Взаимодействие с агентом

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 2 JSON-LD structured data blocks

Business schema found: Organization

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

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.

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

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 and a checkout path are available to 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.

CTA buttons have descriptive labels

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

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

Sufficient text content available for AI extraction

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

No social media links found

Schema.org sameAs links found (cross-platform identity)

Location or rating data found in schema — consider linking to Google Business Profile

Contact information detected (phone, address)

Response time is 1.6s — acceptable, could be faster

Large HTML payload (1390KB)

Response is compressed (br)

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

Review/rating schema found — agents can cite social proof

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

Privacy policy link found

Terms of service link found

iotflows.com

https://iotflows.com

Readiness orbit

Top Priorities

Findings and fixes

All Findings

Turn audit findings into an agent-ready funnel.

Related AX Scores