Scan summary

Needs work

3luxstorage.co.th

ScannedJun 5, 202611:02 AM

CachedRe-check after fixes to refresh the report.

Pages scanned12 / 57

Priority fixes16

Checks passing32 / 66

63/100

Score verdict

Needs focused fixes

Level 2

Findable

9623.9/25 pts

Quotable

7318.3/25 pts

Understandable

7017.5/25 pts

Trustworthy

8220.5/25 pts

AI Readiness

251/12

Technical SEO

747/26

Security

483/10

Performance

—No signal

Production Quality

502/14

Report brief

What stands out

3luxstorage.co.th scored 63/100 on this public readiness scan. 12 pages were sampled from 57 discovered URLs.

Top findings

Needs workContent Depth and DuplicationTechnical SEO
10 page(s) are under 100 words; 2 page(s) are between 100 and 300 words; 1 duplicate-content fingerprint group(s) were detected.
/%E0%B8%94%E0%B8%B9%E0%B8%9A%E0%B8%97%E0%B8%84%E0%B8%A7%E0%B8%B2%E0%B8%A1-73519-1-cantilever-roll-out-racking-%E0%B8%8A%E0%B8%B1%E0%B9%89%E0%B8%99%E0%B8%A7%E0%B8%B2%E0%B8%87%E0%B8%AA%E0%B8%B4%E0%B8%99%E0%B8%84%E0%B9%89%E0%B8%B2%E0%B8%A5%E0%B8%B1%E0%B8%81%E0%B8%A9%E0%B8%93%E0%B8%B0%E0%B8%A2%E0%B8%B2%E0%B8%A7%E0%B8%9E%E0%B8%B4%E0%B9%80%E0%B8%A8%E0%B8%A9-%E0%B8%AA%E0%B8%B2%E0%B8%A1%E0%B8%B2.html, /%E0%B8%94%E0%B8%B9%E0%B8%9A%E0%B8%97%E0%B8%84%E0%B8%A7%E0%B8%B2%E0%B8%A1-73519-cantilever-roll-out-racking-%E0%B8%8A%E0%B8%B1%E0%B9%89%E0%B8%99%E0%B8%A7%E0%B8%B2%E0%B8%87%E0%B8%AA%E0%B8%B4%E0%B8%99%E0%B8%84%E0%B9%89%E0%B8%B2%E0%B8%A5%E0%B8%B1%E0%B8%81%E0%B8%A9%E0%B8%93%E0%B8%B0%E0%B8%A2%E0%B8%B2%E0%B8%A7%E0%B8%9E%E0%B8%B4%E0%B9%80%E0%B8%A8%E0%B8%A9-%E0%B8%AA%E0%B8%B2%E0%B8%A1%E0%B8%B2.html, /%E0%B8%94%E0%B8%B9%E0%B8%9A%E0%B8%97%E0%B8%84%E0%B8%A7%E0%B8%B2%E0%B8%A1-73520-1-mezzanine-floor-%E0%B8%8A%E0%B8%B1%E0%B9%89%E0%B8%99%E0%B8%A5%E0%B8%AD%E0%B8%A2%E0%B9%80%E0%B8%9E%E0%B8%B7%E0%B9%88%E0%B8%AD%E0%B9%80%E0%B8%9E%E0%B8%B4%E0%B9%88%E0%B8%A1%E0%B8%9E%E0%B8%B7%E0%B9%89%E0%B8%99%E0%B8%97%E0%B8%B5%E0%B9%88%E0%B9%83%E0%B8%8A%E0%B9%89%E0%B8%AA%E0%B8%AD%E0%B8%A2%E0%B9%83%E0%B8%99%E0%B8%AD%E0%B8%B2%E0%B8%81%E0%B8%B2%E0%B8%A8.html, /%E0%B8%94%E0%B8%B9%E0%B8%9A%E0%B8%97%E0%B8%84%E0%B8%A7%E0%B8%B2%E0%B8%A1-73520-mezzanine-floor-%E0%B8%8A%E0%B8%B1%E0%B9%89%E0%B8%99%E0%B8%A5%E0%B8%AD%E0%B8%A2%E0%B9%80%E0%B8%9E%E0%B8%B7%E0%B9%88%E0%B8%AD%E0%B9%80%E0%B8%9E%E0%B8%B4%E0%B9%88%E0%B8%A1%E0%B8%9E%E0%B8%B7%E0%B9%89%E0%B8%99%E0%B8%97%E0%B8%B5%E0%B9%88%E0%B9%83%E0%B8%8A%E0%B9%89%E0%B8%AA%E0%B8%AD%E0%B8%A2%E0%B9%83%E0%B8%99%E0%B8%AD%E0%B8%B2%E0%B8%81%E0%B8%B2%E0%B8%A8.html (+8 more)
Needs workMarkdown negotiationAI Readiness
No markdown response for Accept: text/markdown
Needs workAPI CatalogAI Readiness
API catalog is missing valid JSON linkset entries
Needs workContent SignalsSecurity
No Content Signals were detected
Needs workContent-Security-PolicySecurity
Content-Security-Policy is missing

