You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Meta tags are excellent: docs site scores 14/14 and README 14/14 — title, description, canonical, and Open Graph tags are all present and well-formed.
Schema JSON-LD is strong on the docs site: 13/16, with WebSite, Organization, SoftwareApplication, and FAQPage types detected.
Robots.txt actually allows AI crawlers: the authoritative check (docs-robots-verification.json, http_status: 200, found: true) confirms https://github.github.com/gh-aw/robots.txt explicitly Allows GPTBot, ClaudeBot, PerplexityBot, Google-Extended, Amazonbot, CCBot, and more, plus a Sitemap: directive. (The raw score of 0/18 in the JSON audits is a false negative — the GEO tool probes the domain root /robots.txt, which doesn't respect the /gh-aw/ GitHub Pages project-site base path.)
Signals are solid: docs site 6/6 — lang="en", an RSS feed (/blog/rss.xml), and content freshness metadata (2026-05-09) are all present.
Brand & entity presence is good on the docs site: 7/10, with Knowledge Graph pillars (Wikipedia, Wikidata, LinkedIn, Crunchbase) all linked for GitHub as the parent entity.
🚨 Critical Gaps
llms.txt is completely missing on both the docs site and README (0/18 and part of README's 14/14 llms_txt... actually 0 score) — no /llms.txt file exists to give AI systems a structured content index.
AI Discovery signals are 0/6 on the docs site and README — no /.well-known/ai.txt, /ai/summary.json, /ai/faq.json, or /ai/service.json.
README has no Schema JSON-LD at all (0/16) — missing WebSite, Organization (with sameAs links to Wikipedia/Wikidata/LinkedIn/Crunchbase), and FAQPage schema that the docs site already has.
Hidden text detected (display:none/visibility:hidden with content) on both docs site and README — flagged as a potential cloaking pattern that AI crawlers may penalize.
Keyword stuffing: "github" appears at 2.7% density (docs) and 3.6% density (README) — vocabulary should be diversified.
5 of 20 sitemap pages score "Critical" (33–35/100): /about, and blog pages 4, 8, 9, 11 — driven by low schema (3/16) and brand_entity (2/10) scores on those pages.
🔧 Recommended Fixes
Create /llms.txt for the docs site (geo llms --base-url https://github.github.com/gh-aw) — highest-impact single fix, worth up to 18 points on every audited page (20 pages average 0/18 today).
Add JSON-LD schema to the README — WebSite, Organization (with sameAs to Wikipedia/Wikidata/LinkedIn/Crunchbase), and FAQPage — closing the 0/16 schema gap that the docs site has already solved.
Add AI-discovery well-known files: /.well-known/ai.txt, /ai/summary.json, /ai/faq.json, /ai/service.json — currently 0/6 across the board.
Remove hidden text (display:none/visibility:hidden elements with real content) from both the docs site and README to avoid cloaking penalties.
Reduce "github" keyword density and diversify vocabulary on high-density pages.
Improve schema/brand_entity on the 5 critical-band sitemap pages (/about, /blog/4, /blog/8, /blog/9, /blog/11) — these average schema 3/16 and brand_entity 2/10, well below the site average.
Add SearchAction (potentialAction) to the WebSite schema and a VideoObject schema for any embedded video content, per the docs-site recommendations.
📋 Full Breakdown by Category
Docs site homepage (https://github.github.com/gh-aw/, score 44/100, Foundation):
Category
Score
Max
Robots.txt
0*
18
llms.txt
0
18
Schema JSON-LD
13
16
Meta Tags
14
14
Content
7
12
Brand & Entity
7
10
Signals
6
6
AI Discovery
0
6
*Robots.txt scored 0 in the raw JSON due to the GEO tool probing the domain root instead of /gh-aw/robots.txt. The authoritative verification confirms the actual /gh-aw/robots.txt is fully configured and explicitly allows all major AI crawlers — this is a tooling false negative, not a real gap.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
GEO Audit Report — github/gh-aw
Audit Date: 2026-08-17
Run: https://github.com/github/gh-aw/actions/runs/32045987023
📊 Scores
github.github.com/gh-aw/)✅ Top Strengths
WebSite,Organization,SoftwareApplication, andFAQPagetypes detected.docs-robots-verification.json,http_status: 200,found: true) confirmshttps://github.github.com/gh-aw/robots.txtexplicitlyAllows GPTBot, ClaudeBot, PerplexityBot, Google-Extended, Amazonbot, CCBot, and more, plus aSitemap:directive. (The raw score of 0/18 in the JSON audits is a false negative — the GEO tool probes the domain root/robots.txt, which doesn't respect the/gh-aw/GitHub Pages project-site base path.)lang="en", an RSS feed (/blog/rss.xml), and content freshness metadata (2026-05-09) are all present.🚨 Critical Gaps
/llms.txtfile exists to give AI systems a structured content index./.well-known/ai.txt,/ai/summary.json,/ai/faq.json, or/ai/service.json.WebSite,Organization(withsameAslinks to Wikipedia/Wikidata/LinkedIn/Crunchbase), andFAQPageschema that the docs site already has.display:none/visibility:hiddenwith content) on both docs site and README — flagged as a potential cloaking pattern that AI crawlers may penalize./about, and blog pages4,8,9,11— driven by low schema (3/16) and brand_entity (2/10) scores on those pages.🔧 Recommended Fixes
/llms.txtfor the docs site (geo llms --base-url https://github.github.com/gh-aw) — highest-impact single fix, worth up to 18 points on every audited page (20 pages average 0/18 today).WebSite,Organization(withsameAsto Wikipedia/Wikidata/LinkedIn/Crunchbase), andFAQPage— closing the 0/16 schema gap that the docs site has already solved./.well-known/ai.txt,/ai/summary.json,/ai/faq.json,/ai/service.json— currently 0/6 across the board.display:none/visibility:hiddenelements with real content) from both the docs site and README to avoid cloaking penalties./about,/blog/4,/blog/8,/blog/9,/blog/11) — these average schema 3/16 and brand_entity 2/10, well below the site average.SearchAction(potentialAction) to theWebSiteschema and aVideoObjectschema for any embedded video content, per the docs-site recommendations.📋 Full Breakdown by Category
Docs site homepage (
https://github.github.com/gh-aw/, score 44/100, Foundation):*Robots.txt scored 0 in the raw JSON due to the GEO tool probing the domain root instead of
/gh-aw/robots.txt. The authoritative verification confirms the actual/gh-aw/robots.txtis fully configured and explicitly allows all major AI crawlers — this is a tooling false negative, not a real gap.README (
github.com/github/gh-aw, score 55/100, Foundation):Docs sitemap average (20 pages audited, 0 failed):
Band distribution: 15 pages "Foundation", 5 pages "Critical", 0 "Good"/"Excellent".
📄 Sitemap Page Scores
Top 5 pages:
/(homepage)/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-analyticsLowest 5 pages:
/blog/11/blog/9/blog/8/blog/4/aboutAutomated audit powered by geo-optimizer-skill · Run logs
All reactions