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

[github-actions[bot]]

GEO Audit Report — github/gh-aw

Audit Date: 2026-05-09
Run: §25606177061

---

📊 Scores

Target	Score	Band	Citability
Docs site (github.github.com/gh-aw/)	40/100	Foundation	78/100
README (github.com/github/gh-aw)	58/100	Foundation	84/100
Sitemap audit	❌ N/A	—	404 on sitemap.xml

---

✅ Top Strengths

• README robots.txt is comprehensive — 27 AI bots explicitly allowed (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.), scoring 15/18
• llms.txt present on GitHub repo — 2,873 words, 11 sections, 117 links, scoring 14/18
• Docs site meta tags are perfect — title, description, canonical, Open Graph all present, scoring 14/14
• Docs site structured data — WebSite, Organization, SoftwareApplication, and FAQPage JSON-LD types detected, scoring 11/16
• Instruction readiness is advanced — both targets score 90+ for labeled buttons, ARIA, and form accessibility
• Content is JS-independent — both sites render full content without JavaScript, ensuring AI crawler accessibility

---

🚨 Critical Gaps

1. Docs site has no robots.txt (0/18) — AI bots receive no explicit permission signal from github.github.com/gh-aw/. All three major crawlers (GPTBot, ClaudeBot, PerplexityBot) currently return HTTP 301, not 200.
2. Docs site has no llms.txt (0/18) — Zero words, sections, or links for LLM indexing at the docs domain.
3. AI discovery endpoints missing on both targets (0/6 each) — No /.well-known/ai.txt, no /ai/summary.json, /ai/faq.json, or /ai/service.json on either domain.
4. README has zero JSON-LD schema (0/16) — github.com renders no structured data for the repo page; no WebSite, FAQPage, or Organization schema.
5. Brand/entity signals are weak on both (3/10 each) — No Wikipedia, Wikidata, LinkedIn, or Crunchbase sameAs links; no Knowledge Graph pillar URLs.
6. Docs site content lacks statistics — No numerical data detected (numbers_count: 0), reducing AI snippet selectability. RAG chunk readiness is 45/100.

---

🔧 Recommended Fixes

Ordered by estimated impact:

1. [HIGH] Add robots.txt to the Docs site — Create https://github.github.com/gh-aw/robots.txt explicitly allowing GPTBot, ClaudeBot, PerplexityBot, and Google-Extended. This single file closes a 0/18 gap.

2. [HIGH] Generate llms.txt for the Docs site — Run geo llms --base-url https://github.github.com/gh-aw to create an LLM-friendly site summary, closing the 0/18 llms gap.

3. [HIGH] Add JSON-LD schema to README / repo landing — Since github.com controls schema injection, consider adding Organization and SoftwareApplication schema via the repository's docs site instead, or raise a GitHub request. This is the single largest gap on the README (0/16).

4. [MEDIUM] Create AI discovery endpoints on the Docs site — Add /.well-known/ai.txt, /ai/summary.json, /ai/faq.json, and /ai/service.json to close the 0/6 ai_discovery gap and improve Google AI Overviews score from 70 to higher.

5. [MEDIUM] Add quantitative content to Docs site homepage — Include concrete numbers (e.g., workflow execution times, number of supported AI engines, example automation timings). Currently numbers_count: 0; adding stats increases AI snippet selection probability (+40% per audit recommendation).

6. [MEDIUM] Add sameAs links to Organization schema — Reference Wikipedia, Wikidata, or a Crunchbase/LinkedIn profile in the Docs site's Organization JSON-LD to improve Knowledge Graph entity disambiguation.

7. [LOW] Add dateModified to schema and freshness indicators — The README shows high content decay risk (evergreen_score: 30) due to version numbers and issue references. Adding dateModified schema reduces staleness signals.

8. [LOW] Add canonical <link> to README page — Currently missing (canonical_url: ""), costing 3 meta tag points (11/14 vs 14/14).

9. [LOW] Fix keyword stuffing — Docs site: 'github' at 3.6% density; README: 'issue' at 21.8% density. Diversify vocabulary to reduce negative signals.

---

📋 Full Score Breakdown by Category

Docs Site (github.github.com/gh-aw/) — 40/100

Category	Score	Max	Status
Robots.txt	0	18	❌ Missing
llms.txt	0	18	❌ Missing
Schema JSON-LD	11	16	✅ WebSite, Org, SoftwareApp, FAQ
Meta Tags	14	14	✅ Perfect
Content	7	12	⚠️ No stats, no front-loading
Signals	5	6	✅ Lang + RSS
AI Discovery	0	6	❌ No endpoints
Brand & Entity	3	10	⚠️ No KG links

Trust Stack: C / Medium — Technical 3/5, Identity 2/5, Social 2/5, Academic 1/5, Consistency 3/5

Platform citation scores: ChatGPT 50, Perplexity 50, Google AI 70

Negative signals (medium severity): keyword stuffing ('github' 3.6%), 1 hidden text element (keyboard shortcut label CtrlK)

README (github.com/github/gh-aw) — 58/100

Category	Score	Max	Status
Robots.txt	15	18	✅ 27 AI bots allowed
llms.txt	14	18	✅ 2,873 words, 117 links
Schema JSON-LD	0	16	❌ None detected
Meta Tags	11	14	⚠️ No canonical
Content	12	12	✅ Perfect
Signals	3	6	⚠️ No RSS, no freshness
AI Discovery	0	6	❌ No endpoints
Brand & Entity	3	10	⚠️ No KG links

Trust Stack: C / Medium — Technical 5/5, Identity 3/5, Social 1/5, Academic 4/5, Consistency 3/5

Platform citation scores: ChatGPT 55, Perplexity 70, Google AI 45

Negative signals (medium severity): keyword stuffing ('issue' 21.8%), hidden nav text, popup signals, 12 broken links

Content decay risk: HIGH — evergreen_score: 30, version numbers and issue references detected

📄 Sitemap Audit

The sitemap audit returned an error:

HTTP 404: https://github.github.com/gh-aw/sitemap.xml
Error: No URLs found in sitemap

The Docs site (Astro/Starlight) does not appear to expose a standard /sitemap.xml. Generating one would allow the audit tool to assess individual docs pages and help AI crawlers discover all content.

---

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

Generated by GEO Optimizer Daily Audit · ● 3M · ◷

• expires on May 12, 2026, 4:41 PM UTC

[pelikhan]

/plan as a single issue.

[github-actions[bot]]

🚀 Plan Command has started processing this discussion comment

[github-actions[bot]]

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

A newer discussion is available at Discussion #31548.