Отчёт AX Audit

https://povio.com

August 12, 20261571ms response

63AX score / 100

Needs work

Readiness diagnosis

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

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

4 warnings

26 пройдено

Current constraintDiscovery25%

Five readiness layers

Readiness orbit

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

Evidence profile

31 checks recorded

Passed vs. material gaps

Critical

Warnings

Passed

Discovery

Current constraint

3.2 / 13 weighted points

25%

Identity

14.1 / 22 weighted points

64%

Access

26.4 / 31 weighted points

85%

Agent Integration

10.8 / 24 weighted points

45%

User Experience

8.7 / 10 weighted points

87%

Start here

Top Priorities

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

CAPTCHA or bot protection detected

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

Review

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

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

Review

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

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

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

Found 2 JSON-LD structured data blocks

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)

Meta tags complete (title, description, canonical)

JSON-LD schema missing @context or @type

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

Embedded conversion target declared — agents can act on the funnel's conversion URL
Conversion URL: https://app.cal.com/meet-povio/free-consultation

Booking/scheduling integration detected

A form is present but has no obvious email field

Live chat / conversational widget detected

CTA buttons have descriptive labels

HTML semantic structure is well-formed

94% of images have alt text (62/66)

Sufficient text content available for AI extraction

4 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.

Contact information detected (phone, address)

Response time is 1.6s — acceptable, could be faster

Lean HTML payload (329KB)

Response is compressed (gzip)

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

Author/publisher identity declared in schema

Review/rating schema found — agents can cite social proof

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"

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

povio.com

https://povio.com

Readiness orbit

Top Priorities

Findings and fixes

All Findings

Turn audit findings into an agent-ready funnel.

Related AX Scores