Relatório de Auditoria AX

https://nextgen.com

August 12, 20263907ms response

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

26 aprovado

Current constraintAgent Integration41%

Five readiness layers

Readiness orbit

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

Evidence profile

31 checks recorded

Passed vs. material gaps

Critical

Warnings

Passed

Discovery

6.7 / 13 weighted points

51%

Identity

13.8 / 22 weighted points

63%

Access

28.3 / 31 weighted points

91%

Agent Integration

Current constraint

9.8 / 24 weighted points

41%

User Experience

7.3 / 10 weighted points

73%

Start here

Top Priorities

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

JSON-LD found but no business schema (found: Brand, Corporation, WebSite, WebPage)

Dados Estruturados

Review

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

Actionability

Review

2 buttons with vague labels (e.g., "Click here")

Actionability

Review

Only 49% of images have alt text (48/98)

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

Found 4 JSON-LD structured data blocks

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

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

OpenGraph tags complete (title, description, image)

Meta tags complete (title, description, canonical)

llms.txt found with correct format

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.

API documentation links found

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

2 buttons 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.

HTML semantic structure is well-formed

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

Sufficient text content available for AI extraction

9 social media links found

Schema.org sameAs links found (cross-platform identity)

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, address)

Response time is 3.9s — slower than agents prefer

Lean HTML payload (271KB)

Response is compressed (gzip)

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

Entry URL redirects before serving — adds latency for agents

Author/publisher identity declared in schema

No review/rating schema — agents can't surface your reputation

Partial security headers (HSTS only)

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

Footer/copyright year is current

HTTPS enabled

SSL certificate valid

Privacy policy link found

Terms of service link found

nextgen.com

https://nextgen.com

Readiness orbit

Top Priorities

Findings and fixes

All Findings

Turn audit findings into an agent-ready funnel.

Related AX Scores