AX-Audit-Bericht

https://digibuild.com

August 12, 20262175ms response

45AX score / 100

Schlecht

Readiness diagnosis

This site is not ready for AI agents yet. Resolve the critical access and understanding gaps first.

1 kritisch

6 warnings

16 bestanden

Current constraintAgent Integration11%

Five readiness layers

Readiness orbit

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

Evidence profile

23 checks recorded

Passed vs. material gaps

Critical

Warnings

Passed

Discovery

2.2 / 13 weighted points

17%

Identity

2.6 / 22 weighted points

12%

Access

29 / 31 weighted points

94%

Agent Integration

Current constraint

2.6 / 24 weighted points

11%

User Experience

8.7 / 10 weighted points

87%

Start here

Top Priorities

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

No JSON-LD structured data found

Strukturierte Daten

Review

No robots.txt file found

Crawlbarkeit

Review

Missing OpenGraph tags: og:image

Strukturierte Daten

Review

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

Agenteninteraktion

Review

No sitemap.xml found

Agenteninteraktion

Review

Explore the audit

Findings and fixes

Strukturierte Daten

Authoritativeness

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

No JSON-LD structured data found
Add JSON-LD structured data to your page <head>:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Your Business",
  "url": "https://yoursite.com",
  "description": "What your business does"
}
</script>

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

Missing meta tags: canonical link

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

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

CTA buttons have descriptive labels

HTML semantic structure is well-formed

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

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, email)

Response time is 2.2s — acceptable, could be faster

Lean HTML payload (46KB)

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

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"

Footer/copyright year is current

HTTPS enabled

SSL certificate valid

Privacy policy link found

Terms of service link found

digibuild.com

https://digibuild.com

Readiness orbit

Top Priorities

Findings and fixes

All Findings

Turn audit findings into an agent-ready funnel.

Related AX Scores