AI Readiness Report

Site Meta Snapshot

Field	Value
Page title	Statamic — the answer to your frustrating CMS problems.
Meta description	Statamic supports your entire team with an award-winning user experience, a kind-hearted community, and all the power of Laravel at your fingertips.
Meta keywords	Statamic, Statamic CMS, CMS, Content, Management, System, Flat File CMS, Flat File Content Management System, WordPress Alternative, PHP CMS, Laravel CMS, Headless CMS, Enterprise CMS

Field

Value

Page title

Statamic — the answer to your frustrating CMS problems.

Meta description

Statamic supports your entire team with an award-winning user experience, a kind-hearted community, and all the power of Laravel at your fingertips.

Meta keywords

Statamic, Statamic CMS, CMS, Content, Management, System, Flat File CMS, Flat File Content Management System, WordPress Alternative, PHP CMS, Laravel CMS, Headless CMS, Enterprise CMS

Dimension	Score	Weight
AI Crawlability	16/20	20%
AI Understanding	0/25	25%
AI Content Readiness	12/20	20%
AI Citation Potential	17/20	20%
Agent & Protocol Readiness	2/25	25%
Trust & Security	5/5	5%
Total	48/100	Grade: Poor

Dimension

Score

Weight

AI Crawlability

16/20

20%

AI Understanding

0/25

25%

AI Content Readiness

12/20

20%

AI Citation Potential

17/20

20%

Agent & Protocol Readiness

2/25

25%

Trust & Security

5/5

Total

48/100

Grade: Poor

Detailed Findings 38

AI Crawlability 16/20

robots.txt reachable.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

No sitemap declared.

No sitemap.xml was declared. AI crawlers cannot systematically discover all of your pages, so deeper content may remain unindexed.

Generate a sitemap.xml and place it in the website root.
Add the reference in robots.txt: Sitemap: https://statamic.com/sitemap.xml.
Submit the sitemap to major search engine webmaster tools.

GPTBot allowed in robots.txt.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

ClaudeBot allowed in robots.txt.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

Google-Extended allowed in robots.txt.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

Bytespider allowed in robots.txt.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

KimiBot allowed in robots.txt.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

AI Understanding 0/25

No Organization/LocalBusiness schema.

No Organization / LocalBusiness schema was detected. AI engines rely on this markup to build accurate entity relationships and brand understanding, which directly affects citation quality.

Copy the JSON-LD snippet below into the <head> section of your homepage.
Replace name, url and logo with your actual brand details (use an absolute URL for the logo).
Re-run the analysis after deploying the change.

html

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Statamic — the answer to your frustrating CMS problems.",
  "url": "https://statamic.com",
  "logo": "https://statamic.com/glide-img/asset/c2hvd2Nhc2VfaW1hZ2VzLzE3ODYzNTcyMTYtb3Bzc3VpdGUgbG9nbyAoMikuanBn/1786357216-opssuite%20logo%20%282%29.jpg?w=660&amp;fm=webp&amp;s=c7da1db0d14c45b7b57cab56e7447eb3"
}
</script>

No Product schema.

No Product schema was detected. E-commerce or product content cannot be recognised and cited by AI as a structured entity, which costs you rich-result placement.

Add the Product JSON-LD below to each product detail page.
Replace name, image, price and brand with real values (price must be a numeric string).
Use ItemList to aggregate multiple products on listing pages.

html

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Statamic — the answer to your frustrating CMS problems. Product Name",
  "image": ["https://statamic.com/glide-img/asset/c2hvd2Nhc2VfaW1hZ2VzLzE3ODYzNTcyMTYtb3Bzc3VpdGUgbG9nbyAoMikuanBn/1786357216-opssuite%20logo%20%282%29.jpg?w=660&amp;fm=webp&amp;s=c7da1db0d14c45b7b57cab56e7447eb3"],
  "description": "Brief product description",
  "brand": { "@type": "Brand", "name": "Statamic — the answer to your frustrating CMS problems." },
  "offers": { "@type": "Offer", "priceCurrency": "USD", "price": "0" }
}
</script>

No FAQPage schema.

No FAQPage schema was detected. Common questions and answers cannot be cited directly by AI as authoritative answers, and you miss rich-result opportunities.

Add the FAQPage JSON-LD below to your FAQ page.
Make sure the question/answer text matches the visible page content exactly.

html

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "Your first question?",
    "acceptedAnswer": { "@type": "Answer", "text": "The authoritative answer." }
  }]
}
</script>

No Article schema.

No Article schema was detected. Editorial content is less likely to be treated as an authoritative source by AI, and you miss rich-result placement.

Add the Article JSON-LD below to each article page.
Ensure author, publisher and datePublished match the visible content.

