Skip to content
Good for Bots

redhat.com

Good for Bots: Fair +1, 57 of 100Get this badge →

On your homepage, it turns this report’s link to redhat.com dofollow.

Scanned
Markdown
Read this report

Good for Bots report

redhat.com scores 57 of 100: 37 of the 50 base points, 20 of the 50 agent-layer points, no penalties.

Earned

37 of the 50 base points above the line, 20 of the 50 agent-layer points below it.

57
31

Still open

Behind the checks below, with prompts in Pro.

12
Penalties0
How scoring works · current methodology →

For the owner of redhat.com

3 prompts, 31 points

They are in the owner view, ready to paste into Claude Code, Cursor or Codex, beside the badge and rescans.

Open the owner view →

All 36 checks

Evidence for each, in Markdown →

Select a check to see what we found and how it is graded.

Readable base

36.7 / 50

Passes.

3.3 of 3.3 points.

robots.txt is valid, with 1 user-agent group.

Passes.

8.3 of 8.3 points.

Sitemap declared in robots.txt, listing at least 421 URLs.

Fails.

0 of 8.3 points.

Neither page read passes. The homepage publishes no structured data at all: no JSON-LD, no microdata, no RDFa.

Half passes.

5 of 10 points.

1 of 2 pages read pass; 1 partly. The page at /en/blog/channel/devops-and-devsecops is partly structured: The outline jumps from h1 to h3, which the standard forbids.

Prompt in Pro →
Passes.

8.3 of 8.3 points.

113 of 113 assessed homepage navigation links expose usable destinations.

Passes.

4.2 of 4.2 points.

312 of 312 assessed homepage links and buttons have a nonempty accessible name.

Passes.

2.5 of 2.5 points.

3 of 3 assessed homepage form fields meet the static naming and field-semantics checks.

Passes.

2.5 of 2.5 points.

336 of 336 assessed homepage controls and role declarations meet the static role, state and relationship checks.

Passes.

1.7 of 1.7 points.

Both pages read pass. The homepage declares itself as its canonical URL.

Agent layer

20 / 50

Passes.

11.3 of 11.3 points.

/llms.txt is well formed: 28 links across 7 sections.

Passes.

7.5 of 7.5 points.

/llms.txt is descriptive: a summary plus descriptions on 100% of links.

Fails.

0 of 12.5 points.

No /llms-full.txt and no markdown versions linked from llms.txt.

Fails.

0 of 10 points.

Asking the homepage for markdown still returns text/html.

Fails.

0 of 5 points.

robots.txt names no AI crawlers, so every operator has to guess.

Prompt in Pro →
Fails.

0 of 2.5 points.

No usage declaration found in robots.txt or the final successful homepage response header.

Prompt in Pro →

Penalties

− 0

Passes.

Penalty: 0 of 15 points.

Our crawler reaches the page without being challenged.

Passes.

Penalty: 0 of 20 points.

Nothing on the homepage tells a crawler to skip it or to withhold its snippet.

Passes.

Penalty: 0 of 25 points.

The captured homepage HTML contains 1705 content words; completeness is not assessed.

Passes.

Penalty: 0 of 25 points.

robots.txt allows every known search and user-fetch crawler to reach the homepage.

Passes.

Penalty: 0 of 10 points.

The homepage is served over HTTPS and returns HTTP 200.

Passes.

Penalty: 0 of 3 points.

The homepage provides both a non-empty title and meta description.

Passes.

Penalty: 0 of 3 points.

The homepage is reached in 1 redirect.

Passes.

Penalty: 0 of 3 points.

The homepage reached a plain crawler in 389 ms.

Agent capabilities

1 of 11 · no points

Each one found adds +1 to the badge.

Passes.

+1 on the badge.

Publishes an API catalog describing 1 API.

Not applicable.

Adds +1 to the badge when found.

No /auth.md published.

Not applicable.

Adds +1 to the badge when found.

No AI Catalog published, so no MCP server card can be discovered.

Not applicable.

Adds +1 to the badge when found.

No A2A Agent Card at /.well-known/agent-card.json, and none listed in an AI Catalog.

Not applicable.

Adds +1 to the badge when found.

No usable Agent Skills index was found at either well-known path or in the AI Catalog.

Not applicable.

Adds +1 to the badge when found.

No WebMCP declarations were found in the collected HTML or inline scripts. External scripts were not inspected.

Not applicable.

Adds +1 to the badge when found.

No Web Bot Auth key directory at /.well-known/http-message-signatures-directory.

Not applicable.

Adds +1 to the badge when found.

No HTTP 402 payment challenge on the homepage or robots.txt, and no manifest at /.well-known/x402.

Not applicable.

Adds +1 to the badge when found.

No ACP discovery declaration established at /.well-known/acp.json.

Not applicable.

Adds +1 to the badge when found.

No UCP discovery declaration established at /.well-known/ucp.

Not applicable.

Adds +1 to the badge when found.

No public AMP discovery declaration established. Private or hidden agents may not advertise one to our crawler.

Readable base · redhat.com

robots.txt

robots.txt is present and valid

Passes3.3 of 3.3 points

What we found

robots.txt is valid, with 1 user-agent group.

Crawler groups
1
Directives
91
Sitemap declarations
12

Parser findings

No parser errors recorded

Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "errors": [],
  "groups": 1,
  "sitemaps": 12,
  "directives": 91
}

Related checks

See sites that pass robots.txt →Check again: robots.txt checker →Guide: How to write robots.txt rules for AI crawlers →
Methodology →

Readable base · redhat.com

Sitemap

Sitemap is present and parses

Passes8.3 of 8.3 points

What we found

Sitemap declared in robots.txt, listing at least 421 URLs.

