Rapport d'audit AX

https://poly.app

August 12, 20261407ms response

50AX score / 100

Needs work

Readiness diagnosis

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

0 critique

10 warnings

16 réussi

Current constraintDiscovery12%

Five readiness layers

Readiness orbit

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

Evidence profile

26 checks recorded

Passed vs. material gaps

Critical

Warnings

Passed

Discovery

Current constraint

1.6 / 13 weighted points

12%

Identity

8.3 / 22 weighted points

38%

Access

29.3 / 31 weighted points

95%

Agent Integration

5.1 / 24 weighted points

21%

User Experience

5.3 / 10 weighted points

53%

Start here

Top Priorities

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

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

Données structurées

Review

Missing OpenGraph tags: og:title

Données structurées

Review

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

Interaction avec l'agent

Review

No sitemap.xml found

Interaction avec l'agent

Review

No form or direct contact path — agents have no way to convert here

Actionability

Review

Explore the audit

Findings and fixes

Données structurées

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

Missing OpenGraph tags: og:title
<meta property="og:title" content="..." />

Missing meta tags: canonical link

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.

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

Schema.org potentialAction defined — agents know what actions are available

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: <main>, <nav>, <header>, <h1>
Add missing semantic HTML elements: <main>, <nav>, <header>, <h1>

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

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.

Contact information detected (phone, address)

Fast response time (1407ms)

Lean HTML payload (136KB)

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"

No current year found — the site may look stale to agents

HTTPS enabled

SSL certificate valid

Privacy policy link found

No terms of service link detected

poly.app

https://poly.app

Readiness orbit

Top Priorities

Findings and fixes

All Findings

Turn audit findings into an agent-ready funnel.

Related AX Scores