AX監査レポート

https://weekday.works

August 12, 20261691ms 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件

7 warnings

合格 23件

Current constraintDiscovery40%

Five readiness layers

Readiness orbit

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

Evidence profile

30 checks recorded

Passed vs. material gaps

Critical

Warnings

Passed

Discovery

Current constraint

5.3 / 13 weighted points

40%

Identity

12.0 / 22 weighted points

54%

Access

29 / 31 weighted points

94%

Agent Integration

13.0 / 24 weighted points

54%

User Experience

6 / 10 weighted points

60%

Start here

Top Priorities

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

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

構造化データ

Review

llms.txt found but format is incomplete

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

Review

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

コンテンツ品質

Review

Only 0% of images have alt text (0/74)

コンテンツ品質

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

Missing meta tags: canonical link

JSON-LD schema missing @context or @type

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

Embedded conversion target declared — agents can act on the funnel's conversion URL
Conversion URL: https://calendly.com/parasar-weekday/30min-1?utm_source=website&utm_medium=website

Booking/scheduling integration detected

Checkout path found, but no machine-readable prices (Offer schema)

A form is present but has no obvious email field

CTA buttons have descriptive labels

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

Only 0% of images have alt text (0/74)
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

12 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

Response time is 1.7s — acceptable, could be faster

Lean HTML payload (90KB)

Response is compressed (gzip)

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

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"

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

Terms of service link found

weekday.works

https://weekday.works

Readiness orbit

Top Priorities

Findings and fixes

All Findings

Turn audit findings into an agent-ready funnel.

Related AX Scores