URLs collected
421
Documents checked
5
Discovery via robots.txt
Declared

Sitemap sample

  • https://www.redhat.com/sitemap.xml · 23 URLs
  • https://www.redhat.com/markdown-sitemap.xml · 0 URLs · HTTP 404
  • https://www.redhat.com/en/sitemap-news.xml · 0 URLs · Neither a urlset nor a sitemapindex with entries
  • https://www.redhat.com/en/sitemap.xml · 200 URLs
  • https://www.redhat.com/de/sitemap.xml · 200 URLs
Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "urlCount": 421,
  "documents": [
    {
      "url": "https://www.redhat.com/sitemap.xml",
      "kind": "urlset",
      "urls": 23,
      "error": null,
      "valid": true,
      "children": 0,
      "compressed": false
    },
    {
      "url": "https://www.redhat.com/markdown-sitemap.xml",
      "kind": "missing",
      "urls": 0,
      "cause": "not-found",
      "error": "HTTP 404",
      "valid": false,
      "children": 0,
      "compressed": false
    },
    {
      "url": "https://www.redhat.com/en/sitemap-news.xml",
      "kind": "invalid",
      "urls": 0,
      "error": "Neither a urlset nor a sitemapindex with entries",
      "valid": false,
      "children": 0,
      "compressed": false
    },
    {
      "url": "https://www.redhat.com/en/sitemap.xml",
      "kind": "urlset",
      "urls": 200,
      "error": null,
      "valid": true,
      "children": 0,
      "compressed": false
    },
    {
      "url": "https://www.redhat.com/de/sitemap.xml",
      "kind": "urlset",
      "urls": 200,
      "error": null,
      "valid": true,
      "children": 0,
      "compressed": false
    }
  ],
  "declaredInRobots": true
}

Related checks

See sites that pass Sitemap →
Methodology →

Readable base · redhat.com

schema.org JSON-LD

Describes itself to machines with schema.org JSON-LD

Fails0 of 8.3 points

What we found

Neither page read passes. The homepage publishes no structured data at all: no JSON-LD, no microdata, no RDFa.

Pages read

Each page is checked on its own; the median page decides. Types and counts below cover every page read.

  • Fails: Homepage

    The homepage publishes no structured data at all: no JSON-LD, no microdata, no RDFa.

  • Fails: /en/blog/channel/devops-and-devsecops

    The page at /en/blog/channel/devops-and-devsecops publishes no structured data at all: no JSON-LD, no microdata, no RDFa.

Entities
0
Valid JSON-LD blocks
0
Pages examined
2

JSON-LD types

No JSON-LD types recorded

How to fix

+8.3score from 79 to 88
Copy the prompt in the owner view →
Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "nodes": 0,
  "pages": [
    {
      "url": "https://www.redhat.com/en",
      "reason": "none",
      "status": "fail",
      "summary": "The homepage publishes no structured data at all: no JSON-LD, no microdata, no RDFa.",
      "homepage": true
    },
    {
      "url": "https://www.redhat.com/en/blog/channel/devops-and-devsecops",
      "reason": "none",
      "status": "fail",
      "summary": "The page at /en/blog/channel/devops-and-devsecops publishes no structured data at all: no JSON-LD, no microdata, no RDFa.",
      "homepage": false
    }
  ],
  "types": [],
  "blocks": 0,
  "reason": "none",
  "contexts": [],
  "rdfaTypes": [],
  "truncated": false,
  "validBlocks": 0,
  "brokenBlocks": [],
  "unknownTypes": [],
  "pagesExamined": 2,
  "skippedBlocks": 0,
  "topLevelNodes": 0,
  "microdataTypes": [],
  "missingProperties": [],
  "unnamedTopLevelTypes": []
}

Related checks

See sites that pass schema.org JSON-LD →
Methodology →

Readable base · redhat.com

Semantic HTML

Content is marked up so a reader can find it

Half passes5 of 10 points

What we found

1 of 2 pages read pass; 1 partly. The page at /en/blog/channel/devops-and-devsecops is partly structured: The outline jumps from h1 to h3, which the standard forbids.

Pages read

Each page is checked on its own; the median page decides. The measurements below describe the homepage.

  • Passes: Homepage

    The homepage marks its content root, its heading outline and its landmarks.

  • Half passes: /en/blog/channel/devops-and-devsecops

    The page at /en/blog/channel/devops-and-devsecops is partly structured: The outline jumps from h1 to h3, which the standard forbids.

Extracted words
2,232
Headings
78
H1 headings
1

Content and navigation

Share of extracted homepage words by marked region. Navigation inside a header, footer or main region is counted once, under navigation.

Extracted words and their share by page region
RegionWordsShare
Main region1,51267.74%
Navigation53924.15%
Page header00%
Page footer00%
Other text1818.11%

542 words appear before the first main-region text in HTML order.

Diagnostic only; it does not affect the score. Recognised hidden text and script payloads are excluded. Stylesheet visibility and repetition across pages are unknown. A large menu is not necessarily a problem.

Heading outline · first 4

  • H3AI Overview
  • H3AI Products
  • H3AI Engage & learn
  • H3Hybrid cloud Platform solutions

74 more headings recorded

Page landmarks

  • form
  • navigation

How to fix

