Relatório de Auditoria AX

https://assembly.com

August 12, 20261578ms response

60AX score / 100

Needs work

Readiness diagnosis

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

0 crítico

5 warnings

22 aprovado

Current constraintAgent Integration13%

Five readiness layers

Readiness orbit

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

Evidence profile

27 checks recorded

Passed vs. material gaps

Critical

Warnings

Passed

Discovery

3.2 / 13 weighted points

25%

Identity

16.4 / 22 weighted points

75%

Access

29.7 / 31 weighted points

96%

Agent Integration

Current constraint

3.1 / 24 weighted points

13%

User Experience

7.3 / 10 weighted points

73%

Start here

Top Priorities

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

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

No form or direct contact path — agents have no way to convert here

Actionability

Review

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

Qualidade do Conteúdo

Review

Explore the audit

Findings and fixes

Interação com Agente

Actionability

All Findings

robots.txt allows all major AI crawlers

Page returns HTTP 200

Page content available without JavaScript

No CAPTCHA or bot protection detected

Found 2 JSON-LD structured data blocks

Business schema found: Organization

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.

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

No form or direct contact path — agents have no way to convert here
Add an agent-usable conversion path — a contact form, a booking widget, or a Dashform AI funnel agents can complete on the visitor's behalf.

CTA buttons have descriptive labels

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

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

Sufficient text content available for AI extraction

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

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

Limited contact information — add phone, email, and address

Response time is 1.6s — acceptable, could be faster

Lean HTML payload (198KB)

Response is compressed (br)

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

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

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

assembly.com

https://assembly.com

Readiness orbit

Top Priorities

Findings and fixes

All Findings

Turn audit findings into an agent-ready funnel.

Related AX Scores