Rapport d'audit AX

https://ceridian.com

August 12, 20263926ms 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 critique

7 warnings

22 réussi

Current constraintDiscovery29%

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

Current constraint

3.8 / 13 weighted points

29%

Identity

13.9 / 22 weighted points

63%

Access

27 / 31 weighted points

87%

Agent Integration

8.2 / 24 weighted points

34%

User Experience

6.7 / 10 weighted points

67%

Start here

Top Priorities

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

JSON-LD found but no business schema (found: WebPage)

Données structurées

Review

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

Interaction avec l'agent

Review

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

Actionability

Review

Missing semantic HTML: <nav>, <footer>

Qualité du contenu

Review

Only 78% of images have alt text (43/55)

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

Found 2 JSON-LD structured data blocks

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

Schema has 0 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.

MCP configuration found at /mcp.json, /.mcp.json

API specification found at /openapi.json

Sitemap found but may not be valid XML

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

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

CTA buttons have descriptive labels

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

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

Sufficient text content available for AI extraction

FAQ-like content found but no FAQ schema

Heading levels skip (e.g., h1 directly to h3)

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

Response time is 3.9s — slower than agents prefer

Lean HTML payload (423KB)

Response is compressed (gzip)

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

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"

Footer/copyright year is current

HTTPS enabled

SSL certificate valid

Privacy policy link found

Terms of service link found

ceridian.com

https://ceridian.com

Readiness orbit

Top Priorities

Findings and fixes

All Findings

Turn audit findings into an agent-ready funnel.

Related AX Scores