AI Readiness Report

Field	Value
Page title	Red Hat - We make open source technologies for the enterprise
Meta description	Red Hat is the world’s leading provider of enterprise open source solutions, including high-performing Linux, cloud, container, and Kubernetes technologies.

Field

Value

Page title

Red Hat - We make open source technologies for the enterprise

Meta description

Red Hat is the world’s leading provider of enterprise open source solutions, including high-performing Linux, cloud, container, and Kubernetes technologies.

Dimension	Score	Weight
AI Crawlability	20/20	20%
AI Understanding	0/25	25%
AI Content Readiness	16/20	20%
AI Citation Potential	14/20	20%
Agent Readiness	2/10	10%
Trust & Security	4/5	5%
Total	56/100	Grade: Needs Work

Dimension

Score

Weight

AI Crawlability

20/20

20%

AI Understanding

0/25

25%

AI Content Readiness

16/20

20%

AI Citation Potential

14/20

20%

Agent Readiness

2/10

10%

Trust & Security

4/5

Total

56/100

Grade: Needs Work

Detailed Findings 30

AI Crawlability 20/20

robots.txt reachable.

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

sitemap.xml declared.

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

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": "Red Hat - We make open source technologies for the enterprise",
  "url": "https://www.redhat.com",
  "logo": "https://www.redhat.com/rhdc/managed-files/Lightwell_logo_rev_full_color.webp"
}
</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": "Red Hat - We make open source technologies for the enterprise Product Name",
  "image": ["https://www.redhat.com/rhdc/managed-files/Lightwell_logo_rev_full_color.webp"],
  "description": "Brief product description",
  "brand": { "@type": "Brand", "name": "Red Hat - We make open source technologies for the enterprise" },
  "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": "Red Hat - We make open source technologies for the enterprise" },
  "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.redhat.com/"
  },{
    "@type": "ListItem", "position": 2,
    "name": "Products", "item": "https://www.redhat.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 16/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.

Product page reachable.

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

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": "Red Hat - We make open source technologies for the enterprise API",
    "version": "1.0.0",
    "description": "Machine-readable API for Red Hat - We make open source technologies for the enterprise"
  },
  "servers": [{ "url": "https://www.redhat.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": "Red Hat - We make open source technologies for the enterprise", "version": "1.0.0" },
  "capabilities": { "tools": {} },
  "endpoints": { "base": "https://www.redhat.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.

Trust & Safety 4/5

Served over HTTPS.

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

No contact info 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 9

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": "Red Hat - We make open source technologies for the enterprise",
  "url": "https://www.redhat.com",
  "logo": "https://www.redhat.com/rhdc/managed-files/Lightwell_logo_rev_full_color.webp"
}
</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": "Red Hat - We make open source technologies for the enterprise API",
    "version": "1.0.0",
    "description": "Machine-readable API for Red Hat - We make open source technologies for the enterprise"
  },
  "servers": [{ "url": "https://www.redhat.com/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": "Red Hat - We make open source technologies for the enterprise Product Name",
  "image": ["https://www.redhat.com/rhdc/managed-files/Lightwell_logo_rev_full_color.webp"],
  "description": "Brief product description",
  "brand": { "@type": "Brand", "name": "Red Hat - We make open source technologies for the enterprise" },
  "offers": { "@type": "Offer", "priceCurrency": "USD", "price": "0" }
}
</script>

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": "Red Hat - We make open source technologies for the enterprise", "version": "1.0.0" },
  "capabilities": { "tools": {} },
  "endpoints": { "base": "https://www.redhat.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": "Red Hat - We make open source technologies for the enterprise" },
  "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.redhat.com/"
  },{
    "@type": "ListItem", "position": 2,
    "name": "Products", "item": "https://www.redhat.com/products"
  }]
}
</script>

Site Meta Snapshot

Score Overview

Detailed Findings 30

AI Crawlability 20/20

AI Understanding 0/25

Content Quality 16/20

AI Citation 14/20

Agent Integration 2/10

Trust & Safety 4/5

Actionable Recommendations 9

Websites we've checked

AI Readiness Report

Site Meta Snapshot

Score Overview

Detailed Findings 30

AI Crawlability 20/20

AI Understanding 0/25

Content Quality 16/20

AI Citation 14/20

Agent Integration 2/10

Trust & Safety 4/5

Actionable Recommendations 9

Websites we've checked

Share SVG Badge