modeta.cz

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

A2A Agent Card is missing

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.

Agent Skills index is missing

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.

API catalog is missing

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.

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

MCP server card is missing

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.

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

OpenAPI document is missing

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.

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

OAuth protected resource metadata is missing

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.

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

No WebMCP registration markers were detected

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.

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

3 sampled page(s) have missing or multiple meta descriptions; 10 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.

• /agents.md
• /llms-full.txt
• /llms.txt
• www.modeta.cz
• /collections/plavky

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

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

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.

• /agents.md
• /llms-full.txt
• /llms.txt
• /products/jednodilne-tvarujici-plavky-s-prusvitnymi-vsadkami-cerne
• /products/jednodilne-tvarujici-plavky-s-prusvitnymi-vsadkami-na-bocich-cerne

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

5 H1 issue(s) and 9 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.

• /agents.md
• /llms-full.txt
• /llms.txt
• /pages/jak-se-zmerit
• www.modeta.cz

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.

Every sampled HTML page starts with the HTML5 doctype so browsers and validators use standards mode.

3 sampled page(s) are missing an HTML5 doctype.

Add `<!doctype html>` as the first meaningful bytes before the `<html>` element on every public HTML document. This keeps browsers in standards mode and avoids parser differences that can affect crawlers, validators, and assistive technology.

• /agents.md
• /llms-full.txt
• /llms.txt

Every sampled page declares the primary content language on `<html lang>` so crawlers, translators, and assistive tech interpret it correctly.

3 sampled page(s) miss <html lang> and 0 use an invalid language value.

Set the primary page language on the root element, for example `<html lang="en">` or `<html lang="en-GB">`. Keep the value aligned with the visible page language and use hreflang links only for alternate localized URLs.

• /agents.md
• /llms-full.txt
• /llms.txt

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

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

• www.modeta.cz
• /collections/plavky
• /pages/jak-se-zmerit
• /products/jednodilne-plavky-s-efektnim-prekrizenim-cerne
• /products/jednodilne-tvarujici-plavky-s-prusvitnymi-vsadkami-cerne

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

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

• www.modeta.cz
• /agents.md
• /collections/plavky
• /llms-full.txt
• /llms.txt

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

0 page(s) are under 100 words; 2 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.

• /llms-full.txt
• /llms.txt

Content pages with factual claims link out to credible external primary sources so readers and answer engines can verify context.

4 content page(s) have fewer than two contextual external citation links.

For articles, guides, and research-like pages, cite official docs, standards, primary research, or authoritative sources where claims need support. Do not add arbitrary outbound links to transactional pages, and avoid vague anchors like "click here".

• www.modeta.cz
• /agents.md
• /collections/plavky
• /pages/jak-se-zmerit

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

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

• www.modeta.cz
• /pages/jak-se-zmerit

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

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

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.

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

0 blocking social preview issue(s) and 9 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.

• www.modeta.cz
• /collections/plavky
• /pages/jak-se-zmerit
• /products/jednodilne-plavky-s-efektnim-prekrizenim-cerne
• /products/jednodilne-tvarujici-plavky-s-prusvitnymi-vsadkami-cerne

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

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

• www.modeta.cz
• /collections/plavky
• /products/jednodilne-plavky-s-efektnim-prekrizenim-cerne
• /products/jednodilne-tvarujici-plavky-s-prusvitnymi-vsadkami-cerne
• /products/jednodilne-tvarujici-plavky-s-prusvitnymi-vsadkami-na-bocich-cerne

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.

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.

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.

HTTP Observatory grade F with score 0.

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.

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

Domain registration data is temporarily unavailable.

Cloudflare reported cache status DYNAMIC.

Homepage Link headers do not advertise agent-useful discovery artifacts

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

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

No ACP discovery markers were detected

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.

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

No MPP discovery markers were detected

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.

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

No x402 discovery markers were detected

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.

Scanned 12 representative pages out of 227.

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.

No recognizable third-party DNS service signals were detected.

HTML validation is temporarily unavailable.