Relatório de Auditoria AX

https://bolsterbuilt.com

August 12, 20262753ms response

58AX score / 100

Needs work

Readiness diagnosis

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

1 crítico

6 warnings

23 aprovado

Current constraintAgent Integration27%

Five readiness layers

Readiness orbit

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

Evidence profile

30 checks recorded

Passed vs. material gaps

Critical

Warnings

Passed

Discovery

5.6 / 13 weighted points

43%

Identity

15.4 / 22 weighted points

70%

Access

25.7 / 31 weighted points

83%

Agent Integration

Current constraint

6.4 / 24 weighted points

27%

User Experience

5.3 / 10 weighted points

53%

Start here

Top Priorities

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

CAPTCHA or bot protection detected

Rastreabilidade

Review

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

Dados Estruturados

Review

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

Actionability

Review

Missing semantic HTML: <main>, <header>, <footer>

Qualidade do Conteúdo

Review

Only 71% of images have alt text (32/45)

Qualidade do Conteúdo

Review

Explore the audit

Findings and fixes

Rastreabilidade

Performance

Segurança e Confiança

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: SoftwareApplication)
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 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

Contact/lead form with an email field is present

CTA buttons have descriptive labels

Missing semantic HTML: <main>, <header>, <footer>
Add missing semantic HTML elements: <main>, <header>, <footer>

Only 71% of images have alt text (32/45)
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)

No social media links found

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

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

Contact information detected (phone, address)

1 industry directory link found

Response time is 2.8s — acceptable, could be faster

Lean HTML payload (151KB)

Response is compressed (gzip)

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

Entry URL redirects before serving — adds latency for agents

Author/publisher identity declared in schema

Review/rating schema found — agents can cite social proof

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"

No current year found — the site may look stale to agents

HTTPS enabled

SSL certificate valid

Privacy policy link found

Terms of service link found

bolsterbuilt.com

https://bolsterbuilt.com

Readiness orbit

Top Priorities

Findings and fixes

All Findings

Turn audit findings into an agent-ready funnel.

Related AX Scores