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

[github-actions[bot]]

GEO Audit Report — github/gh-aw

Audit Date: 2026-05-17
Run: §25996606600

---

📊 Scores

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

Both targets are in the Foundation band — basic signals are present but significant gaps remain before AI engines will reliably cite or recommend this project.

---

✅ Top Strengths

README (github.com/github/gh-aw)

• ✅ robots.txt — 27 AI bots explicitly allowed (GPTBot, ClaudeBot, PerplexityBot, and more) — near-perfect score (15/18)
• ✅ llms.txt present with 2,873 words, 117 links, 11 sections, and a blockquote summary (14/18)
• ✅ Rich content: 3,017 words, 41 headings, numbers and statistics present (12/12)
• ✅ Open Graph tags (title, description, image) present (11/14)

Docs site (github.github.com/gh-aw/)

• ✅ Full Schema JSON-LD: WebSite, Organization, SoftwareApplication, FAQPage types detected (7/16)
• ✅ All meta tags present with a strong description (186 chars) and canonical URL (14/14)
• ✅ Good content structure: 26 headings, lists/tables, front-loaded content (11/12)
• ✅ Freshness signal present (last updated 2026-05-09), RSS feed, and lang=en (6/6)

---

🚨 Critical Gaps

1. No AI Discovery endpoints — Both targets score 0/6. Missing /.well-known/ai.txt, /ai/summary.json, /ai/faq.json, /ai/service.json. These are increasingly important for AI agent discovery.

2. Docs site has no robots.txt — Scores 0/18. AI crawlers may be blocked or underprioritised when crawling github.github.com/gh-aw/. Add explicit Allow rules for GPTBot, ClaudeBot, PerplexityBot.

3. Docs site has no llms.txt — Scores 0/18. The README has one; the docs site lacks it entirely. Run geo llms --base-url https://github.github.com/gh-aw/ to generate it.

4. README has zero Schema JSON-LD — Scores 0/16. The GitHub-hosted page lacks any structured data types; this is a GitHub platform constraint but contributes to low brand/entity disambiguation.

5. Keyword stuffing detected on both targets — "github" at 3.7% density on docs site; "issue" at 23.7% on README. AI engines may penalise this.

---

🔧 Recommended Fixes

Ordered by estimated impact:

1. Add robots.txt to the docs site (impact: +18 pts potential)
   Add AI bot Allow rules for at minimum: GPTBot, ClaudeBot, PerplexityBot, Google-Extended, Bingbot.

2. Add llms.txt to the docs site (impact: +18 pts potential)
   Run: geo llms --base-url https://github.github.com/gh-aw/
   Publish at https://github.github.com/gh-aw/llms.txt.

3. Create AI Discovery endpoints on both targets (impact: +6 pts each, +12 total)
   Add /.well-known/ai.txt, /ai/summary.json, /ai/faq.json, and /ai/service.json to the docs site.

4. Complete Schema JSON-LD on the docs site (impact: up to +9 pts)

   • Add @context field to WebSite, Organization, and FAQPage schemas (currently incomplete)
   • Add sameAs links to LinkedIn, Wikidata, or GitHub org profile for Knowledge Graph disambiguation

5. Add RSS feed link to README page (impact: +3 pts on signals)
   Add <link rel="alternate" type="application/rss+xml"> in HEAD pointing to the docs blog RSS.

6. Add canonical URL to README page (impact: +3 pts on meta)
   GitHub doesn't inject a canonical by default; consider a workaround or accept this as a platform limitation.

7. Add <link rel="canonical"> to README and diversify vocabulary to reduce keyword density.

8. Add contact/address to Organization schema on the docs site — improves entity validation for Knowledge Graph.

📋 Full Breakdown by Category

Docs site (github.github.com/gh-aw/) — Score: 38/100

Category	Score	Max	Status
Robots.txt	0	18	❌ No robots.txt found
llms.txt	0	18	❌ No llms.txt found
Schema JSON-LD	7	16	⚠️ 4 types found but incomplete @context
Meta Tags	14	14	✅ Perfect
Content	11	12	✅ Good (no numeric stats)
Signals	6	6	✅ Perfect
AI Discovery	0	6	❌ No endpoints
Brand & Entity	3	10	⚠️ Name consistent, no KG links
Negative Penalty	-3	—	⚠️ Keyword stuffing, hidden text

Negative signals detected: Keyword stuffing ("github" 3.7%), hidden text (cloaking risk).

README (github.com/github/gh-aw) — Score: 55/100

Category	Score	Max	Status
Robots.txt	15	18	✅ 27 AI bots allowed
llms.txt	14	18	✅ Present, no llms-full.txt
Schema JSON-LD	0	16	❌ None (GitHub platform)
Meta Tags	11	14	⚠️ No canonical URL
Content	12	12	✅ Perfect
Signals	3	6	⚠️ No RSS, no freshness date
AI Discovery	0	6	❌ No endpoints
Brand & Entity	3	10	⚠️ About link present, no KG sameAs
Negative Penalty	-3	—	⚠️ Keyword stuffing, popup signals, 12 broken links

Negative signals detected: Keyword stuffing ("issue" 23.7%), popup signals, 12 broken links detected.

📄 Sitemap Page Scores

The sitemap audit could not be completed — https://github.github.com/gh-aw/sitemap.xml returned a 404 Not Found error. No sitemap exists at this location.

Recommendation: Generate and publish a sitemap at /sitemap.xml on the docs site. Most static site generators (Astro, which is used here) support this via a plugin.

---

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

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

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

[pelikhan]

/plan

[github-actions[bot]]

🚀 Plan Command has started processing this discussion comment

[github-actions[bot]]

This discussion was automatically closed because it expired on 2026-05-20T16:43:36.063Z.

Closed by Workflow