On 2026-08-12, github.com achieved a score of 80/100, placing it 5th out of 10 in a panel of well-known sites. This score reflects strong visibility, with AI engines able to read and cite content from the site, despite a missing JSON-LD schema on the homepage.
How does github.com perform in our historical probes?
Our probe history for github.com shows a stable performance, with scores ranging from 65 to 80 out of 100 across 10 probes since 2026-07-13. The most recent readings indicate a consistent score of 80 on 2026-08-07 and 2026-08-03, interspersed with occasional dips to 70. This suggests that while github.com maintains a strong presence, there are periodic fluctuations that might be worth monitoring.
What did the latest probe reveal?
The latest probe highlights that github.com has strong visibility, with 4 out of 5 core signals passing. AI-crawler reachability is confirmed as the homepage returns HTTP 200 with approximately 6,872 characters of server-rendered text, making it accessible to retrieval bots. Additionally, major AI crawlers like GPTBot, ClaudeBot, and PerplexityBot can fetch key pages, as there is no blanket disallow in place. The presence of a well-formed /llms.txt file, sized at 28,757 bytes, further aids engines in mapping the site's content. However, the absence of a JSON-LD schema on the homepage is a notable gap, as it prevents engines from identifying the type of entity the site represents.
How does github.com compare within the panel?
Within the panel, github.com ranks 5th with its score of 80/100, matching the median score of the group. The panel average stands at 75.6, indicating that github.com is performing above average. Leading the panel are cloudflare.com and stripe.com, both scoring 100/100, while openai.com lags behind at 20/100. Common challenges across the panel include AI-crawler reachability, GPTBot/ClaudeBot access, and the presence of /llms.txt, with all 10 sites experiencing issues in these areas.
What should a typical business site take from this?
For business sites aiming to improve their visibility to AI engines, github.com's performance offers several lessons. Ensuring AI-crawler reachability and allowing access to major AI crawlers like GPTBot and ClaudeBot are crucial steps. Implementing a well-structured /llms.txt file can significantly aid in content mapping. However, the absence of a JSON-LD schema on github.com serves as a reminder of the importance of structured data in helping engines understand the nature of the site. Addressing such gaps can enhance a site's visibility and ensure it appears in generated answers effectively.
For more detailed guidance on optimizing AI crawler access, refer to our AI crawler playbook , and for insights on creating an effective /llms.txt file, see our llms.txt guide .
No comments yet