# AI-visibility check — github.com

**Score: 80/100 — Strong visibility** (checked with https://geoplaybooks.com/check/)

AI engines can read and cite you — 4 of 5 core signals pass. You're set up to appear in generated answers.

| Signal | Status | Finding |
|---|---|---|
| AI-crawler reachability | PASS | Homepage returns HTTP 200 with ~6,855 chars of server-rendered text. Retrieval bots can read you. |
| GPTBot / ClaudeBot access | PASS | No blanket Disallow for the major AI crawlers — GPTBot, ClaudeBot and PerplexityBot can fetch your key pages. |
| llms.txt | PASS | /llms.txt is present and well-formed markdown (28,649 bytes). Engines have a map to your content. |
| JSON-LD schema | FAIL | No JSON-LD schema on the homepage. Engines can't tell what type of entity you are. |
| Answer-first structure | PASS | Clear H1 + 8 sections with short, extractable answers. Answer-ready. |

## AI fix-it prompt

```text
You are an engineer working on the website github.com. Below is an AI-visibility (GEO) audit of the site — the signals that decide whether AI answer engines (ChatGPT, Perplexity, Google AI Overviews) can crawl, understand and cite it. Implement the fixes.

## Audit findings

### Sitewide signals
- [PASS] AI-crawler reachability: Homepage returns HTTP 200 with ~6,855 chars of server-rendered text. Retrieval bots can read you.
- [PASS] GPTBot / ClaudeBot access: No blanket Disallow for the major AI crawlers — GPTBot, ClaudeBot and PerplexityBot can fetch your key pages.
- [PASS] llms.txt: /llms.txt is present and well-formed markdown (28,649 bytes). Engines have a map to your content.
- [FAIL] JSON-LD schema: No JSON-LD schema on the homepage. Engines can't tell what type of entity you are.
- [PASS] Answer-first structure: Clear H1 + 8 sections with short, extractable answers. Answer-ready.

## Implementation rules
- Work through the failing signals in the order above; PASS items need no changes.
- Crawler access: check robots.txt AND the WAF/CDN layer for blocks on GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, Google-Extended.
- llms.txt: create a curated Markdown index at /llms.txt per https://llmstxt.org — one H1, a > summary, ## sections, every link with a one-line description.
- JSON-LD: add Organization (+ logo, sameAs) sitewide and Article/FAQPage on content pages; link entities with absolute @id references.
- Answer-first structure: under each question-shaped H2, place a self-contained 40–80-word answer paragraph before any elaboration.
- Do not fabricate content; restructure what exists.

## Acceptance criteria
- Re-run the free checker at https://geoplaybooks.com/check/ for github.com until all 5 signals are PASS.
- Validate llms.txt at https://geoplaybooks.com/tools/llms-txt-validator/ (0 errors).
- Verify JSON-LD parses in Google's Rich Results Test.
```

Deeper: page-by-page audit from $49, monthly monitoring from $20/mo — https://geoplaybooks.com/audit/