AX Audit Report

https://uselemma.ai

August 12, 20261123ms 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 critical

6 warnings

22 passed

Current constraintDiscovery43%

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

Current constraint

5.5 / 13 weighted points

43%

Identity

11.6 / 22 weighted points

53%

Access

27 / 31 weighted points

87%

Agent Integration

13.7 / 24 weighted points

57%

User Experience

7.3 / 10 weighted points

73%

Start here

Top Priorities

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

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

Structured Data

Review

llms.txt found but format is incomplete

Agent Interaction

Review

Missing semantic HTML: <main>, <header>

Content Quality

Review

Only 71% of images have alt text (15/21)

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 1 JSON-LD structured data block

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

Schema has 2 fields — consider adding more for better AI comprehension

OpenGraph tags complete (title, description, image)

Missing meta tags: canonical link

llms.txt found but format is incomplete
Your llms.txt should have: # Title, > description blockquote, ## Sections, and [links](url). See https://llmstxt.org for the full spec.

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/jerryzhang/lemma-demo

Booking/scheduling integration detected

Contact/lead form with an email field is present

CTA buttons have descriptive labels

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

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

Sufficient text content available for AI extraction

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.

Limited contact information — add phone, email, and address

Fast response time (1123ms)

HTML payload is on the heavier side (566KB)

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"

Machine-readable <time> elements found

Sitemap shows content updated within the last 6 months

Footer/copyright year is current

HTTPS enabled

SSL certificate valid

No privacy policy link detected

No terms of service link detected

uselemma.ai

https://uselemma.ai

Readiness orbit

Top Priorities

Findings and fixes

All Findings

Turn audit findings into an agent-ready funnel.

Related AX Scores