AI Readiness Report

Field	Value
Page title	The CentOS Project

Field

Value

Page title

The CentOS Project

Dimension	Score	Weight
AI Crawlability	16/20	20%
AI Understanding	0/25	25%
AI Content Readiness	7/20	20%
AI Citation Potential	8/20	20%
Agent Readiness	2/10	10%
Trust & Security	5/5	5%
Total	38/100	Grade: Poor

Dimension

Score

Weight

AI Crawlability

16/20

20%

AI Understanding

0/25

25%

AI Content Readiness

7/20

20%

AI Citation Potential

8/20

20%

Agent Readiness

2/10

10%

Trust & Security

5/5

Total

38/100

Grade: Poor

Detailed Findings 30

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://www.centos.org/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": "The CentOS Project",
  "url": "https://www.centos.org",
  "logo": "https://www.centos.org/assets/img/centos-whitelogo.svg"
}
</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": "The CentOS Project Product Name",
  "image": ["https://www.centos.org/assets/img/centos-whitelogo.svg"],
  "description": "Brief product description",
  "brand": { "@type": "Brand", "name": "The CentOS Project" },
  "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": "The CentOS Project" },
  "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://www.centos.org/"
  },{
    "@type": "ListItem", "position": 2,
    "name": "Products", "item": "https://www.centos.org/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 7/20

Homepage content depth: 4/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.

No Blog / Case page found.

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

AI Citation 8/20

Rich topical content detected.

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

No blog or case section found.

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

No author attribution detected.

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 Integration 2/10

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": "The CentOS Project API",
    "version": "1.0.0",
    "description": "Machine-readable API for The CentOS Project"
  },
  "servers": [{ "url": "https://www.centos.org/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": "The CentOS Project", "version": "1.0.0" },
  "capabilities": { "tools": {} },
  "endpoints": { "base": "https://www.centos.org/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.

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 11

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": "The CentOS Project",
  "url": "https://www.centos.org",
  "logo": "https://www.centos.org/assets/img/centos-whitelogo.svg"
}
</script>

No llms.txt was found at the site root. LLMs and AI agents lack a machine-readable site guide to quickly discover key sections and entry points.

Dimension: AI Crawlability

Create a file named llms.txt in the website root.
Paste the template below and replace the links and sections with your real paths.
Optionally provide llms-full.txt with full page content for deeper indexing.

markdown

# The CentOS Project

> The CentOS Project — AI-readable overview for LLMs and agents.

## Home
- [Home](https://www.centos.org/): Main landing page for The CentOS Project.

## Documentation
- [About](https://www.centos.org/about): Company background and mission.
- [Products](https://www.centos.org/products): Product and service overview.
- [Blog](https://www.centos.org/blog): Insights, guides and case studies.

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": "The CentOS Project API",
    "version": "1.0.0",
    "description": "Machine-readable API for The CentOS Project"
  },
  "servers": [{ "url": "https://www.centos.org/api" }],
  "paths": {
    "/health": {
      "get": {
        "summary": "Service health",
        "responses": { "200": { "description": "OK" } }
      }
    }
  }
}

The homepage lacks semantic structure (header / main / article tags or a clear H1-H3 hierarchy), making it harder for AI to distinguish content, navigation and decorative elements.

Dimension: AI Understanding

Wrap the page skeleton with <header>, <main>, <article> and <footer>.
Use exactly one <h1> per page and build a clear hierarchy with <h2> and <h3>.
Avoid stacking content with generic <div> elements alone.

html

<body>
  <header>
    <nav><!-- Site navigation --></nav>
  </header>
  <main>
    <article>
      <h1>Primary page title</h1>
      <h2>Section heading</h2>
      <p>Body content...</p>
    </article>
  </main>
  <footer><!-- Footer --></footer>
</body>

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": "The CentOS Project Product Name",
  "image": ["https://www.centos.org/assets/img/centos-whitelogo.svg"],
  "description": "Brief product description",
  "brand": { "@type": "Brand", "name": "The CentOS Project" },
  "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://www.centos.org/sitemap.xml.
Submit the sitemap to major search engine webmaster tools.

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": "The CentOS Project", "version": "1.0.0" },
  "capabilities": { "tools": {} },
  "endpoints": { "base": "https://www.centos.org/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": "The CentOS Project" },
  "datePublished": "2026-01-01",
  "dateModified": "2026-01-01"
}
</script>

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://www.centos.org/"
  },{
    "@type": "ListItem", "position": 2,
    "name": "Products", "item": "https://www.centos.org/products"
  }]
}
</script>

Site Meta Snapshot

Score Overview

Detailed Findings 30

AI Crawlability 16/20

AI Understanding 0/25

Content Quality 7/20

AI Citation 8/20

Agent Integration 2/10

Trust & Safety 5/5

Actionable Recommendations 11

Websites we've checked

AI Readiness Report

Site Meta Snapshot

Score Overview

Detailed Findings 30

AI Crawlability 16/20

AI Understanding 0/25

Content Quality 7/20

AI Citation 8/20

Agent Integration 2/10

Trust & Safety 5/5

Actionable Recommendations 11

Websites we've checked

Share SVG Badge