Category context

AI Readiness: 25/100
Technical SEO: 74/100
Security: 48/100
Performance: no signal
Production Quality: 50/100

3luxstorage.co.th/sitemap.xml returned 200 with 53 URLs declared.

Coverage evidence

What this scan proved

12 representative pages were fetched from 57 discovered URLs.

Checked: 12
Found: 57
Mode: Sampled
Non-200: 0

Sitemap sources

3luxstorage.co.th/sitemap.xml200 · 53 URLs declared

Pages checked

Saved-site dashboard

Keep the full public URL map alive.

Save the site when you need URL, sitemap, and robots changes tracked between scans.

URL inventorySource, status, canonical, and indexability for discovered public pages.
Sitemap healthParent indexes, child sitemaps, parse errors, and missing URL coverage.
Robots policyCrawler access, AI bot rules, and implementation-ready robots.txt output.

AI Readiness

Markdown negotiation

Needs work

Goal

Return a markdown version of HTML pages when agents request it via Accept: text/markdown so LLMs ingest your content cleanly.

Issue

No markdown response for Accept: text/markdown

How to fix

Enable Markdown for Agents so requests with `Accept: text/markdown` return a markdown version of your HTML response while HTML stays the default for browsers. Set `Content-Type: text/markdown` on the markdown variant and add `Vary: Accept` so caches differentiate the two representations. Verify with `curl -H "Accept: text/markdown" https://yoursite.com/`.

Resources

Cloudflare Markdown for Agents Skill

Fix guide

API Catalog

Needs work

Goal

Publish an API catalog at /.well-known/api-catalog so agents can discover your API documentation and schemas without crawling.

Issue

API catalog is missing valid JSON linkset entries

How to fix

Create /.well-known/api-catalog returning `application/linkset+json` with a `linkset` array. Each entry should include an `anchor` URL for the API and link relations like `service-desc` (OpenAPI spec), `service-doc` (human docs), and `status` (health endpoint). See RFC 9727 Appendix A for examples and RFC 9264 for the linkset format.

Resources

RFC 9727 Skill

OAuth discovery

Needs work

Goal

Expose OAuth/OIDC discovery metadata so agents can authenticate against your APIs programmatically.

Issue

OAuth or OIDC discovery metadata is missing or incomplete

How to fix

If your site has protected APIs, publish /.well-known/openid-configuration (for OpenID Connect) or /.well-known/oauth-authorization-server (for OAuth 2.0) with `issuer`, `authorization_endpoint`, `token_endpoint`, `jwks_uri`, and `grant_types_supported`. This lets agents discover how to authenticate without parsing your docs.

Resources

RFC 8414 Skill

OpenAPI Discovery

Needs work

Goal

Publish a discoverable OpenAPI 3.x document so agents and developers can understand your public HTTP API without scraping docs.

Issue

OpenAPI document candidate is not parseable

How to fix

Publish a valid OpenAPI 3.x document at /openapi.json or /.well-known/openapi.json, and advertise it with a `Link: <...>; rel="service-desc"` header or from /.well-known/api-catalog. Include `openapi`, `info.title`, `info.version`, `servers`, and `paths`; give operations stable `operationId` and `summary` values so agents can choose the right endpoint safely.

