Rapport d'audit AX

https://stream.claims

August 12, 20262158ms 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 critique

6 warnings

18 réussi

Current constraintAgent Integration16%

Five readiness layers

Readiness orbit

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

Evidence profile

24 checks recorded

Passed vs. material gaps

Critical

Warnings

Passed

Discovery

3.8 / 13 weighted points

29%

Identity

15.1 / 22 weighted points

68%

Access

29 / 31 weighted points

94%

Agent Integration

Current constraint

3.8 / 24 weighted points

16%

User Experience

7.3 / 10 weighted points

73%

Start here

Top Priorities

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

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

Données structurées

Review

Missing OpenGraph tags: og:title, og:description

Données structurées

Review

No Schema.org potentialAction — agents can't tell what they can do on your site

Actionability

Review

Missing semantic HTML: <header>

Qualité du contenu

Review

Only 55% of images have alt text (6/11)

Qualité du contenu

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

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

Meta tags complete (title, description, canonical)

llms.txt found but format is incorrect

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

No scheduling link found — agents can't book time with you directly

Priced offers found, but no clear checkout path for agents

Direct contact link found, but no on-page form for agents

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

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

Sufficient text content available for AI extraction

1 social media link 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"
]

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

Contact information detected (phone, email)

Response time is 2.2s — acceptable, could be faster

Lean HTML payload (51KB)

Response is compressed (gzip)

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"

Footer/copyright year is current

HTTPS enabled

SSL certificate valid

Privacy policy link found

Terms of service link found

stream.claims

https://stream.claims

Readiness orbit

Top Priorities

Findings and fixes

All Findings

Turn audit findings into an agent-ready funnel.

Related AX Scores