Informe de auditoría AX

https://cyberdesk.io

August 12, 20262152ms response

52AX score / 100

Needs work

Readiness diagnosis

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

1 crítico

5 warnings

20 aprobado

Current constraintIdentity9%

Five readiness layers

Readiness orbit

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

Evidence profile

26 checks recorded

Passed vs. material gaps

Critical

Warnings

Passed

Discovery

3.5 / 13 weighted points

27%

Identity

Current constraint

2.0 / 22 weighted points

Access

29 / 31 weighted points

94%

Agent Integration

10.5 / 24 weighted points

44%

User Experience

7.3 / 10 weighted points

73%

Start here

Top Priorities

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

No JSON-LD structured data found

Datos estructurados

Review

Missing OpenGraph tags: og:title, og:description, og:image

Datos estructurados

Review

Missing semantic HTML: <main>

Calidad del contenido

Review

Only 67% of images have alt text (4/6)

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

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>

Missing OpenGraph tags: og:title, og:description, og:image
<meta property="og:title" content="..." />
<meta property="og:description" content="..." />
<meta property="og:image" content="..." />

Missing meta tags: canonical link

llms.txt found but format is incorrect

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

RSS/Atom feed detected

Embedded conversion target declared — agents can act on the funnel's conversion URL
Conversion URL: https://cal.com/mahmoud-al-madi-klrs5s/cyberdesk-intro

Booking/scheduling integration detected

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

CTA buttons have descriptive labels

Missing semantic HTML: <main>
Add missing semantic HTML elements: <main>

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

Sufficient text content available for AI extraction

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

Lean HTML payload (82KB)

Response is compressed (br)

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

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

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

cyberdesk.io

https://cyberdesk.io

Readiness orbit

Top Priorities

Findings and fixes

All Findings

Turn audit findings into an agent-ready funnel.

Related AX Scores