AX 감사 보고서

https://strivemath.com

August 12, 20261754ms response

62AX score / 100

Needs work

Readiness diagnosis

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

0개 심각

7 warnings

21개 통과

Current constraintAgent Integration26%

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

5.3 / 13 weighted points

40%

Identity

16.3 / 22 weighted points

74%

Access

28 / 31 weighted points

90%

Agent Integration

Current constraint

6.3 / 24 weighted points

26%

User Experience

6 / 10 weighted points

60%

Start here

Top Priorities

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

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

에이전트 상호작용

Review

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

Actionability

Review

1 button with vague labels (e.g., "Click here")

Actionability

Review

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

콘텐츠 품질

Review

Only 58% of images have alt text (21/36)

콘텐츠 품질

Review

Explore the audit

Findings and fixes

에이전트 상호작용

Actionability

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

Business schema found: Product

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

OpenGraph tags complete (title, description, image)

Missing meta tags: canonical link

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.

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.

API documentation links found

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

Contact/lead form with an email field is present

1 button with vague labels (e.g., "Click here")
Replace vague button text like "Click here" or "Submit" with descriptive labels like "Book a Demo" or "Get Started". Agents rely on button text to understand page actions.

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

Only 58% of images have alt text (21/36)
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

Schema.org sameAs links found (cross-platform identity)

Location or rating data found in schema — consider linking to Google Business Profile

Contact information detected (phone, email)

Response time is 1.8s — acceptable, could be faster

Lean HTML payload (197KB)

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

Review/rating schema found — agents can cite social proof

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

No current year found — the site may look stale to agents

HTTPS enabled

SSL certificate valid

Privacy policy link found

No terms of service link detected

strivemath.com

https://strivemath.com

Readiness orbit

Top Priorities

Findings and fixes

All Findings

Turn audit findings into an agent-ready funnel.

Related AX Scores