[geo-optimizer] GEO Audit Report — 2026-06-02

[github-actions[bot]]

GEO Audit Report — github/gh-aw

Audit Date: 2026-06-02
Run: §26837864029

---

📊 Scores

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

Both targets are in the Foundation band — functional but lacking key AI-indexing signals. Significant headroom remains before reaching the Good (70+) or Excellent (90+) thresholds.

---

✅ Top Strengths

• README: Excellent robots.txt — 27 AI bots explicitly allowed (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, and more); score 15/18
• README: llms.txt present — 2,919-word file with 12 sections and 117 links; score 14/18
• Docs site: Complete meta tags — title, description, Open Graph, and canonical all present; perfect 14/14
• Docs site: Rich Schema JSON-LD — WebSite, Organization, SoftwareApplication, and FAQPage types found; 12/16
• Docs site: Freshness signals — RSS feed + dateModified present, evergreen score 100 (vs README's 38)
• Both: AI bots unblocked — GPTBot, ClaudeBot, and PerplexityBot all receive full page content (HTTP 200, no challenges)

---

🚨 Critical Gaps

1. Docs site has no robots.txt (0/18) — AI bots can access the site but there is no explicit permission signal; robots.txt is a primary trust indicator for AI crawlers
2. Docs site has no llms.txt (0/18) — The 36-point gap vs the README is almost entirely caused by these two missing files; generating one takes ~1 minute with geo llms --base-url https://github.github.com/gh-aw
3. README has zero Schema JSON-LD (0/16) — github.com renders no structured data on the repo page; this limits Google AI Overview and entity graph signals
4. Neither target has AI Discovery endpoints (0/6 each) — /.well-known/ai.txt, /ai/summary.json, /ai/faq.json, and /ai/service.json are all missing
5. Docs site blog section scores Critical — 19 out of 20 audited pages are in the Critical band (30–33/100), dragging down overall site authority
6. README content decay risk is High (evergreen score 38/100) — Version strings, closed issue dates, and "please upgrade" language trigger staleness signals

---

🔧 Recommended Fixes

Ordered by estimated impact / effort ratio:

#	Fix	Target	Est. Gain
1	Create robots.txt on the docs site with Allow for AI bots	Docs site	+18 pts
2	Generate /llms.txt: geo llms --base-url https://github.github.com/gh-aw	Docs site	+14 pts
3	Create /.well-known/ai.txt, /ai/summary.json, /ai/faq.json, /ai/service.json on docs site	Docs site	+6 pts
4	Add dateModified schema and reduce version-specific language in README to lower content decay	README	+3–5 pts
5	Add Organization + WebSite JSON-LD to docs site (schema desc currently differs from meta description)	Docs site	+3–4 pts
6	Add sameAs links to Wikipedia, Wikidata, LinkedIn, Crunchbase in Organization schema (README only has 0/4 KG pillars; docs site has 2/4)	Both	+3–4 pts
7	Add <link rel="canonical"> to README page (currently missing)	README	+3 pts
8	Lift blog pages from Critical to Foundation — add article schema, author attribution, RSS <link> tags per blog post	Docs site blog	+5–10 pts avg per page
9	Add numerical statistics and concrete data points to docs homepage content (has_numbers: false)	Docs site	+2–3 pts
10	Fix keyword stuffing: github at 2.7% density on docs site, issue at 22.5% on README page	Both	-penalty removed

Quick win: Items 1 + 2 combined would push the docs site from 42 → ~74 (Good band) with under an hour of work.

📋 Full Breakdown by Category

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

Category	Score	Max	Status
Robots.txt	0	18	❌ Missing
llms.txt	0	18	❌ Missing
Schema JSON-LD	12	16	✅ WebSite, Organization, SoftwareApplication, FAQPage
Meta Tags	14	14	✅ Perfect
Content	7	12	⚠️ No numbers/stats, no lists/tables
Signals	6	6	✅ RSS, freshness, lang
AI Discovery	0	6	❌ No well-known/ai.txt or /ai/* endpoints
Brand & Entity	6	10	⚠️ 2/4 KG pillars, no about page
Negative Penalty	-3	—	Hidden text, keyword stuffing

Trust Stack: Grade C (15/25) · Technical 3/5, Identity 3/5, Social 4/5, Academic 1/5, Consistency 4/5

Platform Citation Scores: ChatGPT 50 · Perplexity 65 · Google AI 70

RAG Chunk Readiness: 45/100 — avg section only 5.9 words; increase content depth per section

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

Category	Score	Max	Status
Robots.txt	15	18	✅ 27 bots allowed
llms.txt	14	18	✅ 2,919 words, 12 sections
Schema JSON-LD	0	16	❌ None (GitHub platform limitation)
Meta Tags	11	14	⚠️ Missing canonical URL
Content	12	12	✅ Perfect — rich, front-loaded, lists & numbers
Signals	3	6	⚠️ No RSS, no freshness date
AI Discovery	0	6	❌ No well-known/ai.txt or /ai/* endpoints
Brand & Entity	3	10	❌ 0/4 KG pillars, no contact info in schema
Negative Penalty	-3	—	Hidden text, popup signals, 12 broken links

Trust Stack: Grade C (16/25) · 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

Content Decay: High risk (evergreen score 38/100) — 9 decay signals detected; add dateModified schema

📄 Sitemap Page Scores (20 pages audited)

URL	Score	Band
/gh-aw (homepage)	42	Foundation
/gh-aw/blog	33	Critical
/gh-aw/blog/3	33	Critical
/gh-aw/blog/4	33	Critical
/gh-aw/blog/8	33	Critical
/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-improvement	33	Critical
/gh-aw/blog/2	32	Critical
/gh-aw/blog/5	32	Critical
/gh-aw/blog/6	32	Critical
/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-refactoring	32	Critical
/gh-aw/blog/7	31	Critical
/gh-aw/blog/9	30	Critical
/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory	30	Critical
/gh-aw/blog/2026-01-13-meet-the-workflows-advanced-analytics	30	Critical
/gh-aw/blog/2026-01-13-meet-the-workflows-campaigns	30	Critical
/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-simplicity	30	Critical
/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-style	30	Critical
/gh-aw/blog/2026-01-13-meet-the-workflows-creative-culture	30	Critical
/gh-aw/blog/2026-01-13-meet-the-workflows-documentation	30	Critical
/gh-aw/agent-factory-status	27	Critical

Key finding: The homepage is the only page in Foundation band. All blog posts and the agent-factory-status page are Critical. Prioritize adding robots.txt + llms.txt sitewide, then add structured article schema to individual blog posts.

---

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

Generated by 🌍 GEO Optimizer Daily Audit · sonnet46 104.4K · ◷

• expires on Jun 5, 2026, 5:57 PM UTC

[github-actions[bot]]

This discussion was automatically closed because it expired on 2026-06-05T17:57:28.320Z.

Closed by Workflow