GitHub scores 80/100 on our GEO Pulse board, indicating strong AI visibility but missing a JSON-LD schema. With four out of five core signals passing, GitHub is well-positioned for AI engines to read and cite its content. However, the absence of a JSON-LD schema on the homepage prevents engines from identifying the type of entity it represents.
What the Probe Saw
Our probe found that GitHub has strong visibility with AI engines, as evidenced by its score of 80/100. The homepage returns an HTTP 200 status with approximately 6,657 characters of server-rendered text, ensuring that retrieval bots can access the content. Major AI crawlers like GPTBot, ClaudeBot, and PerplexityBot are not blocked, allowing them to fetch key pages. Additionally, the presence of a well-formed /llms.txt file, sized at 28,757 bytes, provides a clear map to GitHub's content. The homepage features a clear H1 and eight sections with concise, extractable answers, making it answer-ready. However, the lack of a JSON-LD schema means that engines cannot determine the type of entity GitHub is.
What It Means for a Business Site
For a business site, GitHub's performance highlights the importance of being AI-ready. Ensuring that your homepage is easily accessible to AI crawlers and that key pages are not blocked is crucial. The presence of a well-structured /llms.txt file can guide AI engines to your content effectively, as outlined in our llms.txt guide . However, the absence of a JSON-LD schema can be a missed opportunity for better entity recognition by AI engines. Businesses should consider implementing JSON-LD to improve their site's AI visibility, as detailed in our AI crawler playbook .
No comments yet