The prompt is in Pro →
Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "gaps": [],
  "pages": [
    {
      "url": "https://www.redhat.com/en",
      "reason": "structured",
      "status": "pass",
      "summary": "The homepage marks its content root, its heading outline and its landmarks.",
      "homepage": true
    },
    {
      "url": "https://www.redhat.com/en/blog/channel/devops-and-devsecops",
      "reason": "partly-structured",
      "status": "warn",
      "summary": "The page at /en/blog/channel/devops-and-devsecops is partly structured: The outline jumps from h1 to h3, which the standard forbids.",
      "homepage": false
    }
  ],
  "roots": [
    {
      "words": 1512,
      "source": "role",
      "hierarchicallyCorrect": true
    }
  ],
  "reason": "partly-structured",
  "h1Count": 1,
  "headings": [
    {
      "text": "AI\n       Overview",
      "empty": false,
      "level": 3
    },
    {
      "text": "AI\n       Products",
      "empty": false,
      "level": 3
    },
    {
      "text": "AI\n       Engage & learn",
      "empty": false,
      "level": 3
    },
    {
      "text": "Hybrid cloud\n       Platform solutions",
      "empty": false,
      "level": 3
    },
    {
      "text": "Hybrid cloud\n       Use cases",
      "empty": false,
      "level": 3
    },
    {
      "text": "Hybrid cloud\n       Solutions by industry",
      "empty": false,
      "level": 3
    },
    {
      "text": "Discover cloud technologies",
      "empty": false,
      "level": 3
    },
    {
      "text": "Products\n       Platforms",
      "empty": false,
      "level": 3
    },
    {
      "text": "Products\n       Featured",
      "empty": false,
      "level": 3
    },
    {
      "text": "Products\n       Try & buy",
      "empty": false,
      "level": 3
    },
    {
      "text": "Products\n       Services & support",
      "empty": false,
      "level": 3
    },
    {
      "text": "Training\n       Training & certification",
      "empty": false,
      "level": 3
    },
    "… 66 more items"
  ],
  "bodyWords": 2287,
  "landmarks": [
    {
      "role": "navigation",
      "named": false,
      "source": "role",
      "element": "rh-navigation-primary"
    },
    {
      "role": "form",
      "named": true,
      "source": "native",
      "element": "form"
    }
  ],
  "textRatio": 0.0137,
  "truncated": false,
  "articleCount": 1,
  "contentWords": 1705,
  "headingCount": 78,
  "headingSkips": [],
  "requirements": {
    "landmarks": true,
    "contentRoot": true,
    "headingOutline": true
  },
  "landmarkRoles": [
    "form",
    "navigation"
  ],
  "hiddenMainCount": 0,
  "textComposition": {
    "words": {
      "main": 1512,
      "other": 181,
      "footer": 0,
      "header": 0,
      "navigation": 539
    },
    "shares": {
      "main": 0.6774193548387096,
      "other": 0.08109318996415771,
      "footer": 0,
      "header": 0,
      "navigation": 0.2414874551971326
    },
    "version": 1,
    "truncated": false,
    "totalWords": 2232,
    "analysisLimited": false,
    "mainRegionCount": 1,
    "wordsBeforeMain": 542
  },
  "emptyHeadingCount": 0,
  "misnestedMainCount": 0
}

Related checks

See sites that pass Semantic HTML →
Methodology →

Readable base · redhat.com

Crawlable navigation

Navigation links expose usable destinations

Passes8.3 of 8.3 points

What we found

113 of 113 assessed homepage navigation links expose usable destinations.

Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "good": 113,
  "page": "homepage",
  "total": 113,
  "reason": "observed-gaps",
  "limited": false,
  "examples": [],
  "truncated": false,
  "skippedContactLinks": 0,
  "brokenLabelReferences": 0
}

Related checks

See sites that pass Crawlable navigation →
Methodology →

Readable base · redhat.com

Named links and buttons

Links and buttons have accessible names

Passes4.2 of 4.2 points

What we found

312 of 312 assessed homepage links and buttons have a nonempty accessible name.

Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "good": 312,
  "page": "homepage",
  "total": 312,
  "reason": "observed-gaps",
  "limited": false,
  "examples": [],
  "truncated": false,
  "skippedContactLinks": 0,
  "brokenLabelReferences": 0
}

Related checks

See sites that pass Named links and buttons →
Methodology →

Readable base · redhat.com

Named form fields

Form fields have names and recognizable semantics

Passes2.5 of 2.5 points

What we found

3 of 3 assessed homepage form fields meet the static naming and field-semantics checks.

Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "good": 3,
  "page": "homepage",
  "total": 3,
  "reason": "observed-gaps",
  "limited": false,
  "examples": [],
  "truncated": false,
  "nativeForms": 1,
  "submitControls": 1,
  "inputTypeFallbacks": 0,
  "formsWithoutSubmitControl": 0
}

Related checks

See sites that pass Named form fields →
Methodology →

Readable base · redhat.com

Control roles and states

Controls expose roles, states and relationships

Passes2.5 of 2.5 points

What we found

336 of 336 assessed homepage controls and role declarations meet the static role, state and relationship checks.

Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "good": 336,
  "page": "homepage",
  "total": 336,
  "reason": "observed-gaps",
  "limited": false,
  "examples": [],
  "truncated": false
}

Related checks

See sites that pass Control roles and states →
Methodology →

Readable base · redhat.com

Canonical URL

Each page declares one usable canonical URL

Passes1.7 of 1.7 points

What we found

Both pages read pass. The homepage declares itself as its canonical URL.

Pages read

