AX-Audit-Bericht

https://dyspatch.io

August 12, 20262145ms response

71AX score / 100

Gut

Readiness diagnosis

This site is mostly ready for AI agents. A few focused improvements can close the remaining gaps.

0 kritisch

4 warnings

28 bestanden

Current constraintAgent Integration46%

Five readiness layers

Readiness orbit

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

Evidence profile

32 checks recorded

Passed vs. material gaps

Critical

Warnings

Passed

Discovery

8.6 / 13 weighted points

66%

Identity

12.4 / 22 weighted points

56%

Access

29 / 31 weighted points

94%

Agent Integration

Current constraint

10.9 / 24 weighted points

46%

User Experience

10 / 10 weighted points

100%

Start here

Top Priorities

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

No robots.txt file found

Crawlbarkeit

Review

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

Strukturierte Daten

Review

llms.txt found but format is incomplete

Agenteninteraktion

Review

Explore the audit

Findings and fixes

Crawlbarkeit

Performance

Sicherheit & Vertrauen

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

JSON-LD found but no business schema (found: FAQPage)
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)

llms.txt found but format is incomplete
Your llms.txt should have: # Title, > description blockquote, ## Sections, and [links](url). See https://llmstxt.org for the full spec.

Page mentions MCP support but no MCP endpoint found

sitemap.xml found and valid

RSS/Atom feed detected

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

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

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

CTA buttons have descriptive labels

HTML semantic structure is well-formed

97% of images have alt text (29/30)

Sufficient text content available for AI extraction

FAQ schema detected

5 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)

1 industry directory link found

Response time is 2.1s — acceptable, could be faster

Lean HTML payload (300KB)

Response is compressed (br)

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

Entry URL redirects before serving — adds latency for agents

Author/publisher identity declared in schema

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.

Content dates (dateModified/datePublished) present in schema

Sitemap shows content updated within the last 6 months

Footer/copyright year is current

HTTPS enabled

SSL certificate valid

Privacy policy link found

Terms of service link found

dyspatch.io

https://dyspatch.io

Readiness orbit

Top Priorities

Findings and fixes

All Findings

Turn audit findings into an agent-ready funnel.

Related AX Scores