html

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Article title",
  "author": { "@type": "Person", "name": "Author name" },
  "publisher": { "@type": "Organization", "name": "Statamic — the answer to your frustrating CMS problems." },
  "datePublished": "2026-01-01",
  "dateModified": "2026-01-01"
}
</script>

No Breadcrumb schema.

No Breadcrumb schema was detected. AI cannot infer the site hierarchy and breadcrumb relationships as easily, which affects internal-link context.

Add the BreadcrumbList JSON-LD below to relevant pages.
Increment position from 1 and use real, accessible URLs for each item.

html

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [{
    "@type": "ListItem", "position": 1,
    "name": "Home", "item": "https://statamic.com/"
  },{
    "@type": "ListItem", "position": 2,
    "name": "Products", "item": "https://statamic.com/products"
  }]
}
</script>

Entity fields covered: 0/11.

Brand entity coverage is insufficient. AI cannot build a complete entity profile (description, contact details, industry, sameAs social links, etc.), lowering the chance of accurate citations.

Extend your Organization / WebSite schema with description, telephone, email, address, industry, founder and foundingDate.
Link official social profiles, Wikipedia or other authoritative pages via sameAs.
Keep the brand name and logo consistent across all pages.

Content Quality 12/20

Homepage content depth: 5/5.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

About page reachable.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

No Product page found.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

No FAQ page found.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

Blog / Case page reachable.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

AI Citation 17/20

Rich topical content detected.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

Blog / case / news section reachable.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

Author / byline information present.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

Brand entity present but not consistently surfaced.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

Few external trust signals.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

Agent & Protocol Readiness 2/25

No OpenAPI descriptor detected.

No OpenAPI / Swagger descriptor was detected. AI agents cannot auto-discover or invoke your API, which means you miss tool-integration opportunities.

Serve the OpenAPI 3.0 manifest below at /openapi.json.
Fill in your real paths, component schemas and authentication method.
Link to the descriptor from your homepage or developer docs.

json

{
  "openapi": "3.0.3",
  "info": {
    "title": "Statamic — the answer to your frustrating CMS problems. API",
    "version": "1.0.0",
    "description": "Machine-readable API for Statamic — the answer to your frustrating CMS problems."
  },
  "servers": [{ "url": "https://statamic.com/api" }],
  "paths": {
    "/health": {
      "get": {
        "summary": "Service health",
        "responses": { "200": { "description": "OK" } }
      }
    }
  }
}

No Model Context Protocol endpoint found.

No Model Context Protocol (MCP) endpoint was detected. AI agents cannot tool-enable your service through tools or resources without it.

Serve the manifest below at /.well-known/mcp.json.
Implement the corresponding MCP server (tools and resources).
Document the integration path in your developer docs.

json

{
  "protocolVersion": "2024-11-05",
  "serverInfo": { "name": "Statamic — the answer to your frustrating CMS problems.", "version": "1.0.0" },
  "capabilities": { "tools": {} },
  "endpoints": { "base": "https://statamic.com/mcp" }
}

No AI Actions manifest detected.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

API / developer documentation linked.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

No RFC 8288 Link response header detected.

No RFC 8288 Link response header was found. Agents cannot discover your API, docs or AI feed from response headers.

Add a Link header on your homepage pointing to key machine-readable resources.
Example: Link: <https://statamic.com/openapi.json>; rel="service-desc", <https://statamic.com/llms.txt>; rel="describedby"

No DNS-AID (SVCB/HTTPS) records detected.

No DNS-AID (SVCB/HTTPS) records were detected. Agents cannot discover your AI service endpoint directly from DNS.

Publish SVCB or HTTPS DNS records that point to your AI/agent service.
These let agents resolve your MCP or API endpoint without crawling HTML.

No Markdown content negotiation (Accept: text/markdown) detected.

No Markdown content negotiation (Accept: text/markdown) was detected. Agents must parse HTML instead of clean Markdown.

When the request Accept header is text/markdown, return a clean Markdown version of the page.
Point agents to /llms.txt as a fallback machine-readable overview.

No Content Signals directive (ai-train/search/ai-input) detected.

No Content Signals directive (ai-train / search / ai-input) was detected. You are not explicitly telling AI bots how they may use your content.

Add a Content-Signals response header or <meta name="content-signals" content="ai-train=yes; search=yes; ai-input=yes">.

No MCP Server Card (.well-known/mcp/server-card.json) found.

No MCP Server Card was found at .well-known/mcp/server-card.json. Agents cannot discover your MCP tools and resources.

Serve the Server Card below at /.well-known/mcp/server-card.json.
Implement the corresponding MCP server (tools and resources).

json

