AX 감사 보고서

https://upstream.do

August 12, 20261269ms response

40AX score / 100

미흡

Readiness diagnosis

This site is not ready for AI agents yet. Resolve the critical access and understanding gaps first.

1개 심각

5 warnings

16개 통과

Current constraintAgent Integration9%

Five readiness layers

Readiness orbit

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

Evidence profile

22 checks recorded

Passed vs. material gaps

Critical

Warnings

Passed

Discovery

3.2 / 13 weighted points

25%

Identity

4.6 / 22 weighted points

21%

Access

26.7 / 31 weighted points

86%

Agent Integration

Current constraint

2.3 / 24 weighted points

User Experience

3.3 / 10 weighted points

33%

Start here

Top Priorities

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

No JSON-LD structured data found

구조화된 데이터

Review

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

Missing semantic HTML: <main>, <nav>, <header>, multiple <h1> tags (use only one)

콘텐츠 품질

Review

Only 5% of images have alt text (12/262)

콘텐츠 품질

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

No JSON-LD structured data found
Add JSON-LD structured data to your page <head>:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Your Business",
  "url": "https://yoursite.com",
  "description": "What your business does"
}
</script>

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.

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

Direct contact link found, but no on-page form for agents

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

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

Sufficient text content available for AI extraction

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

No 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.

Contact information detected (phone, email)

3 industry directory links found

Fast response time (1269ms)

Very large HTML payload (2463KB) — agents may truncate it
Trim your initial HTML payload — defer non-critical markup and avoid inlining large data blobs. Agents truncate very large documents.

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"

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

upstream.do

https://upstream.do

Readiness orbit

Top Priorities

Findings and fixes

All Findings

Turn audit findings into an agent-ready funnel.

Related AX Scores