AX Audit Report

https://remote.com

August 12, 2026641ms response

70AX score / 100

Good

Readiness diagnosis

This site is mostly ready for AI agents. A few focused improvements can close the remaining gaps.

0 critical

6 warnings

30 passed

Current constraintAgent Integration42%

Five readiness layers

Readiness orbit

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

Evidence profile

36 checks recorded

Passed vs. material gaps

Critical

Warnings

Passed

Discovery

5.9 / 13 weighted points

45%

Identity

13.9 / 22 weighted points

63%

Access

30.3 / 31 weighted points

98%

Agent Integration

Current constraint

10.2 / 24 weighted points

42%

User Experience

9.3 / 10 weighted points

93%

Start here

Top Priorities

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

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

Structured Data

Review

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

Actionability

Review

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

Actionability

Review

Only 79% of images have alt text (56/71)

Content Quality

Review

Explore the audit

Findings and fixes

Structured Data

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

JSON-LD found but no business schema (found: FAQPage, Review, Review, Review, Review)
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)

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

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

HTML semantic structure is well-formed

Only 79% of images have alt text (56/71)
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

4 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.

Limited contact information — add phone, email, and address

1 industry directory link found

Fast response time (641ms)

HTML payload is on the heavier side (669KB)

Response is compressed (gzip)

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

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"

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

remote.com

https://remote.com

Readiness orbit

Top Priorities

Findings and fixes

All Findings

Turn audit findings into an agent-ready funnel.

Related AX Scores