Relatório de Auditoria AX

https://roadmunk.com

August 12, 20261234ms response

44AX score / 100

Fraco

Readiness diagnosis

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

2 crítico

5 warnings

18 aprovado

Global rank

#3985/5215

Communication & Support rank

#142/166

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

25 checks recorded

Passed vs. material gaps

Critical

Warnings

Passed

Discovery

3.2 / 13 weighted points

25%

Identity

5.3 / 22 weighted points

24%

Access

26.4 / 31 weighted points

85%

Agent Integration

Current constraint

2.6 / 24 weighted points

11%

User Experience

6 / 10 weighted points

60%

Start here

Top Priorities

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

CAPTCHA or bot protection detected

Rastreabilidade

Review

No JSON-LD structured data found

Dados Estruturados

Review

No robots.txt file found

Rastreabilidade

Review

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

Interação com Agente

Review

No sitemap.xml found

Interação com Agente

Review

Benchmark context

Related AX Scores

Leading scores in Communication & Support.

Explore benchmarks

Explore the audit

Findings and fixes

Rastreabilidade

Performance

Segurança e Confiança

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

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.

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

Only 31% of images have alt text (14/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)

4 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 (1234ms)

Lean HTML payload (366KB)

Response is compressed (br)

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

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

Relatório de Auditoria AX

roadmunk.com

Relatório de Auditoria AX

https://roadmunk.com

August 12, 20261234ms response

44AX score / 100

Fraco

Readiness diagnosis

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

2 crítico

5 warnings

18 aprovado

Global rank

#3985/5215

Communication & Support rank

#142/166

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

25 checks recorded

Passed vs. material gaps

Critical

Warnings

Passed

Discovery

3.2 / 13 weighted points

25%

Identity

5.3 / 22 weighted points

24%

Access

26.4 / 31 weighted points

85%

Agent Integration

Current constraint

2.6 / 24 weighted points

11%

User Experience

6 / 10 weighted points

60%

Start here

Top Priorities

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

CAPTCHA or bot protection detected

Rastreabilidade

Review

No JSON-LD structured data found

Dados Estruturados

Review

No robots.txt file found

Rastreabilidade

Review

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

Interação com Agente

Review

No sitemap.xml found

Interação com Agente

Review

Benchmark context

Related AX Scores

Leading scores in Communication & Support.

Explore benchmarks

Explore the audit

Findings and fixes

Rastreabilidade

Performance

Segurança e Confiança

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

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.

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

Only 31% of images have alt text (14/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)

4 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 (1234ms)

Lean HTML payload (366KB)

Response is compressed (br)

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

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

https://roadmunk.com

Readiness orbit

Top Priorities

Related AX Scores

Findings and fixes

All Findings

Turn audit findings into an agent-ready funnel.

roadmunk.com

https://roadmunk.com

Readiness orbit

Top Priorities

Related AX Scores

Findings and fixes

All Findings

Turn audit findings into an agent-ready funnel.