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

[github-actions[bot]]

📊 GEO Audit Report — github/gh-aw

Audit Date: 2026-05-24
Run: §26366885418

---

📊 Scores

Target	Score	Band
Docs site (github.github.com/gh-aw/)	42/100	Foundation
README (github.com/github/gh-aw)	55/100	Foundation
Docs sitemap average (20 pages)	31/100	Critical

Both primary targets are in the Foundation band — functional but with significant gaps preventing AI engine citations. The sitemap average of 31 is Critical, meaning most documentation pages are nearly invisible to AI crawlers.

---

✅ Top Strengths

• robots.txt + llms.txt on GitHub.com — The README URL (github.com) scores 15/15 on robots and 14/15 on llms, meaning GitHub's own infrastructure already exposes these signals.
• Meta tags — Both targets pass meta tag checks (docs: 14/15, README: 11/15).
• Instruction readiness — The docs site scores 90/100 for AI agent interaction readiness: all buttons labeled, forms accessible, ARIA live regions present.
• Social trust — 6 sameAs links and 2/4 Knowledge Graph pillars are present on the docs site.
• Consistency — Brand name is consistent across title/H1/schema; dateModified is present.

---

🚨 Critical Gaps

1. No robots.txt on docs site — github.github.com/gh-aw/ scores 0/15 for robots. AI crawlers (GPTBot, ClaudeBot, PerplexityBot) have no explicit permission signal.
2. No llms.txt on docs site — Scores 0/15. An /llms.txt file would give AI systems a structured index of the documentation.
3. No AI Discovery endpoints — Both targets score 0 for ai_discovery. Missing /.well-known/ai.txt, /ai/summary.json, /ai/faq.json, and /ai/service.json.
4. No JSON-LD schema on README — The GitHub repo page scores 0/15 for schema. Missing WebSite, Organization, and FAQPage structured data.
5. Blog/inner pages are Critical — 19 of 20 sitemap pages score ≤33 (Critical band). Average schema score across the sitemap is only 0.6/15.
6. Keyword stuffing detected — "github" at 2.7% on docs site and "issue" at 23.1% on README — both flag as over-dense, potentially penalizing AI snippet selection.
7. 12 broken links on README — Hurts trust signals with AI crawlers.

---

🔧 Recommended Fixes (by impact)

Priority	Fix	Estimated Impact
🔴 High	Add robots.txt to github.github.com/gh-aw/ allowing AI bots	+15 pts docs site
🔴 High	Create /llms.txt on docs site (geo llms --base-url https://github.github.com/gh-aw/)	+15 pts docs site
🔴 High	Add WebSite + Organization + FAQPage JSON-LD schema to README	+15 pts README
🟠 Medium	Create /.well-known/ai.txt, /ai/summary.json, /ai/faq.json, /ai/service.json	+5–10 pts both
🟠 Medium	Fix 12 broken links in README	Removes negative penalty
🟠 Medium	Add sameAs links to Wikipedia, Wikidata, LinkedIn, Crunchbase in schema	+brand_entity
🟡 Low	Add /about page and author attribution on docs site	+identity trust
🟡 Low	Add <link rel="canonical"> to README	Deduplication
🟡 Low	Add numerical statistics / concrete metrics to docs content	+academic trust
🟡 Low	Add WebMCP attributes to interactive elements	Future-proof for Chrome AI agents

📋 Full Score Breakdown by Category

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

Category	Score	Max	Notes
robots.txt	0	15	❌ Missing
llms.txt	0	15	❌ Missing
Schema JSON-LD	12	15	✅ Partial
Meta Tags	14	15	✅ Good
Content	7	15	⚠️ Keyword stuffing ("github" 2.7%)
Signals	6	10	⚠️ Partial
AI Discovery	0	10	❌ Missing
Brand & Entity	6	10	⚠️ Missing 2/4 KG pillars
Negative Penalty	-3	0	Hidden text, keyword stuffing
Trust Grade	C	—	Technical 3/5, Social 4/5, Academic 1/5

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

Category	Score	Max	Notes
robots.txt	15	15	✅ GitHub.com robots
llms.txt	14	15	✅ GitHub.com llms
Schema JSON-LD	0	15	❌ No structured data
Meta Tags	11	15	✅ Good
Content	12	15	⚠️ Keyword stuffing ("issue" 23.1%), 12 broken links
Signals	3	10	⚠️ Low
AI Discovery	0	10	❌ Missing
Brand & Entity	3	10	⚠️ No sameAs KG links
Negative Penalty	-3	0	Hidden text, popup signals, keyword stuffing
Trust Grade	C	—	composite 16/25

📄 Sitemap Page Scores (20 pages audited)

URL	Score	Band
github.github.com/gh-aw	42	Foundation
.../blog	33	Critical
.../blog/2	33	Critical
.../blog/6	33	Critical
.../blog/2026-01-13-meet-the-workflows-continuous-improvement	33	Critical
.../blog/3	32	Critical
.../blog/4	32	Critical
.../blog/2026-01-13-meet-the-workflows-continuous-refactoring	32	Critical
.../blog/5	31	Critical
.../blog/2026-01-13-meet-the-workflows-issue-management	31	Critical

Average: 31.45/100 · 19 Critical, 1 Foundation · All pages score 0/15 on schema and 0/15 on AI discovery

---

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

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

• expires on May 27, 2026, 4:46 PM UTC

[github-actions[bot]]

💥 WHOOSH! 🦸♂️ The Smoke-Test Agent BURSTS onto the scene! 🌪️

KA-POW! 💥 Discussion #34482 has been visited by your friendly neighborhood Claude engine — running smoke tests across the multiverse of MCP servers! 🚀

✨ All systems: NOMINAL ✨
⚡ Engine: CLAUDE
🎯 Run: 26367223912

Up, up, and away! 🦸♀️💨

Warning

Firewall blocked 6 domains

The following domains were blocked by the firewall during workflow execution:

• accounts.google.com
• android.clients.google.com
• clients2.google.com
• contentautofill.googleapis.com
• safebrowsingohttpgateway.googleapis.com
• www.google.com

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "accounts.google.com"
    - "android.clients.google.com"
    - "clients2.google.com"
    - "contentautofill.googleapis.com"
    - "safebrowsingohttpgateway.googleapis.com"
    - "www.google.com"

See Network Configuration for more information.

💥 [THE END] — Illustrated by Smoke Claude · opus47 6.9M · ◷