{
  "protocolVersion": "2024-11-05",
  "serverInfo": { "name": "Statamic — the answer to your frustrating CMS problems.", "version": "1.0.0" },
  "capabilities": { "tools": {}, "resources": {} },
  "endpoints": { "base": "https://statamic.com/mcp" }
}

No Agent Skills catalog (.well-known/agent-skills) found.

No Agent Skills catalog was found at .well-known/agent-skills. Agents cannot discover the skills your site offers.

Create .well-known/agent-skills/ with an index.json listing your skills.
Each skill should have a SKILL.md describing when and how to use it.

No OAuth discovery (.well-known/oauth-authorization-server) found.

No OAuth discovery endpoint (.well-known/oauth-authorization-server) was detected. Agents cannot securely authenticate to your API.

Publish an OAuth 2.0 authorization server metadata document at /.well-known/oauth-authorization-server.

No Auth.md found.

No Auth.md was found. Agents lack guidance on how to authenticate against your services.

Add an Auth.md at your site root or .well-known/ describing authentication flows for agents.

Trust & Safety 5/5

Served over HTTPS.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

Business contact visible.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

HTTP status 200.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

Actionable Recommendations 17

No Organization / LocalBusiness schema was detected. AI engines rely on this markup to build accurate entity relationships and brand understanding, which directly affects citation quality.

Dimension: AI Understanding

Copy the JSON-LD snippet below into the <head> section of your homepage.
Replace name, url and logo with your actual brand details (use an absolute URL for the logo).
Re-run the analysis after deploying the change.

html

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Statamic — the answer to your frustrating CMS problems.",
  "url": "https://statamic.com",
  "logo": "https://statamic.com/glide-img/asset/c2hvd2Nhc2VfaW1hZ2VzLzE3ODYzNTcyMTYtb3Bzc3VpdGUgbG9nbyAoMikuanBn/1786357216-opssuite%20logo%20%282%29.jpg?w=660&amp;fm=webp&amp;s=c7da1db0d14c45b7b57cab56e7447eb3"
}
</script>

No OpenAPI / Swagger descriptor was detected. AI agents cannot auto-discover or invoke your API, which means you miss tool-integration opportunities.

Dimension: Agent

Serve the OpenAPI 3.0 manifest below at /openapi.json.
Fill in your real paths, component schemas and authentication method.
Link to the descriptor from your homepage or developer docs.

json

{
  "openapi": "3.0.3",
  "info": {
    "title": "Statamic — the answer to your frustrating CMS problems. API",
    "version": "1.0.0",
    "description": "Machine-readable API for Statamic — the answer to your frustrating CMS problems."
  },
  "servers": [{ "url": "https://statamic.com/api" }],
  "paths": {
    "/health": {
      "get": {
        "summary": "Service health",
        "responses": { "200": { "description": "OK" } }
      }
    }
  }
}

Brand entity coverage is insufficient. AI cannot build a complete entity profile (description, contact details, industry, sameAs social links, etc.), lowering the chance of accurate citations.

Dimension: AI Understanding

Extend your Organization / WebSite schema with description, telephone, email, address, industry, founder and foundingDate.
Link official social profiles, Wikipedia or other authoritative pages via sameAs.
Keep the brand name and logo consistent across all pages.

No Product schema was detected. E-commerce or product content cannot be recognised and cited by AI as a structured entity, which costs you rich-result placement.

Dimension: AI Understanding

Add the Product JSON-LD below to each product detail page.
Replace name, image, price and brand with real values (price must be a numeric string).
Use ItemList to aggregate multiple products on listing pages.

html

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Statamic — the answer to your frustrating CMS problems. Product Name",
  "image": ["https://statamic.com/glide-img/asset/c2hvd2Nhc2VfaW1hZ2VzLzE3ODYzNTcyMTYtb3Bzc3VpdGUgbG9nbyAoMikuanBn/1786357216-opssuite%20logo%20%282%29.jpg?w=660&amp;fm=webp&amp;s=c7da1db0d14c45b7b57cab56e7447eb3"],
  "description": "Brief product description",
  "brand": { "@type": "Brand", "name": "Statamic — the answer to your frustrating CMS problems." },
  "offers": { "@type": "Offer", "priceCurrency": "USD", "price": "0" }
}
</script>

No sitemap.xml was declared. AI crawlers cannot systematically discover all of your pages, so deeper content may remain unindexed.

Dimension: AI Crawlability

Generate a sitemap.xml and place it in the website root.
Add the reference in robots.txt: Sitemap: https://statamic.com/sitemap.xml.
Submit the sitemap to major search engine webmaster tools.

No RFC 8288 Link response header was found. Agents cannot discover your API, docs or AI feed from response headers.

Dimension: Agent

Add a Link header on your homepage pointing to key machine-readable resources.
Example: Link: <https://statamic.com/openapi.json>; rel="service-desc", <https://statamic.com/llms.txt>; rel="describedby"

