Informe de auditoría AX

https://circlemedical.com

August 12, 20262481ms response

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

24 aprobado

Current constraintAgent Integration34%

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

5.4 / 13 weighted points

42%

Identity

15.6 / 22 weighted points

71%

Access

27 / 31 weighted points

87%

Agent Integration

Current constraint

8.3 / 24 weighted points

34%

User Experience

8.7 / 10 weighted points

87%

Start here

Top Priorities

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

JSON-LD found but no business schema (found: MedicalOrganization, WebSite, FAQPage)

Datos estructurados

Review

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

Interacción con el agente

Review

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

Actionability

Review

Missing semantic HTML: <header>

Calidad del contenido

Review

Only 77% of images have alt text (101/131)

Calidad del contenido

Review

Explore the audit

Findings and fixes

Datos estructurados

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 3 JSON-LD structured data blocks

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

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.

llms-full.txt also found (two-file mode)

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

Schema.org potentialAction defined — agents know what actions are available

Booking/scheduling integration detected

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

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

Sufficient text content available for AI extraction

FAQ schema detected

3 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 2.5s — acceptable, could be faster

HTML payload is on the heavier side (846KB)

Response is compressed (br)

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

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

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"

Footer/copyright year is current

HTTPS enabled

SSL certificate valid

Privacy policy link found

Terms of service link found

circlemedical.com

https://circlemedical.com

Readiness orbit

Top Priorities

Findings and fixes

All Findings

Turn audit findings into an agent-ready funnel.

Related AX Scores