github.comscanned May 22, 2026 · 16:331.44s
Public AI visibility report

github.comAI visibilityPoor

This site is difficult for AI tools to read right now.

Key strengths include AI guidance file, while plain-text page access and sitemap need attention.

Recommended next step

make the homepage respond successfully to requests with Accept: text/markdown, either by serving markdown directly or by adding a markdown variant URL with correct content negotiation.

Why monitor after one scan?

AI visibility changes when teams ship new pages, edit pricing or docs, update sitemaps, or change crawler rules. Weekly monitoring catches those silent regressions before answer engines and agents start reading stale or broken signals.

Monitor weekly

Overall score

38/100
Poor
Go to fixesOverall position374 out of 491Leaderboard

// score breakdown

Points by check

8 checks

Crawlability10/20
Robots.txt7.5/15
llms.txt15/15
Sitemap0/10
Markdown support0/15
Semantic HTML5.7/10
Structured data0/10
Content signals0/5
1pass3warn4fail

Public link

llmscan.dev/scan/_3Mts9lCD1ROyjNr5rjLt

Signals checked

8 AI visibility signals

Fix bundle

4 copy-ready files

Share badge

Poor · 38/100

Add a polished proof badge

A compact badge for footer, press, or trust sections that links visitors to this public report.

Embed codellmscan.dev/scan/_3Mts9lCD1ROyjNr5rjLt
<a href="https://www.llmscan.dev/scan/_3Mts9lCD1ROyjNr5rjLt"
  target="_blank"
  rel="noopener"
>
  <img
    src="https://www.llmscan.dev/scan/_3Mts9lCD1ROyjNr5rjLt/badge.png"
    alt="LLM Scan AI visibility score badge"
    width="460"
    height="120"
    style="width: 260px; max-width: 100%; height: auto;"
  />
</a>
Open badge
L
LLM Scan
Poor
Score
38/100

Share your score

Post the public report with: “We scored 38/100 for AI-readability.”

Download fixes

Grab generated files and implementation notes for the highest-impact gaps.

Rescan weekly

Save this domain to catch regressions after content, sitemap, or robots changes.

Monitor weekly

// signal breakdown

8 signals AI systems depend on

The homepage is reachable, but robots.txt contains AI crawler restrictions for GPTBot, ChatGPT-User, ClaudeBot, Claude-Web, PerplexityBot, and Google-Extended.

Signal weight

10/20
Warn

Evidence

url
https://github.com/
finalUrl
https://github.com/
status
200

Recommendation

Next step: Review AI crawler Disallow rules and keep only the paths that should be excluded from AI crawler access; serve a non-empty HTML homepage with a canonical link tag.

robots.txt contains AI-crawler path blocks for GPTBot, ChatGPT-User, ClaudeBot, Claude-Web, PerplexityBot, and Google-Extended.

Signal weight

8/15
Warn

Evidence

robotsTxtUrl
https://github.com/robots.txt
exists
true
rawRobotsTxt
# If you would like to crawl GitHub contact us via https://support.github.com?tags=dotcom-robots # We also provide an extensive API: https://docs.github.com User-agent: bingbot Disallow: /ekansa/Open-Context-Data Disallow: /ekansa/opencontext-* Disallow: /account-login Disallow: */tarball/ Disallow: */zipball/ Disallow: /Explodingstuff/ Disallow: /copilot/ Disallow: /copilot/c/ User-agent: adidxbot Disallow: /ekansa/Open-Context-Data Disallow: /ekansa/opencontext-* Disallow: /account-login Disallow: */tarball/ Disallow: */zipball/ Disallow: /Explodingstuff/ Disallow: /copilot/ Disallow: /copilot/c/ User-agent: BingPreview Disallow: /ekansa/Open-Context-Data Disallow: /ekansa/opencontext-* Disallow: /account-login Disallow: */tarball/ Disallow: */zipball/ Disallow: /Explodingstuff/ Disallow: /copilot/ Disallow: /copilot/c/ User-agent: baidu crawl-delay: 1 User-agent: * Disallow: /*/*/pulse Disallow: /*/*/projects Disallow: /*/*/forks Disallow: /*/*/issues/new Disallow: /*/*/milestones/new Disallow: /*/*/issues/search Disallow: /*/*/commits/ Disallow: /*/*/branches Disallow: /*/*/contributors Disallow: /*/*/tags Disallow: /*/*/stargazers Disallow: /*/*/watchers Disallow: /*/*/network Disallow: /*/*/graphs Disallow: /*/*/compare Disallow: /*/tree/ Disallow: /gist/ Disallow: /*/download Disallow: /*/revisions Disallow: /*/commits/*?author Disallow: /*/commits/*?path Disallow: /*/comments Disallow: /*/archive/ Disallow: /*/blame/ Disallow: /*/raw/ Disallow: /*/cache/ Disallow: /.git/ Disallow: */.git/ Disallow: /*.git$ Disallow: /search/advanced Disallow: /search$ Disallow: /*q= Disallow: /*.atom$ Disallow: /ekansa/Open-Context-Data Disallow: /ekansa/opencontext-* Disallow: */tarball/ Disallow: */zipball/ Disallow: /*source=* Disallow: /*ref_cta=* Disallow: /*plan=* Disallow: /*return_to=* Disallow: /*ref_loc=* Disallow: /*setup_organization=* Disallow: /*source_repo=* Disallow: /*ref_page=* Disallow: /*source=* Disallow: /*referrer=* Disallow: /*report=* Disallow: /*author=* Disallow: /*since=* Disallow: /*until=* Disallow: /*commits?author=* Disallow: /*report-abuse?report=* Disallow: /*tab=* Allow: /*?tab=achievements&achievement=* Disallow: /account-login Disallow: /Explodingstuff/ Disallow: /copilot/ Disallow: /copilot/c/

