AX監査レポート

https://talkspace.com

August 12, 20261298ms response

68AX score / 100

Needs work

Readiness diagnosis

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

重大 0件

5 warnings

合格 26件

Current constraintAgent Integration33%

Five readiness layers

Readiness orbit

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

Evidence profile

31 checks recorded

Passed vs. material gaps

Critical

Warnings

Passed

Discovery

5.6 / 13 weighted points

43%

Identity

15.8 / 22 weighted points

72%

Access

29.7 / 31 weighted points

96%

Agent Integration

Current constraint

7.8 / 24 weighted points

33%

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: MedicalOrganization)

構造化データ

Review

llms.txt found but format is incomplete

エージェントインタラクション

Review

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

Actionability

Review

Missing semantic HTML: <footer>, multiple <h1> tags (use only one)

コンテンツ品質

Review

Explore the audit

Findings and fixes

構造化データ

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: MedicalOrganization)
Add a business-specific schema type (LocalBusiness, Organization, Product, Service) to help AI agents understand what your business offers.

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

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

CTA buttons have descriptive labels

Missing semantic HTML: <footer>, multiple <h1> tags (use only one)
Add missing semantic HTML elements: <footer>, multiple <h1> tags (use only one)

100% of images have alt text (78/78)

Sufficient text content available for AI extraction

FAQ schema detected

4 social media links found

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

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 (1298ms)

Lean HTML payload (337KB)

Response is compressed (gzip)

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

1 authoritative citation (.gov/.edu/Wikipedia)

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"

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

talkspace.com

https://talkspace.com

Readiness orbit

Top Priorities

Findings and fixes

All Findings

Turn audit findings into an agent-ready funnel.

Related AX Scores