Resources

OpenAPI Specification Skill

OAuth Protected Resource

Needs work

Goal

Publish OAuth Protected Resource metadata so agents know which auth servers issue valid tokens for your APIs.

Issue

OAuth protected resource metadata exists but is missing a valid resource URL

How to fix

Publish /.well-known/oauth-protected-resource (per RFC 9728) with your `resource` identifier, `authorization_servers` (the list of OAuth/OIDC issuer URLs that can issue tokens for this resource), and `scopes_supported`. This tells agents which auth server to obtain access tokens from and which scopes to request.

Resources

RFC 9728 Skill

A2A Agent Card

Needs work

Goal

Publish an A2A Agent Card so other agents can discover your agent-to-agent capabilities and supported interfaces.

Issue

A2A Agent Card exists but is not valid JSON

How to fix

Publish /.well-known/agent-card.json describing your agent: `name`, `description`, `endpoints`, `version`, and a complete `supportedInterfaces` array with the protocols and message types you accept. Include a `capabilities` block so calling agents can negotiate, and keep the URL stable across deploys — agents cache discovery responses.

Resources

A2A protocol Skill

Agent Skills

Needs work

Goal

Publish a discoverable agent-skills index so AI agents can find and load your structured skill bundles.

Issue

Agent Skills index exists but is not valid JSON

How to fix

Publish a skills discovery index at /.well-known/agent-skills/index.json (per the Agent Skills Discovery RFC v0.2.0) with a `$schema` field and a `skills` array. Each entry should have `name`, `type`, `description`, `url`, and a `sha256` digest of the SKILL.md so agents can verify integrity. Make sure each `url` resolves to a reachable SKILL.md.

Resources

Agent Skills Skill

MCP Server Card

Needs work

Goal

Serve an MCP Server Card so agents can discover your Model Context Protocol surface and connect with the right capabilities.

Issue

MCP server card exists but is not valid JSON

How to fix

Serve an MCP Server Card at /.well-known/mcp/server-card.json with `serverInfo` (name, version), the transport endpoint URL, and the `capabilities` you support. Accept /.well-known/mcp.json as a fallback for clients on the legacy path. The schema is being standardized — track the active proposal at github.com/modelcontextprotocol/modelcontextprotocol/pull/2127.

Resources

Model Context Protocol Skill

Fix guide

AI bot rules

Watch

Goal

Set robots.txt rules for AI search, user-triggered browsing, and training crawlers that match your content policy.

Issue

AI search/user crawlers are allowed, while one or more training/data-use crawlers are blocked as a policy choice

How to fix

Add explicit User-agent entries for AI crawlers — GPTBot, OAI-SearchBot, ClaudeBot, Claude-Web, Google-Extended, PerplexityBot, CCBot — with Allow/Disallow rules that reflect your policy. Decide per-bot whether you want training access, search indexing, or both, and document the choice in source so it doesn't silently drift in future edits.

Resources

OpenAI crawlers Anthropic crawlers Perplexity crawlers Google-Extended Skill

Fix guide

llms.txt Bonus

Watch

Issue

llms.txt is present, but one optional LLM guidance file is served with the wrong content type.

How to fix

If you publish `/llms.txt`, serve it as plain text or markdown and link only to important public docs/resources. Treat it as an optional discovery aid, not a guaranteed ranking factor, and do not expose private/internal URLs.

Resources

llms.txt

Fix guide

WebMCP

Info

Goal

Expose in-page tools to AI agents via the WebMCP browser API so agents can act on your site directly.

Result

No in-page agent tool surface was detected, so WebMCP may not apply

How to fix

Implement the WebMCP API by calling `navigator.modelContext.provideContext()` with tool definitions exposing your site's key actions to AI agents. Each tool needs `name`, `description`, `inputSchema` (JSON Schema), and an `execute` callback. Register tools at the points an agent could meaningfully use them — after page hydration, on route changes, or when permission state changes.

Resources

WebMCP Skill

Technical SEO

Content Depth and Duplication

Needs work

Goal

