Rapport d'audit AX

https://dataglade.com

August 12, 20261588ms response

53AX score / 100

Needs work

Readiness diagnosis

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

1 critique

6 warnings

21 réussi

Current constraintIdentity6%

Five readiness layers

Readiness orbit

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

Evidence profile

28 checks recorded

Passed vs. material gaps

Critical

Warnings

Passed

Discovery

3.2 / 13 weighted points

25%

Identity

Current constraint

1.3 / 22 weighted points

Access

29.7 / 31 weighted points

96%

Agent Integration

13.8 / 24 weighted points

57%

User Experience

4.7 / 10 weighted points

47%

Start here

Top Priorities

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

No JSON-LD structured data found

Données structurées

Review

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

Données structurées

Review

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

Qualité du contenu

Review

Only 1% of images have alt text (1/89)

Qualité du contenu

Review

Explore the audit

Findings and fixes

Données structurées

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

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

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

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

API documentation links found

API specification found at /openapi.json

Sitemap found but may not be valid XML

Embedded conversion target declared — agents can act on the funnel's conversion URL
Conversion URL: https://calendly.com/ashrai/dataglade-introduction

Booking/scheduling integration detected

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

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

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

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

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

Lean HTML payload (79KB)

Response is compressed (gzip)

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

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"

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

dataglade.com

https://dataglade.com

Readiness orbit

Top Priorities

Findings and fixes

All Findings

Turn audit findings into an agent-ready funnel.

Related AX Scores