Each page is checked on its own; the median page decides. The measurements below describe the homepage.

  • Passes: Homepage

    The homepage declares itself as its canonical URL.

  • Passes: /en/blog/channel/devops-and-devsecops

    The page at /en/blog/channel/devops-and-devsecops declares itself as its canonical URL.

Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "pages": [
    {
      "url": "https://www.redhat.com/en",
      "reason": "declared",
      "status": "pass",
      "summary": "The homepage declares itself as its canonical URL.",
      "homepage": true
    },
    {
      "url": "https://www.redhat.com/en/blog/channel/devops-and-devsecops",
      "reason": "declared",
      "status": "pass",
      "summary": "The page at /en/blog/channel/devops-and-devsecops declares itself as its canonical URL.",
      "homepage": false
    }
  ],
  "reason": "declared",
  "target": "https://www.redhat.com/en",
  "readings": [
    {
      "url": "https://www.redhat.com/en",
      "target": "https://www.redhat.com/en",
      "relative": false,
      "crossHost": false,
      "truncated": false,
      "duplicates": 0,
      "declarations": [
        {
          "url": "https://www.redhat.com/en",
          "href": "https://www.redhat.com/en",
          "source": "head"
        }
      ],
      "selfReference": true,
      "invalidDeclarations": 0
    },
    {
      "url": "https://www.redhat.com/en/blog/channel/devops-and-devsecops",
      "target": "https://www.redhat.com/en/blog/channel/devops-and-devsecops",
      "relative": false,
      "crossHost": false,
      "truncated": false,
      "duplicates": 0,
      "declarations": [
        {
          "url": "https://www.redhat.com/en/blog/channel/devops-and-devsecops",
          "href": "https://www.redhat.com/en/blog/channel/devops-and-devsecops",
          "source": "head"
        }
      ],
      "selfReference": true,
      "invalidDeclarations": 0
    }
  ],
  "relative": false,
  "crossHost": false,
  "truncated": false,
  "duplicates": 0,
  "declarations": [
    {
      "url": "https://www.redhat.com/en",
      "href": "https://www.redhat.com/en",
      "source": "head"
    }
  ],
  "selfReference": true,
  "invalidDeclarations": 0
}

Related checks

See sites that pass Canonical URL →
Methodology →

Readable base · redhat.com

Working section links

Section links reach an element on the page

Passes0.8 of 0.8 points

What we found

Both pages read pass. The homepage has 1 section link, and every one reaches an element on the page.

Each page is checked on its own; the median page decides. The measurements below describe the homepage.

  • Passes: Homepage

    The homepage has 1 section link, and every one reaches an element on the page.

  • Passes: /en/blog/channel/devops-and-devsecops

    The page at /en/blog/channel/devops-and-devsecops has 1 section link, and every one reaches an element on the page.

Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "pages": [
    {
      "url": "https://www.redhat.com/en",
      "reason": "working",
      "status": "pass",
      "summary": "The homepage has 1 section link, and every one reaches an element on the page.",
      "homepage": true
    },
    {
      "url": "https://www.redhat.com/en/blog/channel/devops-and-devsecops",
      "reason": "working",
      "status": "pass",
      "summary": "The page at /en/blog/channel/devops-and-devsecops has 1 section link, and every one reaches an element on the page.",
      "homepage": false
    }
  ],
  "reason": "working",
  "readings": [
    {
      "top": 0,
      "url": "https://www.redhat.com/en",
      "working": 1,
      "assessed": 1,
      "examples": [],
      "truncated": false,
      "baseElsewhere": 0,
      "missingTarget": 0,
      "textDirectives": 0,
      "scriptAddresses": 0
    },
    {
      "top": 4,
      "url": "https://www.redhat.com/en/blog/channel/devops-and-devsecops",
      "working": 1,
      "assessed": 1,
      "examples": [],
      "truncated": false,
      "baseElsewhere": 0,
      "missingTarget": 0,
      "textDirectives": 0,
      "scriptAddresses": 0
    }
  ]
}

Related checks

See sites that pass Working section links →
Methodology →

Agent layer · redhat.com

llms.txt

llms.txt is present and well formed

Passes11.3 of 11.3 points

What we found

/llms.txt is well formed: 28 links across 7 sections.

Links
28
Sections
7
Characters
4,366
Document title
Red Hat
Opening summary
Present

Parser findings

No parser errors recorded

File contents are not shown here.

Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "links": 28,
  "title": "Red Hat",
  "errors": [],
  "sections": 7,
  "charLength": 4366,
  "hasSummary": true,
  "sectionsWithLinks": 7
}

Related checks

See sites that pass llms.txt →Check again: llms.txt checker →Guide: How to write a useful llms.txt →
Methodology →

Agent layer · redhat.com

Descriptive llms.txt

llms.txt is descriptive, not a bare link list

Passes7.5 of 7.5 points

What we found

/llms.txt is descriptive: a summary plus descriptions on 100% of links.

Links
28
Characters
4,366
Links with descriptions
28
Opening summary
Present
Additional context
Not found

File contents are not shown here.

Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "links": 28,
  "charLength": 4366,
  "hasDetails": false,
  "hasSummary": true,
  "describedLinks": 28,
  "descriptionRatio": 1,
  "unconventionalSeparators": 0
}

Related checks

See sites that pass Descriptive llms.txt →Check again: llms.txt checker →Guide: How to write a useful llms.txt →
Methodology →

Agent layer · redhat.com

llms-full.txt or .md pages

Serves markdown at its own URL

Fails0 of 12.5 points

What we found

No /llms-full.txt and no markdown versions linked from llms.txt.

Bytes received
0
Markdown links in llms.txt
0

Response receivedHTTP 404

Full-text file
Not usable

How to fix

+12.5score from 57 to 69
Copy the prompt in the owner view →
Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "reason": "none",
  "llmsFullTxt": {
    "status": 404,
    "usable": false,
    "rejected": null,
    "truncated": false,
    "byteLength": 0
  },
  "markdownLinksInLlmsTxt": 0,
  "servesMarkdownOnRequest": false
}

Related checks

See sites that pass llms-full.txt or .md pages →Check again: llms.txt checker →Guide: How to write a useful llms.txt →
Methodology →

Agent layer · redhat.com

Markdown negotiation

Serves markdown when asked for it

Fails0 of 10 points

What we found

Asking the homepage for markdown still returns text/html.