Each indexable page carries enough unique, substantive content to merit indexing on its own without overlapping siblings.

Issue

10 page(s) are under 100 words; 2 page(s) are between 100 and 300 words; 1 duplicate-content fingerprint group(s) were detected.

How to fix

Audit indexable pages for substantive, unique content — at minimum a few hundred words of original copy that delivers on the title and description. Consolidate near-duplicate pages with canonical tags or merge them into a single richer page. Don't ship placeholder "Coming soon" pages to production indexable URLs.

Affected pages (12)

Resources

Google snippets

Heading Structure

Needs work

Goal

Each page has a clear heading hierarchy with one h1 and properly nested h2/h3 sections so structure conveys meaning to readers and crawlers.

Issue

12 H1 issue(s) and 12 skipped heading hierarchy warning(s) were detected.

How to fix

Use exactly one `<h1>` per page that conveys the page's subject, then nest `<h2>` sections beneath it and `<h3>` for sub-sections — never skip levels (h1 → h3) or wrap headings in `<div>` for styling. Headings communicate document structure to assistive tech and crawlers; write them as outline entries, not as styled text.

Affected pages (12)

Resources

Google title links

Link headers

Needs work

Goal

Expose Link response headers so agents can discover related resources (API catalog, skills, agent card) without parsing HTML.

Issue

No discovery-oriented Link headers were detected on the homepage response

How to fix

Add Link response headers on your homepage and key API endpoints pointing agents to discovery documents. For example: `Link: </.well-known/api-catalog>; rel="api-catalog"` for your API catalog, or `Link: </docs/api>; rel="service-doc"` for documentation. See RFC 8288 for the format and the IANA Link Relations registry for valid `rel` values.

Resources

RFC 8288 Skill

Mixed Content

Needs work

Goal

HTTPS pages only reference HTTPS subresources so browsers do not block assets or downgrade user trust.

Issue

12 insecure http:// subresource reference(s) were found on HTTPS pages.

How to fix

Replace every `http://` script, stylesheet, image, iframe, media, and embedded resource URL on HTTPS pages with an `https://` URL, or serve the asset from the same secure origin. Mixed content can be blocked by browsers and weakens security signals.

Affected pages (11)

Resources

Google link best practices

Social Preview / Open Graph

Needs work

Goal

Pages expose complete Open Graph and Twitter Card metadata so they preview cleanly when shared on social, in chat, or by AI assistants.

Issue

1 blocking social preview issue(s) and 24 warning(s) were detected.

How to fix

On shareable pages, add Open Graph and Twitter Card metadata in the head: `og:title`, `og:description`, `og:image` (1200×630 minimum), `og:url`, `og:type`, plus `twitter:card` set to `summary_large_image`. Make the OG content match the visible page so previews aren't misleading, and use a real image URL with stable dimensions so social platforms cache reliably.

Affected pages (12)

Resources

Open Graph protocol Google snippets

Fix guide

Internal Link Quality

Watch

Goal

Internal links use descriptive anchor text and form a reachable graph so crawlers, readers, and AI agents can navigate context.

Issue

280 link crawlability or anchor-text warning(s) were detected.

How to fix

Use real `<a href="...">` elements for navigation — never `<div onclick>` or button-styled spans, which crawlers can't follow. Write descriptive anchor text that summarizes the destination (avoid "click here", "read more", or naked URLs). Keep important pages within ~3 clicks of the homepage so crawl depth doesn't starve them.

Affected pages (12)

Resources

Google link best practices

Content Freshness

Watch

Goal

Article-like and substantial pages expose reliable freshness signals so answer engines know whether the content is current.

Issue

0 content page(s) have no reliable date signal and 2 have a newest signal older than six months.

How to fix

Add truthful freshness metadata only where it reflects a real content update: JSON-LD dateModified/datePublished, article modified-time meta tags, a visible updated or reviewed date, or sitemap lastmod. Do not stamp every page with build time unless the visible content actually changed.

Affected pages (2)

Resources

Google sitemap lastmod Sitemaps protocol Google structured data

Image SEO and Accessibility

Watch

Goal