No Markdown content negotiation (Accept: text/markdown) was detected. Agents must parse HTML instead of clean Markdown.

Dimension: Agent

When the request Accept header is text/markdown, return a clean Markdown version of the page.
Point agents to /llms.txt as a fallback machine-readable overview.

No Model Context Protocol (MCP) endpoint was detected. AI agents cannot tool-enable your service through tools or resources without it.

Dimension: Agent

Serve the manifest below at /.well-known/mcp.json.
Implement the corresponding MCP server (tools and resources).
Document the integration path in your developer docs.

json

{
  "protocolVersion": "2024-11-05",
  "serverInfo": { "name": "Statamic — the answer to your frustrating CMS problems.", "version": "1.0.0" },
  "capabilities": { "tools": {} },
  "endpoints": { "base": "https://statamic.com/mcp" }
}

No MCP Server Card was found at .well-known/mcp/server-card.json. Agents cannot discover your MCP tools and resources.

Dimension: Agent

Serve the Server Card below at /.well-known/mcp/server-card.json.
Implement the corresponding MCP server (tools and resources).

json

{
  "protocolVersion": "2024-11-05",
  "serverInfo": { "name": "Statamic — the answer to your frustrating CMS problems.", "version": "1.0.0" },
  "capabilities": { "tools": {}, "resources": {} },
  "endpoints": { "base": "https://statamic.com/mcp" }
}

No FAQPage schema was detected. Common questions and answers cannot be cited directly by AI as authoritative answers, and you miss rich-result opportunities.

Dimension: AI Understanding

Add the FAQPage JSON-LD below to your FAQ page.
Make sure the question/answer text matches the visible page content exactly.

html

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "Your first question?",
    "acceptedAnswer": { "@type": "Answer", "text": "The authoritative answer." }
  }]
}
</script>

No Article schema was detected. Editorial content is less likely to be treated as an authoritative source by AI, and you miss rich-result placement.

Dimension: AI Understanding

Add the Article JSON-LD below to each article page.
Ensure author, publisher and datePublished match the visible content.

html

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Article title",
  "author": { "@type": "Person", "name": "Author name" },
  "publisher": { "@type": "Organization", "name": "Statamic — the answer to your frustrating CMS problems." },
  "datePublished": "2026-01-01",
  "dateModified": "2026-01-01"
}
</script>

No DNS-AID (SVCB/HTTPS) records were detected. Agents cannot discover your AI service endpoint directly from DNS.

Dimension: Agent

Publish SVCB or HTTPS DNS records that point to your AI/agent service.
These let agents resolve your MCP or API endpoint without crawling HTML.

No Agent Skills catalog was found at .well-known/agent-skills. Agents cannot discover the skills your site offers.

Dimension: Agent

Create .well-known/agent-skills/ with an index.json listing your skills.
Each skill should have a SKILL.md describing when and how to use it.

No Breadcrumb schema was detected. AI cannot infer the site hierarchy and breadcrumb relationships as easily, which affects internal-link context.

Dimension: AI Understanding

Add the BreadcrumbList JSON-LD below to relevant pages.
Increment position from 1 and use real, accessible URLs for each item.

html

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [{
    "@type": "ListItem", "position": 1,
    "name": "Home", "item": "https://statamic.com/"
  },{
    "@type": "ListItem", "position": 2,
    "name": "Products", "item": "https://statamic.com/products"
  }]
}
</script>

No Content Signals directive (ai-train / search / ai-input) was detected. You are not explicitly telling AI bots how they may use your content.

Dimension: Agent

Add a Content-Signals response header or <meta name="content-signals" content="ai-train=yes; search=yes; ai-input=yes">.

No OAuth discovery endpoint (.well-known/oauth-authorization-server) was detected. Agents cannot securely authenticate to your API.

Dimension: Agent

Publish an OAuth 2.0 authorization server metadata document at /.well-known/oauth-authorization-server.

No Auth.md was found. Agents lack guidance on how to authenticate against your services.

Dimension: Agent

Add an Auth.md at your site root or .well-known/ describing authentication flows for agents.

Site Meta Snapshot

Score Overview

Detailed Findings 38

AI Crawlability 16/20

AI Understanding 0/25

Content Quality 12/20

AI Citation 17/20

Agent & Protocol Readiness 2/25

Trust & Safety 5/5

Actionable Recommendations 17

Websites we've checked

AI Readiness Report

Site Meta Snapshot

Score Overview

Detailed Findings 38

AI Crawlability 16/20

AI Understanding 0/25

Content Quality 12/20

AI Citation 17/20

Agent & Protocol Readiness 2/25

Trust & Safety 5/5

Actionable Recommendations 17

Websites we've checked

Share SVG Badge