AX Audit Report

https://betterstack.com

August 12, 20261024ms response

51AX score / 100

Needs work

Readiness diagnosis

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

2 critical

3 warnings

23 passed

Current constraintIdentity24%

Five readiness layers

Readiness orbit

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

Evidence profile

28 checks recorded

Passed vs. material gaps

Critical

Warnings

Passed

Discovery

3.8 / 13 weighted points

29%

Identity

Current constraint

5.3 / 22 weighted points

24%

Access

25.4 / 31 weighted points

82%

Agent Integration

11.5 / 24 weighted points

48%

User Experience

4.7 / 10 weighted points

47%

Start here

Top Priorities

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

CAPTCHA or bot protection detected

Crawlability

Review

No JSON-LD structured data found

Structured Data

Review

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

Agent Interaction

Review

Missing semantic HTML: <main>

Content Quality

Review

Only 0% of images have alt text (0/127)

Content Quality

Review

Explore the audit

Findings and fixes

Crawlability

Performance

Security & Trust

All Findings

robots.txt allows all major AI crawlers

Page returns HTTP 200

Page content available without JavaScript

Cookie consent wall detected — may block AI crawlers

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

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>

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.

Page mentions MCP support but no MCP endpoint found

sitemap.xml found and valid

Embedded conversion target declared — agents can act on the funnel's conversion URL
Conversion URL: https://calendly.com/betterstack/consultation-migrating-from-datadog

Booking/scheduling integration detected

Contact/lead form with an email field is present

CTA buttons have descriptive labels

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

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

Sufficient text content available for AI extraction

Heading levels skip (e.g., h1 directly to h3)

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

Fast response time (1024ms)

Lean HTML payload (264KB)

Response is compressed (gzip)

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

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"

Footer/copyright year is current

HTTPS enabled

SSL certificate valid

Privacy policy link found

Terms of service link found

betterstack.com

https://betterstack.com

Readiness orbit

Top Priorities

Findings and fixes

All Findings

Turn audit findings into an agent-ready funnel.

Related AX Scores