Images carry meaningful alt text and reasonable dimensions so the page is accessible, indexable, and renders without layout shift.

Issue

84 image metadata or crawlability warning(s) were detected.

How to fix

Use `<img src="...">` (or a `srcset`) for crawlable images, never CSS `background-image` for content imagery. Write descriptive `alt` text on meaningful images and `alt=""` on purely decorative ones. Set explicit `width` and `height` attributes to reserve layout space, and avoid `loading="lazy"` on above-the-fold or LCP images so they aren't deferred.

Affected pages (12)

Resources

Google lazy loading guidance

Meta Description Quality

Watch

Goal

Every indexable page has a single meta description (50-160 chars) that previews the page accurately for search and social.

Issue

0 sampled page(s) have missing or multiple meta descriptions; 2 description quality warning(s) were detected.

How to fix

Add one `<meta name="description">` tag to each important indexable page — 50–180 characters of distinct, human-readable copy that previews the page accurately. Avoid copying the title, padding with keywords, or duplicating descriptions across pages; search engines either rewrite duplicates or skip them entirely.

Affected pages (1)

/%E0%B8%94%E0%B8%B9%E0%B8%AB%E0%B8%99%E0%B9%89%E0%B8%B2-23485-%E0%B9%81%E0%B8%9C%E0%B8%99%E0%B8%9C%E0%B8%B1%E0%B8%87%E0%B9%80%E0%B8%A7%E0%B9%87%E0%B8%9A%E0%B9%84%E0%B8%8B%E0%B8%95%E0%B9%8C.html

Resources

Google snippets

Title Quality

Watch

Goal

Every indexable page has exactly one descriptive, unique title that summarizes the page in 50-60 characters.

Issue

0 sampled page(s) have missing or multiple titles; 10 title quality warning(s) were detected.

How to fix

Add exactly one `<title>` tag to every indexable page, ideally 50–60 characters. Make each title descriptive and unique across the site so search engines can disambiguate them. For sectional pages, include the brand as a suffix (`Page Topic | Brand`) so social previews still attribute correctly.

Affected pages (6)

Resources

Google title links

Canonical Hygiene

Watch

Goal

Each indexable page declares one canonical URL pointing to itself or the definitive original, so search engines consolidate ranking signals.

Issue

0 canonical error(s) and 4 canonical warning(s) were detected in the sample.

How to fix

Add exactly one `<link rel="canonical" href="...">` per indexable page in the document head, with an absolute URL pointing to the preferred version (after redirects, with the right protocol and trailing-slash policy). Self-canonical is fine for the original; cross-canonical only when consolidating duplicates. Never canonicalize to a noindexed or 404 page.

Affected pages (4)

Resources

Google canonicals

Content Readability

Watch

Goal

Public page copy is readable enough for visitors, assistants, and crawlers to summarize without wading through oversized sentences.

Issue

1 sampled page(s) have unusually long sentence or word patterns.

How to fix

Rewrite dense copy into shorter sentences and paragraphs with concrete nouns, direct verbs, and clear section breaks. Keep important explanatory pages easy to scan before adding more keywords or decorative copy.

Affected pages (1)

3luxstorage.co.th

Resources

Google snippets

Keyword Stuffing Risk

Watch

Goal

Page copy reads naturally without repeating target keywords beyond useful frequency — informative for readers, not gamed for crawlers.

Issue

2 sampled page(s) have repeated phrase patterns that may read like keyword stuffing.

How to fix

Re-read pages flagged for repetition and rewrite for human readers — the copy should explain the topic naturally, not chant the target keyword. Don't aim for a fixed keyword density; modern search engines and AI agents penalize unnatural repetition more than they reward it. Variety in vocabulary and sentence structure helps both ranking and comprehension.

Affected pages (2)

Resources

Google spam policies

SEO-Friendly URL

Watch

Goal

Public URLs are stable, readable, and canonical enough for search engines, humans, and AI agents to understand without query noise.

Issue

11 sampled URL(s) use patterns that are harder to read, share, or canonicalize.

How to fix

Prefer lowercase, hyphen-separated path URLs with stable nouns, and keep tracking parameters out of canonical indexable URLs. Avoid opaque IDs, excessive query parameters, file-extension routes for HTML pages, and uppercase path variants that create duplicate crawl surfaces.