Response characters
1,107,581

Response received

Content-Type: text/html; charset=UTF-8

Vary: Accept
Not found

How to fix

+10score from 69 to 79
Copy the prompt in the owner view →
Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "vary": "Accept-Encoding",
  "pages": [
    {
      "url": "https://www.redhat.com/en",
      "reason": "not-markdown",
      "status": "fail",
      "summary": "Asking the homepage for markdown still returns text/html.",
      "homepage": true
    }
  ],
  "reason": "not-markdown",
  "charset": "UTF-8",
  "variant": null,
  "bodyLength": 1107581,
  "contentType": "text/html; charset=UTF-8",
  "variesOnAccept": false
}

Related checks

See sites that pass Markdown negotiation →Check again: Markdown negotiation checker →Guide: How to serve Markdown to AI agents with content negotiation →
Methodology →

Agent layer · redhat.com

AI crawler rules

States a position on AI crawlers

Fails0 of 5 points

What we found

robots.txt names no AI crawlers, so every operator has to guess.

Named AI crawlers
0
Wildcard rule at /
Does not block crawling

Allowed at /

None recorded

Blocked at /

None recorded

Declared purposes

None recorded

How to fix

The prompt is in Pro →
Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "allowed": [],
  "blocked": [],
  "purposes": [],
  "crawlersNamed": 0,
  "wildcardBlocksEverything": false
}

Related checks

See sites that pass AI crawler rules →Check again: robots.txt checker →Guide: How to write robots.txt rules for AI crawlers →
Methodology →

Agent layer · redhat.com

Content Signals

Declares AI usage preferences

Fails0 of 2.5 points

What we found

No usage declaration found in robots.txt or the final successful homepage response header.

Preference vocabularies

None recorded

Content-Signal declarations

None recorded

Content-Usage declarations

None recorded

How to fix

The prompt is in Pro →
Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "carriers": [],
  "contentUsage": [],
  "vocabularies": [],
  "contentSignal": [],
  "contentUsageHeader": null,
  "recognisedUsageCategories": [],
  "recognisedSignalCategories": []
}

Related checks

See sites that pass Content Signals →Check again: robots.txt checker →Guide: How to write robots.txt rules for AI crawlers →
Methodology →

Agent layer · redhat.com

Typed links

Advertises machine-readable resources with typed links

Passes1.3 of 1.3 points

What we found

Both pages read pass. The homepage points at a markdown version of itself through a Link header.

Each page is checked on its own; the median page decides. The measurements below describe the homepage.

  • Passes: Homepage

    The homepage points at a markdown version of itself through a Link header.

  • Passes: /en/blog/channel/devops-and-devsecops

    The page at /en/blog/channel/devops-and-devsecops points at a markdown version of itself through a Link header.

Links inspected
30

Discovery relations

  • alternate
Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "pages": [
    {
      "url": "https://www.redhat.com/en",
      "reason": "markdown-alternate",
      "status": "pass",
      "summary": "The homepage points at a markdown version of itself through a Link header.",
      "homepage": true
    },
    {
      "url": "https://www.redhat.com/en/blog/channel/devops-and-devsecops",
      "reason": "markdown-alternate",
      "status": "pass",
      "summary": "The page at /en/blog/channel/devops-and-devsecops points at a markdown version of itself through a Link header.",
      "homepage": false
    }
  ],
  "reason": "markdown-alternate",
  "sources": [
    "header",
    "html"
  ],
  "totalLinks": 30,
  "markdownAlternates": [
    {
      "href": "https://www.redhat.com/en/home-page.md",
      "source": "header"
    },
    {
      "href": "https://www.redhat.com/en/home-page.md",
      "source": "html"
    }
  ],
  "meaningfulRelations": [
    "alternate"
  ]
}

Related checks

See sites that pass Typed links →Guide: How to serve Markdown to AI agents with content negotiation →
Methodology →

Penalties · redhat.com

No bot challenge

Serves our crawler without a challenge

PassesPenalty: 0 of 15 points

What we found

Our crawler reaches the page without being challenged.

Response receivedHTTP 200

Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "status": 200
}

Related checks

Methodology →

Penalties · redhat.com

No noindex

The homepage does not block indexing or snippets

PassesPenalty: 0 of 20 points

What we found

Nothing on the homepage tells a crawler to skip it or to withhold its snippet.

Indexing restrictions

None recorded

Snippet restrictions

None recorded

Training opt-outs

None recorded

Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "blocking": [],
  "finalUrl": "https://www.redhat.com/en",
  "redirects": 1,
  "directives": [],
  "ignoredScopes": [],
  "trainingOptOut": [],
  "snippetBlocking": []
}

Related checks

Methodology →

Penalties · redhat.com

No JavaScript wall

Serves its content without JavaScript

PassesPenalty: 0 of 25 points

What we found

The captured homepage HTML contains 1705 content words; completeness is not assessed.

Words in raw HTML
1,705
Script elements
34
Markup characters
1,107,581

Measured from the response HTML, before JavaScript runs.

Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "reason": "text-observed",
  "bodyWords": 2287,
  "truncated": false,
  "scriptCount": 34,
  "contentWords": 1705,
  "markupLength": 1107581,
  "passWordThreshold": 120,
  "hasNoscriptFallback": false,
  "nontextElementCount": 397
}

Related checks

Guide: How to serve content AI crawlers can read without JavaScript →
Methodology →

Penalties · redhat.com

AI search bots let in

Allows search and user-fetch crawlers

PassesPenalty: 0 of 25 points

What we found

robots.txt allows every known search and user-fetch crawler to reach the homepage.

Blocked crawlers
0
Path checked
/

Blocked crawlers

