Content-Signal detected via robots.txt: search=yes, ai-train=yes, ai-input=yes
Key Gaps
Biggest opportunities
Structured data — FAQ / help page
Sampled 1 faq / help page; expected Faqpage OR Qapage, found: no JSON-LD.
→ Wrap existing Q&A pairs on the FAQ page with FAQPage JSON-LD (`mainEntity` → `Question` + `acceptedAnswer`). AI answer engines cite FAQPage content directly. Target path pattern: /aktion/*.
Machine-readable capability discovery
Probed 18 endpoints — none returned a valid .well-known response.
→ If you expose APIs or developer capabilities, publish /.well-known/openid-configuration, /.well-known/mcp, or /.well-known/api-catalog as appropriate.
No x402, ACP, UCP, MPP, or related commerce-protocol signals found (probed /.well-known/{acp,ucp,mpp,x402,agent-commerce}.json)
→ If you sell products or services, evaluate x402 / ACP / UCP / MPP support and publish a capability document at `/.well-known/acp.json` (or equivalent) with your protocol version + supported actions.
Structured data / Schema.org coverage
Homepage (1 sampled): present — organization
Product pages (1 sampled): present — product
About / company page (1 sampled): present — organization
FAQ / help page (1 sampled): missing
→ Top improvements for this scan (highest impact, already quick to ship):
• Add Faqpage or Qapage on /aktion/* (FAQ / help page) — impact +8, ease 2/5.
MCP server card (.well-known/mcp.json)
No `/.well-known/mcp.json` or `/.well-known/mcp` available
→ Publish `/.well-known/mcp.json` describing your MCP server: include `name`, `description`, `capabilities`, `tools[]`, and optional `auth` endpoints per the MCP spec.
Suggested Improvements
Where to focus next
Structured data — FAQ / help page — Wrap existing Q&A pairs on the FAQ page with FAQPage JSON-LD (`mainEntity` → `Question` + `acceptedAnswer`). AI answer engines cite FAQPage content directly. Target path pattern: /aktion/*.
Machine-readable capability discovery — If you expose APIs or developer capabilities, publish /.well-known/openid-configuration, /.well-known/mcp, or /.well-known/api-catalog as appropriate.
Emerging commerce protocol signals (x402, ACP, UCP, MPP) — If you sell products or services, evaluate x402 / ACP / UCP / MPP support and publish a capability document at `/.well-known/acp.json` (or equivalent) with your protocol version + supported actions.
Structured data / Schema.org coverage — Top improvements for this scan (highest impact, already quick to ship):
• Add Faqpage or Qapage on /aktion/* (FAQ / help page) — impact +8, ease 2/5.
MCP server card (.well-known/mcp.json) — Publish `/.well-known/mcp.json` describing your MCP server: include `name`, `description`, `capabilities`, `tools[]`, and optional `auth` endpoints per the MCP spec.
Get a fresh Agent Readiness audit for your own site
Run a free scan now and see how your website compares to Heinz and the rest of the Index.