Affected pages (11)

Resources

Google canonicals

External Citation Links

Observed

Result

No article-like content pages requiring external citations were detected in the sample.

How to fix

Add outbound citations only where the page makes claims that benefit from primary sources, standards, or official documentation.

Resources

Google link best practices

FAQ Content

Observed

Result

No visible FAQ-style questions or FAQPage JSON-LD were detected.

How to fix

Add visible question-and-answer sections only where they genuinely help users make a decision or complete a task.

Resources

Google structured data

Hreflang Annotations

Observed

Goal

Pages declare language and region alternates with hreflang annotations when content varies by locale, so search engines route the right version to the right reader.

Result

No hreflang annotations were detected in the sampled pages.

How to fix

On each localized page, add `<link rel="alternate" hreflang="...">` tags pointing to every language/region variant (including a self-reference). Use valid IANA language-region codes (e.g. `en-US`, `fr-FR`), absolute `href` URLs, and one `hreflang="x-default"` entry pointing to the version for unspecified locales. Each variant must reciprocally link back.

Resources

Google localized versions

Page and Server Snapshot

Observed

Goal

Lightweight server and document metrics from the sampled homepage are captured every scan so drift in HTML size, server stack, or DOM complexity is observable across reports.

Result

Captured lightweight server and document metrics from the sampled homepage.

Structured Data

Observed

Goal

Pages publish JSON-LD structured data so search engines and AI agents can extract entities, products, FAQs, and offers reliably.

Result

No JSON-LD structured data was detected in the sampled pages.

How to fix

Embed JSON-LD `<script type="application/ld+json">` blocks in the head describing the page's primary entity — Article, Product, FAQPage, Organization, etc. — using schema.org types and required fields per Google's structured data guidelines. Validate with the Rich Results Test before shipping, and keep the JSON strictly parseable (no trailing commas, no comments).

Resources

Google structured data

Security

Content Signals

Needs work

Goal

Declare AI-usage preferences via Content-Signal directives in robots.txt (ai-train, search, ai-input).

Issue

No Content Signals were detected

How to fix

Add Content-Signal directives to your robots.txt declaring preferences for ai-train, search, and ai-input. Example: `Content-Signal: ai-train=no, search=yes, ai-input=no`. Pair with explicit User-agent blocks so each signal targets specific bots, and review quarterly as the spec evolves.

Resources

Content Signals Skill

Content-Security-Policy

Needs work

Issue

Content-Security-Policy is missing

How to fix

Publish a baseline Content-Security-Policy for the site shell.

HTTP Observatory

Needs work

Issue

HTTP Observatory grade D with score 35.

How to fix

Tighten response headers and HTTP posture where Observatory reports gaps.

Resources

MDN HTTP Observatory

Web Bot Auth

Needs work

Goal

Identify your own bot traffic with Web Bot Auth signed requests so receiving sites can verify and trust them.

Issue

Web Bot Auth directory exists but does not contain valid signing keys

How to fix

Publish a JWKS at /.well-known/http-message-signatures-directory containing the public keys you use to sign outgoing bot requests, so receiving sites can verify those requests via HTTP Message Signatures (RFC 9421). Rotate keys on a regular cadence and keep the previous key in the JWKS until in-flight requests have aged out.

Resources

Web Bot Auth HTTP Message Signatures Directory Skill

Cloudflare Challenge Signals

Observed

Result

No Cloudflare Challenge Page marker was detected on the homepage response.

Resources

Detect a Challenge Page response

DNSSEC Signals

Observed

Result

No DNSSEC DS or DNSKEY records were detected for the DNS zone.

Resources

Cloudflare DNSSEC

Domain Trust

Unavailable

Issue

Domain registration data is temporarily unavailable.

Performance

Cloudflare Cache Signals

Observed

Result

Cloudflare reported cache status DYNAMIC.

Resources

Cloudflare cache responses

HTTPS/SVCB Records

Observed

Result

No HTTPS/SVCB DNS records were detected for the scanned host or zone.

