Relatório de Auditoria AX

https://ilabservice.us

August 12, 20262014ms response

49AX score / 100

Fraco

Readiness diagnosis

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

1 crítico

7 warnings

17 aprovado

Current constraintAgent Integration28%

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.5 / 13 weighted points

34%

Identity

11.5 / 22 weighted points

52%

Access

22.7 / 31 weighted points

73%

Agent Integration

Current constraint

6.7 / 24 weighted points

28%

User Experience

3.3 / 10 weighted points

33%

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

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

1 button with vague labels (e.g., "Click here")

Actionability

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 1 JSON-LD structured data block

JSON-LD found but no business schema (found: WebSite)
Add a business-specific schema type (LocalBusiness, Organization, Product, Service) to help AI agents understand what your business offers.

Schema has 3 fields — consider adding more for better AI comprehension

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.

MCP configuration found at /.well-known/mcp.json, /.well-known/mcp

AI agent plugin manifest found at /.well-known/ai-plugin.json, /.well-known/ai-agent.json

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

Direct contact link found, but no on-page form for agents

1 button with vague labels (e.g., "Click here")
Replace vague button text like "Click here" or "Submit" with descriptive labels like "Book a Demo" or "Get Started". Agents rely on button text to understand page actions.

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

Only 19% of images have alt text (9/48)
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)

8 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.0s — acceptable, could be faster

HTML payload is on the heavier side (659KB)

Response is compressed (gzip)

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

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

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 shows content updated within the last 6 months

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

HTTPS enabled

SSL certificate valid

Privacy policy link found

No terms of service link detected

ilabservice.us

https://ilabservice.us

Readiness orbit

Top Priorities

Findings and fixes

All Findings

Turn audit findings into an agent-ready funnel.

Related AX Scores