None recorded

Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "path": "/",
  "capped": false,
  "blocked": [],
  "blockedCount": 0,
  "penaltyPoints": 0
}

Related checks

Check again: robots.txt checker →Guide: How to write robots.txt rules for AI crawlers →
Methodology →

Penalties · redhat.com

HTTPS and HTTP 200

Serves the homepage over HTTPS with HTTP 200

PassesPenalty: 0 of 10 points

What we found

The homepage is served over HTTPS and returns HTTP 200.

Response receivedHTTP 200

https://redhat.com

Final URL: https://www.redhat.com/en

Final connection
HTTPS
Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "error": null,
  "secure": true,
  "status": 200,
  "finalUrl": "https://www.redhat.com/en",
  "requestedUrl": "https://redhat.com"
}

Related checks

Methodology →

Penalties · redhat.com

Title and description

Provides a title and meta description

PassesPenalty: 0 of 3 points

What we found

The homepage provides both a non-empty title and meta description.

Title elements
1
Meta descriptions
1

Page metadata

Red Hat - We make open source technologies for the enterprise

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

Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "title": "Red Hat - We make open source technologies for the enterprise",
  "titleCount": 1,
  "description": "Red Hat is the world’s leading provider of enterprise open source solutions, including high-performing Linux, cloud, container, and Kubernetes technologies.",
  "descriptionCount": 1
}

Related checks

Methodology →

Penalties · redhat.com

Two redirects at most

Reaches the homepage within two redirects

PassesPenalty: 0 of 3 points

What we found

The homepage is reached in 1 redirect.

Redirects
1

Response received

https://redhat.com

Final URL: https://www.redhat.com/en

Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "finalUrl": "https://www.redhat.com/en",
  "redirects": 1,
  "threshold": 2,
  "requestedUrl": "https://redhat.com"
}

Related checks

Methodology →

Penalties · redhat.com

Answers within 3 s

Returns the homepage within three seconds

PassesPenalty: 0 of 3 points

What we found

The homepage reached a plain crawler in 389 ms.

Response time
389 ms
Direct attempts
1
Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "durationMs": 389,
  "thresholdMs": 3000,
  "directAttempts": 1
}

Related checks

Methodology →

Agent capabilities · redhat.com

API catalog

Publishes an API catalog

Passes+1 on the badge

What we found

Publishes an API catalog describing 1 API.

Response receivedHTTP 200

Content-Type: application/linkset+json; profile="https://www.rfc-editor.org/info/rfc9727"

Advertised via

None recorded

Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "apis": 1,
  "links": 11,
  "relations": [
    "alternate",
    "service-desc"
  ],
  "wellKnown": {
    "status": 200,
    "problem": null,
    "profile": "https://www.rfc-editor.org/info/rfc9727",
    "contentType": "application/linkset+json; profile=\"https://www.rfc-editor.org/info/rfc9727\""
  },
  "advertisedVia": []
}

Related checks

See sites that pass API catalog →
Methodology →

Agent capabilities · redhat.com

auth.md

Publishes an auth.md for agents

Not applicableAdds +1 to the badge when found

What we found

No /auth.md published.

Response receivedHTTP 404

Content-Type: text/plain

Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "error": null,
  "reason": "absent",
  "status": 404,
  "contentType": "text/plain"
}

Related checks

See sites that pass auth.md →
Methodology →

Agent capabilities · redhat.com

MCP server card

Lists an MCP server card in its AI Catalog

Not applicableAdds +1 to the badge when found

What we found

No AI Catalog published, so no MCP server card can be discovered.

Catalog entries
0

Response receivedHTTP 404

Discovery result
absent
Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "reason": "absent",
  "catalog": {
    "status": 404,
    "entries": 0,
    "problem": "absent",
    "contentType": null,
    "specVersion": null,
    "malformedEntries": 0
  }
}

Related checks

See sites that pass MCP server card →
Methodology →

Agent capabilities · redhat.com

A2A agent card

Publishes an A2A Agent Card

Not applicableAdds +1 to the badge when found

What we found

No A2A Agent Card at /.well-known/agent-card.json, and none listed in an AI Catalog.

Catalog entries
0

Response receivedHTTP 404

Content-Type: text/html; charset=UTF-8

Discovery result
absent
Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "cards": [
    {
      "via": "well-known",
      "name": null,
      "error": null,
      "notes": [],
      "shape": null,
      "skills": 0,
      "source": "https://redhat.com/.well-known/agent-card.json",
      "status": 404,
      "usable": false,
      "problem": "absent",
      "version": null,
      "bindings": [],
      "identifier": null,
      "interfaces": []
    }
  ],
  "reason": "absent",
  "catalog": {
    "status": 404,
    "entries": 0,
    "problem": "absent"
  },
  "wellKnown": {
    "status": 404,
    "problem": "absent",
    "contentType": "text/html; charset=UTF-8"
  }
}

Related checks

See sites that pass A2A agent card →
Methodology →

Agent capabilities · redhat.com

Agent Skills index

Publishes an Agent Skills index

Not applicableAdds +1 to the badge when found

What we found

No usable Agent Skills index was found at either well-known path or in the AI Catalog.

Artifact verification
not-performed
Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "reason": "absent",
  "catalog": {
    "status": 404,
    "problem": "absent",
    "individualSkills": 0
  },
  "indexes": [
    {
      "via": "well-known",
      "error": null,
      "notes": [],
      "total": 0,
      "format": null,
      "issues": [],
      "schema": null,
      "source": "https://redhat.com/.well-known/agent-skills/index.json",
      "status": 404,
      "usable": 0,
      "entries": [],
      "problem": "absent",
      "rejected": 0,
      "identifier": null
    },
    {
      "via": "well-known",
      "error": null,
      "notes": [],
      "total": 0,
      "format": null,
      "issues": [],
      "schema": null,
      "source": "https://redhat.com/.well-known/skills/index.json",
      "status": 404,
      "usable": 0,
      "entries": [],
      "problem": "absent",
      "rejected": 0,
      "identifier": null
    }
  ],
  "artifactVerification": "not-performed"
}

