Is github.com AI agent ready? C · 55/100
Scan history · 5 public scans of github.com
4 failed · 2 partial out of 11 that apply to your site.
Fix automatically with AIScan
6 open checks (4 failing) can be handed to an AI agent: D1, D2, C1, C3, B2, E5. Pick one route — each returns the full, check-by-check instructions.
npx add-skill https://aiscan.site/aiscan-skill.jsonThen ask your agent: “Fix the failing AI readiness checks for https://github.com/”.
curl -o CLAUDE.md https://aiscan.site/CLAUDE.mdDrop it in your project root, then ask Claude Code to fix the failing AIScan checks.
https://aiscan.site/api/mcpTools: scan_website, get_fixes, get_grade. Call get_fixes { "url": "https://github.com/" }.
curl -s 'https://aiscan.site/api/public/scan?url=https%3A%2F%2Fgithub.com%2F'Returns every check with its complete fix guide.
Verify: Re-scan at https://aiscan.site after applying fixes, or run npx aiscan-cli https://github.com/. Individual checks that need a specific probe list it in their own guide.
Quick Wins
Top 3 fixes ranked by score impact
- 01Fail+8 pts if fixed
Markdown content negotiation
See full detailsServe text/markdown when the client sends Accept: text/markdown, or publish /index.md.
- 02Fail+5 pts if fixed
Explicit AI bot rules
See full detailsAdd explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.
- 03Fail+4 pts if fixed
XML sitemap
See full detailsPublish /sitemap.xml and reference it in robots.txt.
# Agent-readiness remediation brief Site: https://github.com/ Platform: unknown (0% confidence) AIScan score: 55/100 — Level 3 (Governed) Rubric: v2026.08.2 ## Failing checks (sorted by weight) - **[C1] Markdown content negotiation** — FAIL - Evidence: Accept: text/markdown → 406 (text/html; charset=utf-8) - Fix: Serve text/markdown when the client sends Accept: text/markdown, or publish /index.md. - **[D1] robots.txt present & sane** — PARTIAL - Evidence: 200 OK, 2274 bytes - Fix: Serve a non-blocking /robots.txt that references your Sitemap. - **[B2] Explicit AI bot rules** — FAIL - Evidence: 0 known AI agent(s) addressed in robots.txt - Fix: Add explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc. - **[D2] XML sitemap** — FAIL - Evidence: no /sitemap.xml or /sitemap_index.xml resolved - Fix: Publish /sitemap.xml and reference it in robots.txt. - **[C3] Structured HTML (title, meta, JSON-LD, single H1)** — PARTIAL - Evidence: h1: 1, title: true, meta description: true, JSON-LD: false - Fix: Ensure a single <h1>, <title>, meta description, and schema.org JSON-LD. - **[E5] Content feed (RSS / Atom / JSON Feed)** — FAIL - Evidence: no RSS, Atom or JSON Feed found at the conventional paths - Fix: Publish an RSS, Atom, or JSON Feed of new content and declare it in <head> with <link rel="alternate" type="application/rss+xml">. Feeds give agents a cheap, dated changelog of your site that a sitemap doesn't. ## General guidance - Static-first: `robots.txt`, `llms.txt`, `/.well-known/*` JSON cards. - Markdown negotiation: serve `text/markdown` when requested via `Accept` header or `?format=md`. - Bot access: explicit allow/deny per AI user-agent (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, Applebot-Extended, Bytespider, Amazonbot, CCBot, meta-externalagent, cohere-ai, Diffbot). - Capabilities: publish an MCP server card and (optionally) an Agent Skills manifest even if the runtime isn't live — discovery first. - Re-scan at aiscan.site after deploying.
How this score is calculated
Every check earns points against a weight. We divide the points you earned by the points that actually apply to a site like yours — so checks that don't apply never drag you down.
Baseline every site should meet.
Strong signals most sites benefit from.
Emerging standards. Can only add points.
Not counted (7): B1, B3, P1, P2, P3, P4, E2 — either not applicable to this site profile or optional and not yet adopted. Expand any check to see the exact evidence we based it on.
Discoverability
71Can agents find your pages? robots, sitemaps, llms.txt.
Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · D2
What we foundno /sitemap.xml or /sitemap_index.xml resolved
Measured againstHow to fix itPublish /sitemap.xml and reference it in robots.txt.
Generate a sitemap
Most frameworks have a built-in sitemap generator (Next.js:
app/sitemap.ts, TanStack: a route at/sitemap.xml). Publish all public URLs.Reference it in robots.txt
Sitemap: https://yoursite.com/sitemap.xml
Content
52Can agents read your content cleanly? Markdown, structured data.
Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · C1
What we foundAccept: text/markdown → 406 (text/html; charset=utf-8)
How to fix itServe text/markdown when the client sends Accept: text/markdown, or publish /index.md.
Serve text/markdown on Accept negotiation
When a client sends
Accept: text/markdown, return a markdown rendering of the same content. The simplest path is to publish parallel.mdfiles (e.g./about→/about.md) and rewrite based on the Accept header.Test it
curl -H "Accept: text/markdown" https://yoursite.com/
Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · E5
What we foundno RSS, Atom or JSON Feed found at the conventional paths
Measured againstHow to fix itPublish an RSS, Atom, or JSON Feed of new content and declare it in <head> with <link rel="alternate" type="application/rss+xml">. Feeds give agents a cheap, dated changelog of your site that a sitemap doesn't.
Publish a feed
RSS, Atom, or JSON Feed — any of them gives agents a cheap, dated changelog of new content that a sitemap can't.
Declare it in <head>
<link rel="alternate" type="application/rss+xml" title="Blog" href="/feed.xml" />
Keep dates accurate
Each item needs a real publish date; that's the freshness signal agents actually use.
Bot Access
0Are AI crawlers explicitly allowed or blocked?
Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · B2
What we found0 known AI agent(s) addressed in robots.txt
Measured againstHow to fix itAdd explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.
Add explicit User-agent blocks
Don't rely on
User-agent: *alone. Address each major AI crawler so your policy is unambiguous.Recommended block
User-agent: GPTBot Allow: / User-agent: ClaudeBot Allow: / User-agent: PerplexityBot Allow: / User-agent: Google-Extended Allow: / User-agent: Applebot-Extended Allow: /
Share as a social image
Download a 1200×630 social card or post straight to X, LinkedIn or Facebook — sized for every feed.
Tip: for X and LinkedIn, upload the downloaded PNG with your post so the card shows in the feed. Posts that include just the link will still preview AIScan.site.
Embed your AIScan badge
Drop this badge into your site footer, GitHub README, or docs. It links back to a fresh scan of github.com on AIScan.site.
<!-- AIScan.site agent-readiness badge --> <a href="https://aiscan.site/?u=https%3A%2F%2Fgithub.com%2F" target="_blank" rel="noopener" title="Agent-Readiness Grade C (55/100) — AIScan.site"> <img src="https://aiscan.site/api/public/badge.svg?score=55&grade=C&host=github.com" alt="AIScan.site Grade C — 55/100" width="240" height="64" loading="lazy" /> </a>
[](https://aiscan.site/?u=https%3A%2F%2Fgithub.com%2F)
Create a free account to track this site over time
- Save scan history
- See score trends
- Re-scan anytime
Dig deeper
github.com is built on Custom / Unknown. AI-agent readiness for custom and unrecognised stacks walks through the same checks on that platform.
This page always shows the most recent public scan for github.com.