Skip to content
geo/aeoplaybooks
Explore

github.com ranks 9 of 10 in panel, score 35/100

On 2026-11-20, github.com scored 35/100, ranking 9th in a 10-site panel.

How this note was made: an LLM drafted it automatically from our own probe logs (the hourly GEO Pulse data), and it was published without line-by-line human editing. Every number comes from those logs; the method is on the methodology page.

GEO & AEO Playbooks github.com ranks 9 of 10 in panel, score 35/100 geo/aeo playbooks · independent GEO lab

GitHub's score of 35/100 on November 20, 2026, places it 9th out of 10 in our panel of well-known sites. This low score is primarily due to technical issues affecting crawler access and schema detection, rather than a lack of AI mentions or citations.

What Did the Probe Detect on github.com?

Our probe encountered significant challenges when assessing github.com. The homepage returned an HTTP 429 status, indicating that the server was overwhelmed or refusing connections from our AI crawler. This impeded our ability to retrieve the site cleanly and assess its AI-related content. While the site does not block GPTBot, ClaudeBot, PerplexityBot, Google-Extended, or CCBot, the actual access paths for these crawlers might differ, affecting their reachability.

Additionally, the probe could not detect any JSON-LD schema on the homepage due to access issues. This absence means we cannot evaluate the site's structured data, which is crucial for AI and search engine optimization.

How Has github.com's Score Varied Over Time?

The probe history for github.com shows a fluctuating performance, with scores ranging from 20 to 80 out of 100 since July 13, 2026. Recent readings have been particularly volatile, with scores swinging from 35 to 70 within the same day. This inconsistency suggests intermittent technical issues affecting the site's accessibility and performance.

108probes recorded
20-80observed range
35current score

How Does github.com Compare to Other Sites in the Panel?

In the context of our 10-site panel, github.com ranks 9th with a score of 35/100. The panel's average score is 73.8, with a median of 90, highlighting GitHub's underperformance relative to its peers. Sites like cloudflare.com, stripe.com, and vercel.com achieved perfect scores of 100/100, demonstrating robust technical setups and accessibility.

Common issues across the panel include AI-crawler reachability, which all sites struggle with, suggesting a broader industry challenge. However, GitHub's specific issues with HTTP 429 responses and schema detection are more severe than those faced by most other panel members.

What Should a Normal Business Site Learn from This?

For any business site, ensuring reliable access for AI crawlers is critical. Technical barriers like HTTP 429 responses can severely impact a site's visibility and performance in AI-driven search environments. Maintaining a clear and accessible /llms.txt file is also essential, as it guides AI crawlers on how to interact with the site.

Additionally, implementing and maintaining a robust JSON-LD schema can enhance a site's discoverability and relevance in search results. Business sites should regularly audit their technical infrastructure to prevent access issues and ensure they meet the evolving standards of AI and search engine technologies.

For more detailed guidance on AI crawler access and /llms.txt implementation, refer to our AI crawler playbook and llms.txt guide . These resources provide comprehensive strategies to optimize site accessibility and performance in AI-driven environments.

Run the same 5-signal probe on your own domainThis note came out of the hourly GEO Pulse board. The free checker runs the identical probe on any site, and Monitor re-runs it every month.

No comments yet