Related checks

See sites that pass Agent Skills index →
Methodology →

Agent capabilities · redhat.com

WebMCP

Declares WebMCP tools for browser agents

Not applicableAdds +1 to the badge when found

What we found

No WebMCP declarations were found in the collected HTML or inline scripts. External scripts were not inspected.

Pages checked
2
Declarations
0
Usable declarations
0
Detection method
static
Runtime verification
not-performed
Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "pages": [
    {
      "key": "homepage",
      "url": "https://www.redhat.com/en",
      "secure": true,
      "usable": 0,
      "truncated": false,
      "references": 0,
      "parseErrors": 0,
      "declarations": 0
    },
    {
      "key": "page:https://www.redhat.com/en/blog/channel/devops-and-devsecops",
      "url": "https://www.redhat.com/en/blog/channel/devops-and-devsecops",
      "secure": true,
      "usable": 0,
      "truncated": false,
      "references": 0,
      "parseErrors": 0,
      "declarations": 0
    }
  ],
  "reason": "absent",
  "detection": "static",
  "pageCount": 2,
  "references": [],
  "parseErrors": 0,
  "usableCount": 0,
  "declarations": [],
  "referenceCount": 0,
  "declarationCount": 0,
  "runtimeVerification": "not-performed"
}

Related checks

See sites that pass WebMCP →
Methodology →

Agent capabilities · redhat.com

Web Bot Auth

Publishes a Web Bot Auth key directory

Not applicableAdds +1 to the badge when found

What we found

No Web Bot Auth key directory at /.well-known/http-message-signatures-directory.

Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "keys": {
    "total": 0,
    "sample": [],
    "usable": 0,
    "testKeys": 0,
    "evaluated": 0,
    "privateMaterial": 0
  },
  "notes": [
    "media-type",
    "redirected",
    "unsigned"
  ],
  "shape": null,
  "reason": "absent",
  "signature": {
    "total": 0,
    "status": "absent",
    "ignored": 0,
    "coverage": null,
    "malformed": false,
    "signatures": []
  },
  "wellKnown": {
    "status": 404,
    "problem": "absent",
    "finalUrl": "https://www.redhat.com/.well-known/http-message-signatures-directory",
    "redirects": 1,
    "contentType": null
  },
  "extraMembers": [],
  "signatureAgent": "https://www.redhat.com"
}

Related checks

See sites that pass Web Bot Auth →
Methodology →

Agent capabilities · redhat.com

x402 / MPP payments

Accepts agent payments with x402 or MPP

Not applicableAdds +1 to the badge when found

What we found

No HTTP 402 payment challenge on the homepage or robots.txt, and no manifest at /.well-known/x402.

Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "reason": "absent",
  "manifest": {
    "kind": null,
    "notes": [],
    "shape": null,
    "status": 404,
    "problem": "absent",
    "finalUrl": "https://www.redhat.com/.well-known/x402",
    "resources": {
      "total": 0,
      "sample": [],
      "skipped": {},
      "eligible": 0,
      "examined": 0
    },
    "contentType": null
  },
  "protocols": [],
  "responses": [],
  "verification": null,
  "paymentVerification": "not-performed"
}

Related checks

See sites that pass x402 / MPP payments →
Methodology →

Agent capabilities · redhat.com

ACP commerce

Publishes ACP discovery metadata

Not applicableAdds +1 to the badge when found

What we found

No ACP discovery declaration established at /.well-known/acp.json.

Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "api": false,
  "key": "well-known-acp",
  "issues": [],
  "marked": false,
  "reason": "absent",
  "status": 404,
  "usable": false,
  "problem": "absent",
  "version": null,
  "commerce": false,
  "services": [],
  "transports": [],
  "capabilities": [],
  "transactionVerification": "not-performed"
}

Related checks

See sites that pass ACP commerce →
Methodology →

Agent capabilities · redhat.com

UCP commerce

Publishes UCP discovery metadata

Not applicableAdds +1 to the badge when found

What we found

No UCP discovery declaration established at /.well-known/ucp.

Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "api": false,
  "key": "well-known-ucp",
  "issues": [],
  "marked": false,
  "reason": "absent",
  "status": 404,
  "usable": false,
  "problem": "absent",
  "version": null,
  "commerce": false,
  "services": [],
  "transports": [],
  "capabilities": [],
  "transactionVerification": "not-performed"
}

Related checks

See sites that pass UCP commerce →
Methodology →

Agent capabilities · redhat.com

AMP discovery

Publishes AMP discovery metadata

Not applicableAdds +1 to the badge when found

What we found

No public AMP discovery declaration established. Private or hidden agents may not advertise one to our crawler.

Response receivedHTTP 404

https://redhat.com/.well-known/agent.json

Final URL: https://www.redhat.com/.well-known/agent.json

Content-Type: text/html; charset=UTF-8

Discovery source
native
Declaration location
https://www.redhat.com/.well-known/agent.json

Declared agent addresses

No usable addresses recorded

Declaration issues

No issues recorded

Discovery documents

  • https://www.redhat.com/.well-known/agent.json · absent

