Relatório de Auditoria AX

https://alixia.com

August 12, 20263050ms response

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

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

25 checks recorded

Passed vs. material gaps

Critical

Warnings

Passed

Discovery

4.8 / 13 weighted points

37%

Identity

Current constraint

4.7 / 22 weighted points

21%

Access

24.4 / 31 weighted points

79%

Agent Integration

5.7 / 24 weighted points

24%

User Experience

6.7 / 10 weighted points

67%

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 Schema.org potentialAction — agents can't tell what they can do on your site

Actionability

Review

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)

Missing meta tags: canonical link

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.

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: <nav>
Add missing semantic HTML elements: <nav>

100% of images have alt text (38/38)

Sufficient text content available for AI extraction

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

3 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"
]

Google Maps / Business Profile presence detected

Contact information detected (phone, email)

Response time is 3.0s — slower than agents prefer

Lean HTML payload (167KB)

Response is compressed (br)

No caching headers — repeat agent fetches can't be revalidated

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

9 authoritative citations (.gov/.edu/Wikipedia)

No HSTS or CSP headers detected
Add Strict-Transport-Security and Content-Security-Policy headers — they signal a well-maintained, trustworthy origin.

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 content hasn't changed in over a year

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

alixia.com

https://alixia.com

Readiness orbit

Top Priorities

Findings and fixes

All Findings

Turn audit findings into an agent-ready funnel.

Related AX Scores