[geo-optimizer] GEO Audit Report — 2026-05-16

[github-actions[bot]]

GEO Audit Report — github/gh-aw

Audit Date: 2026-05-16
Run: §25967255726

---

📊 Scores

Target	Score	Band	Trust Grade
Docs site (github.github.com/gh-aw/)	38/100	Foundation	C (medium)
README (github.com/github/gh-aw)	55/100	Foundation	C (medium)

Both targets sit in the Foundation band — AI crawlers can reach the content, but structural signals needed for reliable citation are missing.

---

✅ Top Strengths

• AI bots fully unblocked (README): All major crawlers allowed — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, and 24 more explicitly permitted in robots.txt (score 15/18).
• llms.txt present (README): 2,873 words, 11 sections, 117 links, blockquote — a strong LLM-friendly site summary (score 14/18).
• Meta tags complete (docs site): Perfect 14/14 — title, description, canonical, OG title/description/image all present.
• Content structure strong: Both targets score 11–12/12 — heading hierarchy, lists/tables, front-loaded content, rich word counts.
• Technical trust (README): Full 5/5 — HTTPS, HSTS, CSP, X-Frame-Options all present.
• Perplexity citability: Docs site scores 65/100 and README 70/100 on Perplexity — the best-performing platform for both targets.

---

🚨 Critical Gaps

1. No robots.txt on docs site — GPTBot, ClaudeBot, PerplexityBot get no explicit permission; score 0/18. Docs site is the primary user-facing target for AI citation yet has no AI crawler policy.
2. No llms.txt on docs site — Score 0/18. An /llms.txt file would tell AI engines how to index and summarize the documentation.
3. No JSON-LD schema on README — Score 0/16. GitHub's repository page has no WebSite, Organization, or FAQPage schema, severely limiting structured-data-based citations (especially Google AI: 45/100).
4. No AI discovery endpoints on either target — Both score 0/6 for /.well-known/ai.txt, /ai/summary.json, /ai/faq.json, and /ai/service.json.
5. Brand/entity signals weak (both targets) — Score 3/10 each. No Wikipedia, Wikidata, LinkedIn, or Crunchbase sameAs links; no Knowledge Graph anchors.

---

🔧 Recommended Fixes

Ordered by estimated impact:

1. Add /robots.txt to docs site — Allow GPTBot, ClaudeBot, PerplexityBot, Google-Extended. Unlocks up to +18 pts on docs site score.

   User-agent: GPTBot
   Allow: /
   User-agent: ClaudeBot
   Allow: /
   User-agent: PerplexityBot
   Allow: /
   User-agent: Google-Extended
   Allow: /
   

2. Generate /llms.txt for docs site — Run geo llms --base-url https://github.github.com/gh-aw and publish the output. Unlocks up to +18 pts.

3. Add JSON-LD schema to README / project homepage — Add WebSite, Organization (with sameAs to GitHub org), and FAQPage schema. Critical for Google AI (currently 45/100). Up to +16 pts on README.

4. Create /.well-known/ai.txt on both targets — Defines AI crawler permissions in a standardized location. +6 pts each (ai_discovery 0→6).

5. Add /ai/summary.json, /ai/faq.json, /ai/service.json endpoints on docs site — Structured data specifically for AI engine consumption.

6. Add Knowledge Graph sameAs links — Link Organization schema to Wikidata, LinkedIn, or Crunchbase for entity disambiguation. +up to 7 pts on brand_entity for each target.

7. Fix sitemap.xml on docs site — Sitemap returned 404 (https://github.github.com/gh-aw/sitemap.xml). Add one to enable sitemap-wide crawling by AI bots.

8. Add <link rel="canonical"> to README page — Currently missing (score 11/14 meta tags). Prevents duplicate-content penalties.

9. Add RSS/Atom feed to README — Signals freshness to AI discovery tools (+3 pts signals).

10. Diversify keyword density — README has 'issue' at 23.4% density (keyword stuffing penalty −3 pts). Review and diversify vocabulary in README content.

📋 Full Score Breakdown by Category

Category	Docs Site	Max	README	Max
robots.txt	0	18	15	18
llms.txt	0	18	14	18
Schema JSON-LD	7	16	0	16
Meta Tags	14	14	11	14
Content	11	12	12	12
Signals	6	6	3	6
AI Discovery	0	6	0	6
Brand & Entity	3	10	3	10
Negative Penalty	−3	—	−3	—
Total	38	100	55	100

Negative signals detected on both targets:

• Hidden text (display:none) flagged as suspicious — medium risk
• Keyword stuffing (docs: 'github' 3.7%; README: 'issue' 23.4%)

Platform citation scores (README):

• ChatGPT: 55/100 — FAQPage schema and Organization schema missing
• Perplexity: 70/100 — Strong; add dateModified schema
• Google AI: 45/100 — Needs JSON-LD, canonical, and /.well-known/ai.txt

Platform citation scores (Docs Site):

• ChatGPT: 50/100 — Needs robots.txt and llms.txt
• Perplexity: 65/100 — Needs robots.txt and llms.txt
• Google AI: 70/100 — Best performer; add more schema types

Content decay risk (README): High (evergreen score 70/100) — version numbers and relative time phrases detected; add dateModified schema.

RAG chunk readiness: Docs site 45/100, README 46/100 — sections are short (avg 5.9 and 23.5 words respectively); improve section depth for better RAG retrieval.

📄 Sitemap Audit

The sitemap audit could not complete — https://github.github.com/gh-aw/sitemap.xml returned 404 Not Found.

Creating a sitemap is a recommended action (see fix #7 above). Once published, re-running the sitemap audit will show per-page GEO scores across the documentation.

---

References:

• §25967255726

Automated audit powered by geo-optimizer-skill · Run logs

Generated by 🌍 GEO Optimizer Daily Audit · ● 5.6M · ◷

• expires on May 19, 2026, 4:43 PM UTC

[github-actions[bot]]

This discussion has been marked as outdated by GEO Optimizer Daily Audit.

A newer discussion is available at Discussion #32848.