Discovery only. Messaging, health, identity ownership and extension activation were not tested. This does not establish Level 0 conformance.

Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "reason": "absent",
  "selected": {
    "via": "native",
    "issues": [],
    "marked": false,
    "source": "https://www.redhat.com/.well-known/agent.json",
    "status": 404,
    "usable": false,
    "problem": "absent",
    "version": null,
    "endpoint": null,
    "finalUrl": "https://www.redhat.com/.well-known/agent.json",
    "contentType": "text/html; charset=UTF-8",
    "identifiers": [],
    "requestedUrl": "https://redhat.com/.well-known/agent.json",
    "lifecycleStatus": null
  },
  "declarations": [
    {
      "via": "native",
      "issues": [],
      "marked": false,
      "source": "https://www.redhat.com/.well-known/agent.json",
      "status": 404,
      "usable": false,
      "problem": "absent",
      "version": null,
      "endpoint": null,
      "finalUrl": "https://www.redhat.com/.well-known/agent.json",
      "contentType": "text/html; charset=UTF-8",
      "identifiers": [],
      "requestedUrl": "https://redhat.com/.well-known/agent.json",
      "lifecycleStatus": null
    }
  ],
  "runtimeVerification": "not-performed"
}

Related checks

See sites that pass AMP discovery →Check again: Agent Mesh Protocol checker →Guide: How to publish Agent Mesh Protocol discovery →
Methodology →

Site profile

Login
Not established
API
Detected
An API catalog
Commerce
Not established

It decides which conditional checks apply. “Not established” means no proof in what we read, not proof of absence.

Access & usage policy

Who can read this page, and for what purpose?

GoodForBotsBot received HTTP 200 via a direct request. No indexing restriction was observed in the supported homepage directives.

Sampled URL: https://www.redhat.com/en

Declared crawling rules

No matching refusal for this URL was found for the listed identities.

Sources and scope: declared crawling rules

  • Declared allow · Scan admission

    • GoodForBotsBot/1.0 (+https://goodforbots.com/bot)

    The recorded robots admission decision allowed our crawler to proceed.

    GoodForBotsBot admission along the homepage request chain

    https://redhat.com/

    robots.txt is present and valid

  • Declared allow · robots.txt

    • goodforbotsbot (Site diagnostics)
    • * (Default robots group)
    • oai-searchbot (ai-search)
    • claude-searchbot (ai-search)
    • perplexitybot (ai-search)
    • mistralai-index (ai-search)
    • kimi-searchbot (ai-search)
    • amzn-searchbot (ai-search)
    • meta-webindexer (ai-search)
    • exasearchbot (ai-search)
    • aiwebindex (ai-search)
    • duckassistbot (ai-search)
    • shapbot (ai-search)
    • yandexadditional (ai-search)
    • yandexadditionalbot (ai-search)
    • gptbot (ai-training)
    • claudebot (ai-training)
    • mistralai-training (ai-training)
    • kimibot (ai-training)
    • ai2bot (Unknown)
    • applebot-extended (ai-training)
    • webzio-extended (ai-training)
    • chatgpt-user (user-fetch)
    • claude-user (user-fetch)
    • perplexity-user (user-fetch)
    • mistralai-user (user-fetch)
    • kimi-user (user-fetch)
    • amzn-user (user-fetch)
    • diffbot-user (user-fetch)
    • firecrawlagent (extraction)
    • webzio (extraction)
    • meta-externalfetcher (user-fetch, agent)
    • google-extended (ai-training, grounding)
    • meta-externalagent (ai-training, product-improvement)
    • amazonbot (ai-training, product-improvement)
    • ccbot (open-dataset, ai-training)
    • googlebot (search)
    • bingbot (search)

    No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.

    Acquisition of https://www.redhat.com/en

    https://www.redhat.com/robots.txt

    User-agent: *

    robots.txt is present and validStates a position on AI crawlersAllows search and user-fetch crawlers

Observed access

GoodForBotsBot received HTTP 200 via a direct request.

Sources and scope: observed access
Coverage and interpretation
  • Crawler coverage includes the registered identities and up to 50 user-agent entries from robots.txt. Source excerpts and detail groups are bounded; omissions are labelled.
  • Observed access describes GoodForBotsBot only. Other crawler entries describe declared rules, not tests of those operators' access.
  • Coverage is the sampled homepage response and collected robots.txt files. No indexing or citation is guaranteed. Usage preferences are declarations, not a legal determination of permission.
  • This explanation adds no points or penalties. Any score effects belong to the linked checks.
  • AIPREF and Content Signals keep their own definitions. AIPREF search can include processing used exclusively for search; training preferences are not a blanket ruling on every search process.

Scan details

Every scan is kept. Pro draws the history as a chart →

Scanned
7 Nov 2026
Rubric
0.9.0
Requests
23
Fetched
6.8 MB
Took
246.7 s
Homepage
389 ms · direct
Pages read
2
robots.txt
allowed
Which pages the scan read

The homepage and up to three pages from the sitemap and homepage links. Structured data, page structure, Markdown negotiation and typed links check each page read and take the median page; other checks read the homepage.

  • Homepagealways read
  • /en/blog/channel/devops-and-devsecopsarticle · linked from the homepage · read
  • /en/products/aiproduct · linked from the homepage · not read: the scan's request budget ran out
  • /en/solutions/security-and-compliance-approachservice · linked from the homepage · not read: the scan's request budget ran out

Similar reports

The whole directory →

Also Fair

Volanea

volanea.com

Transactional email, campaigns, and automation API with AI agent support

SaaS Cubes

saascubes.com

Curated SaaS directory offering permanent do-follow backlinks for modern software products

Good for Bots

goodforbots.com

Evaluates website readability for AI crawlers and language models with a scoring rubric

Also Fair

Intertakt

intertakt.com

Interval timer app with voice cues and background audio for workouts

Also Fair

tracerHQ

tracerhq.co

SEO-to-revenue attribution platform connecting search data to signups and MRR for SaaS teams

Do you run redhat.com? Open the owner view → Removing the listing is free. Remove →