Resources

Cloudflare ECH Protocol Cloudflare HTTP/3

PageSpeed Insights

Unavailable

PageSpeed Insights returned no Lighthouse result.

PageSpeed sometimes throttles or skips a URL. The miss is cached on our side for ~15 minutes, so refreshing this report often returns the same answer. A fresh scan is the surest fix.

What this means

The URL might be unsupported (e.g. a single-page route Lighthouse can't reach).
Google could be rate-limiting our project key — usually clears within a few minutes.
The page returned a redirect chain or a non-200 that Lighthouse refused to score.

Resources

PageSpeed Insights API

Run fresh scan

CrUX Field Data

No field data

Chrome doesn't have enough real-user traffic for this site to publish field metrics yet — this isn't a failure on your side.

The Chrome User Experience Report only covers public origins with enough opted-in Chrome traffic. Smaller or newly launched sites typically appear after they accumulate sufficient sample size. Lab performance (PageSpeed Insights) below stays a useful proxy in the meantime.

Resources

CrUX eligibility criteria CrUX API

Production Quality

Discovery Link Headers

Needs work

Issue

Homepage Link headers do not advertise agent-useful discovery artifacts

How to fix

Expose Link headers for api-catalog, service-desc, agent-skills, or related discovery artifacts.

Duplicate Titles

Needs work

Issue

4 duplicate page titles were detected in the sample

How to fix

Make page titles unique across important templates.

ACP

Needs work

Goal

Publish Agentic Commerce Protocol discovery so agents can transact with your commerce surfaces without scraping.

Issue

No ACP discovery markers were detected

How to fix

Serve /.well-known/acp.json at the origin root with `protocol.name` set to `"acp"`, the `protocol.version`, `api_base_url`, supported transports, and `capabilities.services`. Agents can then discover your ACP implementation without first creating a checkout session.

Resources

ACP Skill

MPP

Needs work

Goal

Publish Machine Payment Protocol metadata so agents can discover paid endpoints in your API.

Issue

No MPP discovery markers were detected

How to fix

Publish an OpenAPI document at /openapi.json with `x-payment-info` extensions on payable operations. Each operation should declare `intent` (charge or session), `method` (tempo, stripe, lightning, card), `amount`, and `currency`. Use the MPP SDK (`mppx` for TypeScript, `pympp` for Python) with framework middleware for Hono, Express, Next.js, or Elysia to handle the payment flow.

Resources

MPP Skill

UCP

Needs work

Goal

Expose Universal Commerce Protocol metadata so agents can transact for content or services through a standard interface.

Issue

No UCP discovery markers were detected

How to fix

Serve /.well-known/ucp with your protocol version, declared `services`, supported `capabilities`, and reachable `endpoints`. Make sure any spec URLs and referenced JSON Schemas resolve so agents can validate against them at discovery time.

Resources

UCP Skill

x402

Needs work

Goal

Support x402-style HTTP 402 payment flows so agents can pay for API access machine-to-machine.

Issue

No x402 discovery markers were detected

How to fix

Add x402 payment middleware to your API routes so AI agents can pay for access via HTTP. Use `@x402/express`, `@x402/hono`, or `@x402/next` middleware with a facilitator URL and wallet address. Protected routes will return HTTP 402 with payment requirements that agents can fulfill automatically.

Resources

x402 Skill

Scan Coverage

Observed

Result

Scanned 12 representative pages out of 57.

Cloudflare Error Diagnostics

Observed

Result

No Cloudflare-generated error diagnostics were detected on the homepage response.

Resources

Cloudflare error diagnostic headers

Cloudflare Product Signals

Observed

Result

No Cloudflare product beacons were detected in the homepage response.

Resources

Cloudflare Web Analytics Cloudflare Turnstile

Cloudflare Trace Endpoint

Observed

Result

The Cloudflare trace endpoint was not available for this origin.

Resources

/cdn-cgi/trace

DNS Service Discovery

Observed

Result

No recognizable third-party DNS service signals were detected.

Resources

Cloudflare DNS over HTTPS JSON

HTML Validation

Unavailable

Issue

HTML validation is temporarily unavailable.