Recommendation

Next step: Review AI crawler Disallow rules and keep only the paths that should be excluded from AI crawler access.

The llms.txt file was found and includes the expected text, length, heading, and URL signals.

Signal weight

15/15
Pass

Evidence

llmsTxtUrl
https://github.com/llms.txt
present
true
accessible
true

No accessible XML sitemap was found for this site.

Signal weight

0/10
Fail

Evidence

sitemapUrl
https://github.com/sitemap.xml
sitemapUrls
[https://github.com/sitemap.xml]
robotsSitemapUrls
[]

Recommendation

Next step: Publish a valid XML sitemap at /sitemap.xml and reference it from robots.txt so crawlers and AI systems can discover important URLs.

The homepage could not be fetched with a markdown Accept header.

Signal weight

0/15
Fail

Evidence

url
https://github.com/
acceptHeader
text/markdown
status
406

Recommendation

Next step: Make the homepage respond successfully to requests with Accept: text/markdown, either by serving markdown directly or by adding a markdown variant URL with correct content negotiation.

The homepage has some semantic HTML signals, but one or more title, metadata, heading, landmark, content, or link text checks need improvement.

Signal weight

6/10
Warn

Evidence

url
https://github.com/
quality
partial
score
57

Recommendation

Next step: Shorten the meta description to 160 characters or fewer. Use exactly one h1 element and move secondary section titles to h2-h6. Add missing semantic elements: article.

No JSON-LD, Microdata, or RDFa structured data was found on the page.

Signal weight

0/10
Fail

Evidence

url
https://github.com/
quality
none
hasStructuredData
false

Recommendation

Next step: Add JSON-LD structured data with Organization or WebSite schema so AI systems can identify the site owner or website entity.

Content-Signal directive not detected in headers, HTML metadata, or robots.txt.

Signal weight

0/5
Fail

Evidence

url
https://github.com/
hasContentSignals
false
hasContentSignalHeader
false

Recommendation

Next step: Add the standard directive 'Content-Signal: ai-train=no, search=yes, ai-input=yes' to robots.txt, HTML metadata, or HTTP headers so AI systems can discover content usage preferences.

// generated fixes

Downloadable fix files

Preview the generated files below. Enter your email to reveal the full fixes, download the bundle, or copy the agent-ready implementation prompt.

Done-for-you

Agency package

Not sure how to ship the technical fixes? Book a call and we can help turn this report into implemented updates.

Fix planning from your scan

Implementation guidance

AI visibility monitoring

llms.txtMarkdown
# GitHub · Change is constant. GitHub keeps you ahead. · GitHub > Join the world's most widely adopted, AI-powered developer platform where millions of developers, businesses, and the largest open source community build software that advances humanity. This llms.txt file summarizes the public, canonical resources that AI assistants and crawlers should use to understand this site. ## Site Overview - Canonical URL: https://github.com/- Site type: website
robots.txtTXT
# robots.txt additions# Copy these blocks into the existing robots.txt file. Keep current rules unless a note calls out a conflicting Disallow. # Sitemap discovery# Add this top-level directive so search and AI crawlers can discover the canonical sitemap.Sitemap: https://github.com/sitemap.xml # AI crawler access# Add explicit Allow rules for blocked AI crawlers; remove or narrow conflicting Disallow rules if your crawler target requires precedence.User-agent: GPTBot
schema.jsonJSON
{  "@context": "https://schema.org",  "@graph": [    {      "@type": "Organization",      "@id": "https://github.com/#organization",      "name": "GitHub · Change is constant. GitHub keeps you ahead. · GitHub",      "description": "Join the world's most widely adopted, AI-powered developer platform where millions of developers, businesses, and the largest open source community build software that advances humanity.",      "url": "https://github.com/",      "logo": "https://github.githubassets.com/favicons/favicon.png",
head metaHTML
# Content-Signal recommendations Use these directives to make AI-use preferences explicit for compliant crawlers and AI systems. They are advisory signals, so keep them aligned with robots.txt, terms, and access controls. ## Recommended values - ai-train=no: AI model training, fine-tuning, and dataset creation.- search=yes: AI search indexing, snippets, and discovery.- ai-input=yes: AI answer grounding, retrieval, and generated-response context.