AX 감사 보고서

https://archicad.com

August 12, 20266233ms response

61AX 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 constraintAgent Integration30%

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

4.9 / 13 weighted points

38%

Identity

13.4 / 22 weighted points

61%

Access

27.7 / 31 weighted points

89%

Agent Integration

Current constraint

7.3 / 24 weighted points

30%

User Experience

7.3 / 10 weighted points

73%

Start here

Top Priorities

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

No robots.txt file found

크롤 가능성

Review

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

에이전트 상호작용

Review

No sitemap.xml found

에이전트 상호작용

Review

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

Actionability

Review

Only 59% of images have alt text (42/71)

콘텐츠 품질

Review

Explore the audit

Findings and fixes

크롤 가능성

Performance

보안 및 신뢰

All Findings

No robots.txt file found
Create a robots.txt file at your site root. For AI-friendly access:

User-agent: GPTBot
Allow: /

User-agent: ClaudeBot
Allow: /

User-agent: Google-Extended
Allow: /

Page returns HTTP 200

Page content available without JavaScript

No CAPTCHA or bot protection detected

Found 2 JSON-LD structured data blocks

Business schema found: Organization

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

OpenGraph tags complete (title, description, image)

Meta tags complete (title, description, canonical)

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

No sitemap.xml found
Create a /sitemap.xml file listing all your important pages. Also declare it in robots.txt:
Sitemap: https://yoursite.com/sitemap.xml

RSS/Atom feed detected

Schema.org potentialAction defined — agents know what actions are available

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 59% of images have alt text (42/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-like content found but no FAQ schema

Heading levels skip (e.g., h1 directly to h3)

5 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

Slow response (6.2s) — agents may time out
Speed up your time-to-first-byte (caching, a CDN, lighter server work). Agents enforce short timeouts and abandon slow pages.

Lean HTML payload (298KB)

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

No HSTS or CSP headers detected
Add Strict-Transport-Security and Content-Security-Policy headers — they signal a well-maintained, trustworthy origin.

Content dates (dateModified/datePublished) present in schema

Footer/copyright year is current

HTTPS enabled

SSL certificate valid

Privacy policy link found

Terms of service link found

archicad.com

https://archicad.com

Readiness orbit

Top Priorities

Findings and fixes

All Findings

Turn audit findings into an agent-ready funnel.

Related AX Scores