AX-Audit-Bericht

https://apnews.com

August 12, 2026570ms response

65AX score / 100

Needs work

Readiness diagnosis

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

1 kritisch

7 warnings

25 bestanden

Current constraintAgent Integration37%

Five readiness layers

Readiness orbit

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

Evidence profile

33 checks recorded

Passed vs. material gaps

Critical

Warnings

Passed

Discovery

6.7 / 13 weighted points

51%

Identity

15.8 / 22 weighted points

72%

Access

25.7 / 31 weighted points

83%

Agent Integration

Current constraint

9.0 / 24 weighted points

37%

User Experience

7.3 / 10 weighted points

73%

Start here

Top Priorities

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

CAPTCHA or bot protection detected

Crawlbarkeit

Review

JSON-LD found but no business schema (found: WebSite, NewsMediaOrganization)

Strukturierte Daten

Review

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

Agenteninteraktion

Review

No sitemap.xml found

Agenteninteraktion

Review

Missing semantic HTML: <header>, <h1>

Inhaltsqualität

Review

Explore the audit

Findings and fixes

Crawlbarkeit

Performance

Sicherheit & Vertrauen

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

Schema has 7 fields — consider adding more for better AI comprehension

OpenGraph tags complete (title, description, image)

Meta tags complete (title, description, canonical)

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.

API documentation links found

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

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

A form is present but has no obvious email field

CTA buttons have descriptive labels

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

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

Sufficient text content available for AI extraction

9 social media links found

Schema.org sameAs links found (cross-platform identity)

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 (570ms)

Very large HTML payload (2206KB) — agents may truncate it
Trim your initial HTML payload — defer non-critical markup and avoid inlining large data blobs. Agents truncate very large documents.

Response is compressed (br)

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

Author/publisher identity declared in schema

No review/rating schema — agents can't surface your reputation

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"

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

apnews.com

https://apnews.com

Readiness orbit

Top Priorities

Findings and fixes

All Findings

Turn audit findings into an agent-ready funnel.

Related AX Scores