amplifyed.io

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

No markdown response for Accept: text/markdown

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/`.

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

No agent-to-agent surface was detected, so A2A agent-card discovery may not apply

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.

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

No agent skill surface was detected, so agent-skills discovery may not apply

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.

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

No public API surface was detected, so API catalog discovery may not apply

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.

No llms.txt file was detected; this emerging convention is optional and does not reduce the base score.

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.

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

No MCP server surface was detected, so MCP server-card discovery may not apply

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.

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

No public login, signup, or protected API surface was detected, so OAuth/OIDC discovery may not apply

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.

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

No protected API surface was detected, so OAuth protected-resource metadata may not apply

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.

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

No public API surface was detected, so OpenAPI discovery may not apply

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.

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

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

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.

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

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

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.

• /new-home-page
• /blog
• /contact
• /our-work
• /podcast-episodes

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

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

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.

• /new-home-page
• /podcast-episodes
• amplifyed.io
• /about
• /privacy-policy

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

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

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.

• /about
• /blog
• /contact
• /new-home-page
• /our-work

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

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

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.

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

12 blocking social preview issue(s) and 14 warning(s) were detected.

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.

• amplifyed.io
• /about
• /blog
• /case-studies/castra
• /contact

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

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

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.

• amplifyed.io
• /about
• /blog
• /case-studies/castra
• /contact

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

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

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.

• amplifyed.io
• /about
• /blog
• /case-studies/castra
• /contact

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

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

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.

• amplifyed.io
• /about
• /blog
• /case-studies/castra
• /contact

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

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

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.

• /blog

FAQPage schema is treated as a bonus only when it matches visible question-and-answer content.

Visible question headings were detected without matching FAQPage JSON-LD.

Keep FAQ sections visible and useful. Only add FAQPage JSON-LD when the same questions and answers are present in the page body; remove FAQ schema for hidden, fabricated, or irrelevant questions.

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.

No hreflang annotations were detected in the sampled pages.

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.

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.

Captured lightweight server and document metrics from the sampled homepage.

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

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

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

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

No Content Signals were detected

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.

Content-Security-Policy is missing

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

HTTP Observatory grade C- with score 45.

Tighten response headers and HTTP posture where Observatory reports gaps.

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

Web Bot Auth HTTP Message Signatures directory is missing

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.

X-Content-Type-Options is not set to nosniff

Set X-Content-Type-Options: nosniff.

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

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

Domain registration data is temporarily unavailable.

Cloudflare reported cache status DYNAMIC.

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

Homepage Link headers do not advertise agent-useful discovery artifacts

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

Scanned 12 representative pages out of 52.

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

No payable API surface was detected, so ACP discovery may not apply

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.

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

No Cloudflare product beacons were detected in the homepage response.

The Cloudflare trace endpoint was not available for this origin.

Detected 4 public DNS/service signal(s).

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

No payable API surface was detected, so MPP discovery may not apply

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.

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

No payable API surface was detected, so UCP discovery may not apply

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.

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

No payable API surface was detected, so x402 discovery may not apply

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.

HTML validation is temporarily unavailable.