[geo-optimizer] GEO Audit Report — 2026-08-18 #53758
Closed
Replies: 1 comment
|
This discussion was automatically closed because it expired on 2026-08-21T16:42:01.381Z.
|
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
GEO Audit Report — github/gh-aw
Audit Date: 2026-08-18
Run: https://github.com/github/gh-aw/actions/runs/32160801176
📊 Scores
github.github.com/gh-aw/)Note on robots.txt: the GEO scanner's
robots_txtcheck reportsfound: falsefor the docs site because it probes the domain root (https://github.github.com/robots.txt), which doesn't include the/gh-aw/GitHub Pages project-site base path. A direct, authoritative check ofhttps://github.github.com/gh-aw/robots.txtconfirms it does exist (HTTP 200) and explicitly allows all major AI crawlers (GPTBot, ClaudeBot, PerplexityBot, OAI-SearchBot, anthropic-ai, Google-Extended, etc.) plus aSitemap:directive. This is a scanner limitation, not a real site gap — no action needed on robots.txt for the docs site.✅ Top Strengths
WebSite,Organization,SoftwareApplication, andFAQPagetypes (13/16).lang="en", an RSS feed (/blog/rss.xml), and a freshness date — full 6/6.🚨 Critical Gaps
llms.txton the docs site (0/18) — no/llms.txtfile exists to help AI systems index the site structure./.well-known/ai.txt,/ai/summary.json,/ai/faq.json,/ai/service.json.WebSite/Organization/FAQPagestructured data on the GitHub repo homepage.display:none/visibility:hiddenwith content) — flagged as a potential cloaking pattern that AI crawlers may penalize (contributes to the -3 negative penalty on both audits)./blog/9at 33,/blog/11at 35,/blog/8at 35,/aboutat 35) — largely driven by weak schema/brand-entity scores on those pages.🔧 Recommended Fixes
Ordered by estimated impact:
/llms.txtfor the docs site (up to +18 pts) — rungeo llms --base-url https://github.github.com/gh-awto generate a structured AI-indexing file with H1, description, sections, and links.name,url,logo,sameAs(Wikipedia/Wikidata/LinkedIn/Crunchbase), andFAQPageschema./.well-known/ai.txt,/ai/summary.json,/ai/faq.json,/ai/service.json.display:none/visibility:hiddenelements with real content) on both the docs site and README to eliminate the cloaking-pattern penalty (-3 pts each).<link rel="canonical">to the README page to prevent duplicate-content indexing issues./blog/9,/blog/11,/blog/8,/about) for schema and brand-entity gaps specifically.📋 Full Breakdown by Category
Docs site (
https://github.github.com/gh-aw/) — score 44/100:*See robots.txt note above — this is a scanner domain-root artifact; the actual
/gh-aw/robots.txtis valid and AI-bot-friendly.README (
https://github.com/github/gh-aw) — score 55/100:Sitemap-wide averages (20 pages sampled of 224 discovered):
Band distribution: 16 pages "foundation", 4 pages "critical" (out of 20 audited).
📄 Sitemap Page Scores
Top pages:
/gh-aw(home)/blog/2026-01-13-meet-the-workflows-continuous-improvement/blog/2026-01-13-meet-the-workflows-continuous-refactoring/blog/2026-01-12-welcome-to-pelis-agent-factory/blog/2026-01-13-meet-the-workflows-advanced-analyticsWorst pages:
/blog/9/blog/11/blog/8/about/blog/10Automated audit powered by geo-optimizer-skill · Run logs
All reactions