Relatório de Auditoria AX

https://reamaze.com

August 12, 20262118ms response

52AX 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

5 warnings

23 aprovado

Current constraintIdentity21%

Five readiness layers

Readiness orbit

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

Evidence profile

29 checks recorded

Passed vs. material gaps

Critical

Warnings

Passed

Discovery

3.2 / 13 weighted points

25%

Identity

Current constraint

4.7 / 22 weighted points

21%

Access

29 / 31 weighted points

94%

Agent Integration

12.4 / 24 weighted points

51%

User Experience

2.7 / 10 weighted points

27%

Start here

Top Priorities

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

No JSON-LD structured data found

Dados Estruturados

Review

Missing OpenGraph tags: og:description

Dados Estruturados

Review

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

Interação com Agente

Review

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

Actionability

Review

Missing semantic HTML: html lang="", <main>, <nav>, <header>, <footer>, multiple <h1> tags (use only one)

Qualidade do Conteúdo

Review

Explore the audit

Findings and fixes

Dados Estruturados

Authoritativeness

All Findings

robots.txt allows all major AI crawlers

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:description
<meta property="og:description" content="..." />

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.

MCP configuration found at /.well-known/mcp

API documentation links found

API specification found at /graphql

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

Booking/scheduling integration detected

Contact/lead form with an email field is present

CTA buttons have descriptive labels

Missing semantic HTML: html lang="", <main>, <nav>, <header>, <footer>, multiple <h1> tags (use only one)
Add missing semantic HTML elements: html lang="", <main>, <nav>, <header>, <footer>, multiple <h1> tags (use only one)

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

Sufficient text content available for AI extraction

FAQ-like content found but no FAQ schema

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)

Response time is 2.1s — acceptable, could be faster

Lean HTML payload (59KB)

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

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

reamaze.com

https://reamaze.com

Readiness orbit

Top Priorities

Findings and fixes

All Findings

Turn audit findings into an agent-ready funnel.

Related AX Scores