# GitHub repos, package registries, and docs architecture in AI search

> Across 41,065 GitHub citations, 1.52 million tech-market links, and 60 live developer docs hosts, AI engines treat GitHub as a documentation database (88.55% hit repo roots or Markdown blobs, 71.3x ahead of Stack Overflow), boost #1 brand win rates 34.5% when GitHub pairs with an owned site, and flip 23.8x on docs vs blog share between ChatGPT Search (2.38x) and Perplexity (0.10x).

HTML: https://parse.gl/research/github-repos-and-docs-architecture-in-ai-search · Site index: https://parse.gl/llms.txt · Published: 2026-11-20

How do ChatGPT Search, Google AI Mode, and Perplexity actually use GitHub repositories, package registries, developer communities, and documentation sites when answering software and infrastructure buyer questions?

We analyzed 5,166,830 organic AI citation rows across ChatGPT Search and Google AI Mode (September 1 to November 19, 2026) and Perplexity (November 1 to November 19, 2026), isolating 41,065 github.com citations, 1,521,062 citation rows across 361 active tech markets, 163,874 tech-market answer-brand pairs (October 20 to November 19, 2026), and live HTTP checks across the top 60 cited tech documentation hosts.

## Key figures

- **of 41,065 GitHub citations hit repo roots or Markdown docs:** 88.55% (59.11% repo root READMEs (24,274) and 29.44% Markdown blobs (12,088))
- **higher #1 brand win rate when GitHub pairs with an owned site:** 34.5% (22.23% vs 16.53% own-site alone on ChatGPT Search (42.05% vs 32.19% on Google))
- **more citations to GitHub than the entire Stack Overflow network:** 71.3x (41,065 GitHub rows vs 576 Stack Overflow rows (and 480 across package registries))
- **docs-to-blog citation ratio in tech markets by engine:** 2.38x vs 0.10x (ChatGPT Search cites docs 2.38x blogs; Google (0.20x) and Perplexity (0.10x) flip)

## 88.55% of GitHub citations hit repository roots or Markdown docs, not source code

Across 41,065 github.com citation rows (43,179 citation occurrences across 10,318 distinct URLs), AI search engines treat GitHub as a structured technical encyclopedia rather than a code dump. Repository roots and READMEs capture 59.11% of all GitHub citations (24,274 rows across 5,242 URLs and 6,244 buyer questions), and Markdown or plain-text documentation /blob/ pages capture another 29.44% (12,088 rows across 3,927 URLs).

Inside all 12,590 cited /blob/ URLs, 96.01% (12,088) are Markdown, MDX, RST, AsciiDoc, or text documentation files, whereas only 502 rows (1.22% of all GitHub citations) point to code or config files. GitHub product marketing pages add 5.69% (2,337), organization or user profile pages add 2.16% (887), and wikis supply 0.67% (276). Releases and tags account for just 0.23% (93 rows), and pull requests appear six times total (0.01%).

**Share of 41,065 github.com citations by URL path class**

| Item | Value |
| --- | --- |
| Repository root and README | 59.11% (24,274 rows) |
| Markdown or text docs (/blob/) | 29.44% (12,088 rows) |
| GitHub product and marketing pages | 5.69% (2,337 rows) |
| Org or user profile pages | 2.16% (887 rows) |
| Source code or config (/blob/) | 1.22% (502 rows) |
| Repository wikis | 0.67% (276 rows) |
| GitHub Issues | 0.52% (215 rows) |
| Tree or raw directories | 0.45% (183 rows) |
| GitHub Discussions | 0.29% (119 rows) |
| Releases and tags | 0.23% (93 rows) |

_Organic citations across ChatGPT Search (36,019), Google AI Mode (4,999), and Perplexity (47), Sep 1 to Nov 19, 2026 (Perplexity Nov 1 to Nov 19)._

> AI engines cite your README and Markdown docs files 72 times more often than your source code files.

## Google AI Mode cites GitHub Issues and Discussions 36.9x more often than ChatGPT Search

The three AI engines pull very different sections of the same repository. ChatGPT Search splits its 36,019 GitHub links between repository roots (56.63%, 20,399 rows) and deep Markdown documentation blobs (32.67%, 11,767 rows), and Perplexity shows an even heavier tilt toward Markdown blobs in its 47-row November sample (51.06% blobs vs 34.04% roots).

Google AI Mode concentrates 77.20% of its 4,999 GitHub links on repo roots (3,859 rows), pulls Markdown blobs only 5.94% of the time (297 rows), and shifts its remaining citations into troubleshooting threads: 3.54% GitHub Issues (177 rows) and 2.00% GitHub Discussions (100 rows). Together, Issues and Discussions supply 5.54% of Google AI Mode's GitHub links versus just 0.15% on ChatGPT Search (0.10% Issues, 0.05% Discussions), a 36.9x gap.

- **Markdown /blob/ share: ChatGPT vs Google:** 32.67% vs 5.94% (Perplexity reached 51.06% (24 of 47 rows in Nov))
- **Issues + Discussions: Google vs ChatGPT:** 5.54% vs 0.15% (36.9x higher troubleshooting thread reliance on Google AI Mode)
- **Google AI Mode GitHub links hitting repo roots:** 77.20% (Compared with 56.63% on ChatGPT Search (20,399 rows))
- **Share of GitHub citations going to releases/tags:** 0.23% (Changelog and version summaries earn more value inside README/docs)

> Keep READMEs clear for Google AI Mode and structure Markdown files cleanly under /docs in your repo for ChatGPT Search.

## Observability, AI evals, and Markdown docs repos top AI citations and reach up to 60.2% #1 win rates

Across all 41,065 GitHub citations, arize-ai/phoenix leads by distinct buyer questions (251 questions, 499 cited answers, 625 occurrences), followed by signoz/signoz (186 questions), louislam/uptime-kuma (182 questions, 622 answers, 782 occurrences), openobserve/openobserve (176 questions), grafana/loki (160), and langchain-ai/docs (141). Pure documentation repositories such as langchain-ai/docs (99.58% blobs), github/docs (100%), langfuse/langfuse-docs (100%), clickhouse/clickhouse-docs (100%), and open-telemetry/opentelemetry.io (100%) rely entirely on ChatGPT Search citing deep Markdown files.

Pairing a high-citation repo with clear product identity drives dominant brand positioning. When mentioned in an answer that cites its repo, open-telemetry/opentelemetry.io earns #1 recommendation 60.20% of the time (52.21% of all cited answers), backstage/backstage wins #1 at 57.34% (51.90% overall), langchain-ai/docs hits 50.34%, grafana/loki hits 47.02%, and promptfoo/promptfoo hits 44.17%. By contrast, louislam/uptime-kuma earns 14.90% of its citations from its GitHub wiki, while owasp/devsecopsguideline receives citations on 131 questions yet rarely maps to a single commercial brand (only 14 answers matched GitHub).

**Top 25 most-cited GitHub repositories in organic AI buyer answers**

| Repository | Attributed brand | Questions | Occurrences | Root (%) | Blob (%) | #1 rate, cited answers (%) | #1 rate, when mentioned (%) |
| --- | --- | --- | --- | --- | --- | --- | --- |
| arize-ai/phoenix | Arize Phoenix | 251 | 625 | 73.53 | 26.13 | 18.24 | 19.28 |
| signoz/signoz | SigNoz | 186 | 441 | 80.6 | 18.94 | 18.29 | 18.38 |
| louislam/uptime-kuma | Uptime Kuma | 182 | 782 | 78.69 | 5.75 | 40.19 | 40.32 |
| openobserve/openobserve | OpenObserve | 176 | 530 | 90.61 | 7.14 | 13.76 | 13.88 |
| grafana/loki | Grafana Loki | 160 | 405 | 56.04 | 43.7 | 46.75 | 47.02 |
| langchain-ai/docs | LangChain LangGraph | 141 | 241 | 0.42 | 99.58 | 34.27 | 50.34 |
| owasp/devsecopsguideline | OWASP (unattributed / GitHub mentioned) | 131 | 178 | 0 | 100 | 1.17 | 14.29 |
| github/docs | GitHub | 120 | 177 | 0 | 100 | 7.55 | 20.34 |
| langfuse/langfuse-docs | Langfuse | 117 | 244 | 0 | 100 | 40.3 | 40.7 |
| grafana/grafana | Grafana | 117 | 211 | 46.63 | 52.4 | 16.41 | 18.6 |
| clickhouse/clickhouse-docs | ClickHouse | 116 | 350 | 0 | 100 | 17.41 | 17.94 |
| semgrep/semgrep | Semgrep | 111 | 216 | 87.14 | 12.38 | 37.19 | 37.37 |
| open-telemetry/semantic-conventions-genai | OpenTelemetry | 103 | 374 | 4.96 | 95.04 | 38.27 | 40.26 |
| promptfoo/promptfoo | Promptfoo | 101 | 186 | 54.1 | 45.36 | 44.17 | 44.17 |
| clickhouse/clickstack | ClickStack | 95 | 176 | 99.36 | 0.64 | 18.84 | 20.47 |
| pgvector/pgvector | pgvector | 90 | 246 | 76.92 | 23.08 | 9.95 | 9.95 |
| bunnyway/documentation | Bunny | 87 | 219 | 9.27 | 90.73 | 7.69 | 12.39 |
| backstage/backstage | Backstage | 85 | 183 | 32.6 | 66.3 | 51.9 | 57.34 |
| confident-ai/deepeval | DeepEval | 84 | 147 | 92.41 | 5.52 | 19.01 | 19.29 |
| microsoftdocs/azure-ai-docs | Azure AI Document Intelligence | 77 | 105 | 0 | 100 | 7.61 | 25 |
| open-telemetry/opentelemetry.io | OpenTelemetry | 76 | 123 | 0 | 100 | 52.21 | 60.2 |
| vllm-project/vllm | vLLM | 75 | 205 | 16.92 | 72.64 | 24.55 | 25.79 |
| evidentlyai/evidently | Evidently | 73 | 199 | 95.03 | 4.97 | 35.48 | 37.67 |
| microsoft/opentelemetry-semantic-conventions | OpenTelemetry | 72 | 134 | 0 | 100 | 19.33 | 21.5 |
| snyk/user-docs | Snyk | 70 | 131 | 0 | 100 | 22.33 | 27.06 |

_Ranked by distinct organic buyer questions citing the repo, Sep 1 to Nov 19, 2026 across ChatGPT Search, Google AI Mode, and Perplexity._

> Public Markdown docs repos (langfuse-docs, clickhouse-docs, snyk/user-docs) earn hundreds of AI citations even without owning a software runtime.

## GitHub plus owned-site citations lift #1 brand win rate by 34.5% on ChatGPT and 30.6% on Google

Does a GitHub citation actually win #1 product recommendations, or do AI engines just drop the repo link for background context? Across 163,874 tech-market answer-brand pairs from October 20 to November 19, 2026 on questions where github.com appeared, combining a GitHub citation with an owned-website citation yields the strongest recommendation rate on both engines.

On ChatGPT Search (82,097 pairs), brands cited via GitHub plus their own website win the #1 recommendation slot 22.23% of the time (597 of 2,686 pairs, mean recommendation rank 3.96), a 34.5% relative lift over owned-site citations without GitHub (16.53%, mean rank 4.72). Yet GitHub citations without an owned site win #1 only 10.69% of the time (mean rank 5.54), trailing even third-party-only citations (14.16%). On Google AI Mode (81,568 pairs), GitHub plus own site climbs to a 42.05% #1 win rate (37 of 88, mean rank 2.58), up 30.6% over own-site alone (32.19%) and 4.6x uncited mentions (9.20%).

**#1 brand recommendation rate by citation backing on GitHub-citing tech questions**

| Item | Value |
| --- | --- |
| GitHub + own site: ChatGPT Search | 22.23% (597 of 2,686) |
| GitHub + own site: Google AI Mode | 42.05% (37 of 88) |
| Own site (no GitHub): ChatGPT Search | 16.53% (4,039 of 24,441) |
| Own site (no GitHub): Google AI Mode | 32.19% (1,554 of 4,828) |
| GitHub (no own site): ChatGPT Search | 10.69% (208 of 1,945) |
| GitHub (no own site): Google AI Mode | 31.18% (130 of 417) |
| Third-party (no GitHub): ChatGPT Search | 14.16% (265 of 1,872) |
| Third-party (no GitHub): Google AI Mode | 19.32% (1,853 of 9,593) |
| No attributed citation: ChatGPT Search | 8.99% (4,597 of 51,153) |
| No attributed citation: Google AI Mode | 9.20% (6,134 of 66,642) |

_Oct 20 to Nov 19, 2026 across 82,097 ChatGPT Search and 81,568 Google AI Mode answer-brand pairs (Perplexity recorded 209 unattributed pairs at 13.40%)._

> GitHub alone wins #1 half as often as GitHub paired with your own domain (10.69% vs 22.23% on ChatGPT); link your repo README cleanly back to your product site and docs.

## GitHub beats Stack Overflow 71.3-to-1 and all package registries combined 85.6-to-1

While Stack Overflow's 2025 Developer Survey shows 84% of developers using or planning to use AI tools alongside traditional search, AI answer engines rarely link back to classic Q&A threads or package registry listings. Across September 1 to November 19, 2026, github.com's 41,065 citation rows outpace the entire Stack Overflow / Stack Exchange network (576 rows across Stack Overflow, Server Fault, Super User, Ask Ubuntu, and Stack Exchange) by 71.3-to-1 overall, and by 356.6-to-1 on ChatGPT Search (36,019 vs 101).

GitHub also beats PyPI (215 rows), npm (200), Docker Hub (35), and crates.io/Go/RubyGems/NuGet/Packagist combined (30) by 85.6-to-1 (41,065 vs 480). Alongside github.com, *.github.io project pages add 8,066 rows, docs.github.com adds 4,813, and Hugging Face adds 1,781. In November 1 to 19 three-engine comparisons, github.com appears in 4.859% of all ChatGPT Search answers (0.9004% of citations), 2.574% of Perplexity answers (0.4341%), and 0.829% of Google AI Mode answers (0.3932%).

**Developer and open-source ecosystem citations across AI engines**

| Ecosystem | Engine | Citation rows | Questions | Tech-market rows |
| --- | --- | --- | --- | --- |
| reddit.com | Google AI Mode | 53270 | 20295 | 17226 |
| github.com | ChatGPT Search | 36019 | 8791 | 20278 |
| *.github.io | ChatGPT Search | 7512 | 2706 | 4195 |
| reddit.com | ChatGPT Search | 6968 | 1696 | 226 |
| github.com | Google AI Mode | 4999 | 2217 | 2576 |
| docs.github.com | ChatGPT Search | 4527 | 991 | 2955 |
| huggingface.co | ChatGPT Search | 1528 | 355 | 724 |
| *.github.io | Google AI Mode | 552 | 325 | 264 |
| stackoverflow_network | Google AI Mode | 475 | 218 | 160 |
| docs.github.com | Google AI Mode | 284 | 120 | 190 |
| huggingface.co | Google AI Mode | 252 | 138 | 126 |
| pypi.org | ChatGPT Search | 171 | 98 | 77 |
| npmjs.com | ChatGPT Search | 156 | 73 | 25 |
| gist.github.com | Google AI Mode | 120 | 78 | 70 |
| stackoverflow_network | ChatGPT Search | 101 | 38 | 8 |
| github.com | Perplexity | 47 | 26 | 14 |
| npmjs.com | Google AI Mode | 44 | 26 | 14 |
| pypi.org | Google AI Mode | 40 | 37 | 24 |
| reddit.com | Perplexity | 26 | 16 | 0 |
| other_pkg_registries | ChatGPT Search | 23 | 16 | 15 |

Showing 20 of 22 rows (Sep 1 to Nov 19 totals). Full CSV: /research/github-repos-and-docs-architecture-in-ai-search/dataset.csv

_Switch views between Sep 1 to Nov 19 totals and Nov 1 to Nov 19 matched-window citation and answer shares._

> Package registries and Stack Overflow together account for barely 2.6% of GitHub's AI citation footprint; invest in GitHub READMEs and hosted docs first.

## Google AI Mode dominates technical Reddit citations by up to 730-to-1 over ChatGPT Search

If ChatGPT Search leans on GitHub and product documentation, Google AI Mode leans heavily on developer subreddits. In November 1 to 19, 2026, Reddit accounted for 4.6899% of all Google AI Mode citations (appearing in 9.960% of cited answers) compared with just 0.0406% of ChatGPT Search citations (0.267% of answers), a 115.5x share gap.

Across 24 developer and infrastructure subreddits from September 1 to November 19, r/devops leads with 1,417 rows (1,408 Google AI Mode vs 9 ChatGPT Search), followed by r/saas (1,328: 1,144 vs 184), r/selfhosted (731: 730 vs 1), r/sysadmin (514: 512 vs 2), r/kubernetes (486: 481 vs 5), r/webdev (446: 444 vs 2), and r/cybersecurity (287: 285 vs 2). Only r/machinelearning shows meaningful ChatGPT Search overlap (79 ChatGPT vs 108 Google AI Mode).

**Top 15 developer and infrastructure subreddits in AI citations**

| Subreddit | Total rows | Questions | Google AI Mode | ChatGPT Search | Nov 1 to 19 rows |
| --- | --- | --- | --- | --- | --- |
| r/devops | 1417 | 688 | 1408 | 9 | 241 |
| r/saas | 1328 | 641 | 1144 | 184 | 327 |
| r/selfhosted | 731 | 388 | 730 | 1 | 138 |
| r/sysadmin | 514 | 316 | 512 | 2 | 90 |
| r/kubernetes | 486 | 214 | 481 | 5 | 97 |
| r/webdev | 446 | 260 | 444 | 2 | 46 |
| r/cybersecurity | 287 | 160 | 285 | 2 | 80 |
| r/machinelearning | 187 | 64 | 108 | 79 | 4 |
| r/dataengineering | 187 | 130 | 187 | 0 | 46 |
| r/localllama | 186 | 134 | 176 | 10 | 42 |
| r/node | 102 | 50 | 101 | 1 | 8 |
| r/aws | 83 | 55 | 82 | 1 | 9 |
| r/homelab | 79 | 43 | 79 | 0 | 32 |
| r/python | 38 | 24 | 38 | 0 | 5 |
| r/reactjs | 37 | 27 | 37 | 0 | 2 |

_Sep 1 to Nov 19, 2026 organic citations across ChatGPT Search, Google AI Mode, and Perplexity (0 Perplexity citations recorded in this 24-subreddit set)._

> Engineering reputation in r/devops, r/selfhosted, and r/kubernetes drives Google AI Mode visibility far more than it drives ChatGPT Search.

## ChatGPT cites docs 2.38x over blogs in tech markets while Google (0.20x) and Perplexity (0.10x) flip 23.8x

Across 1,521,062 citation rows in 361 active tech markets, the three AI engines flip completely on documentation versus blog content. ChatGPT Search devotes 19.19% of its tech-market citations to documentation surfaces (219,035 of 1,141,291 rows) vs 8.07% to blogs (92,131), a 2.38-to-1 docs advantage. Google AI Mode cites docs only 5.58% of the time (21,108 of 377,951) vs 27.72% blogs (104,752), a 0.20-to-1 ratio, while Perplexity drops to 4.18% docs vs 41.10% blogs (0.10-to-1), a 23.8x inversion from ChatGPT Search.

Controlling for prompt mix confirms the split. Across 146 matched tech-market questions answered by all three engines in November 1 to 19, ChatGPT Search gave 12.67% of its links to docs vs 10.22% to blogs; Google AI Mode gave 2.96% to docs vs 29.67% to blogs (plus 8.49% to Reddit); and Perplexity gave 3.13% to docs vs 42.99% to blogs. Meanwhile, across 1,257 brand-owned websites cited on both surfaces in tech markets, documentation outperformed blogs 2.16-to-1 (178,598 vs 82,821 rows, winning on 637 of 1,257 brands).

**Tech-market citation share: docs surfaces vs blog surfaces by AI engine**

| Item | Value |
| --- | --- |
| Docs surfaces: ChatGPT Search | 19.19% (219,035 of 1,141,291) |
| Docs surfaces: Google AI Mode | 5.58% (21,108 of 377,951) |
| Docs surfaces: Perplexity | 4.18% (76 of 1,820) |
| Blog surfaces: ChatGPT Search | 8.07% (92,131 of 1,141,291) |
| Blog surfaces: Google AI Mode | 27.72% (104,752 of 377,951) |
| Blog surfaces: Perplexity | 41.10% (748 of 1,820) |

_1,521,062 tech-market citation rows across 361 active markets in nine technical Parse industry groups (Sep 1 to Nov 19, 2026; Perplexity Nov 1 to 19)._

> Documentation drives ChatGPT Search, whereas editorial and blog guides drive Google AI Mode and Perplexity; B2B tech teams need both surfaces in sync.

## Subdirectory /docs/ URLs earn 24.1% more citations per page, while /blog/ crushes blog. subdomains 21.8-to-1

URL architecture splits differently for docs than for blogs across brand-owned tech domains. Dedicated docs.* subdomains reach more total brands (1,676 root domains generating 107,813 citation rows across 22,452 URLs) than /docs/* subdirectories (1,071 root domains generating 70,030 rows across 11,751 URLs), and pure-subdomain hosts outnumber pure-subdirectory hosts 1,810 to 1,016 (80,792 vs 42,666 rows).

Yet /docs/* subdirectories earn 24.1% higher citation density per URL: 6.33 occurrences per URL (and 0.69 questions per URL) vs 5.10 occurrences per URL (and 0.51 questions per URL) on docs.* subdomains. On blogs, there is no close contest: /blog/* subdirectories generate 160,760 citation rows across 8,310 domains compared with just 7,378 rows across 367 blog.* subdomains, a 21.8-to-1 volume lead.

**Brand-owned tech documentation and marketing URL architectures**

| URL architecture | Citation rows | Distinct URLs | Root domains | Occ / URL | Questions / URL |
| --- | --- | --- | --- | --- | --- |
| Other brand pages | 722138 | 158978 | 21671 | 4.8 | 0.15 |
| Homepage | 217745 | 14441 | 11945 | 15.65 | 1.38 |
| Subdirectory /blog/* | 160760 | 35210 | 8310 | 4.58 | 0.57 |
| Subdomain docs.* | 107813 | 22452 | 1676 | 5.1 | 0.51 |
| Subdirectory /docs/* | 70030 | 11751 | 1071 | 6.33 | 0.69 |
| Subdomain help.*/support.*/kb.* | 63556 | 18301 | 1416 | 3.58 | 0.55 |
| Subdomain learn.* | 32322 | 6982 | 63 | 4.87 | 0.87 |
| Subdomain developer.*/api.* | 22178 | 4721 | 445 | 4.98 | 0.93 |
| Subdirectory /learn/* or /guides/* | 20347 | 4285 | 946 | 4.79 | 1.8 |
| Subdirectory /help/* or /support/* | 11445 | 3058 | 432 | 3.87 | 1.1 |
| Subdomain blog.* | 7378 | 1780 | 367 | 4.16 | 1.59 |
| Subdirectory /developer/* or /api/* | 2088 | 643 | 246 | 3.51 | 1.28 |

_Sep 1 to Nov 19, 2026 tech-market citations across tracked brand domains._

> Both docs.* and /docs/* earn massive AI citations, though /docs/* averages 24.1% more occurrences per URL; for blogs, keep /blog/* on the main domain.

## Cloud, observability, and API-first docs hosts hit up to 35.5 occurrences per cited URL

Within tech markets, learn.microsoft.com leads overall docs volume (30,037 rows, 31,653 occurrences across 6,532 URLs), ahead of grafana.com (16,301 rows, 17,105 occurrences) and docs.aws.amazon.com (16,185 rows). Yet lean documentation centers match enterprise scale on efficiency: docs.cloudzero.com averages 35.51 occurrences per cited URL (41 URLs generating 1,456 occurrences), docs.pagerduty.com averages 25.72, prometheus.io averages 23.10, opentelemetry.io averages 22.99, and langfuse.com averages 20.77.

Across hosted vendor docs subdomains, *.github.io leads with 712 subdomains and 8,066 citation rows, followed by *.readthedocs.io (223 subdomains, 2,347 rows), *.mintlify.app (75 subdomains, 280 rows), *.gitbook.io (57 subdomains, 216 rows), *.readme.io (29 subdomains, 203 rows), and *.notion.site (11 subdomains, 20 rows). Many commercial Mintlify, ReadMe, and GitBook customers run on custom docs.* or /docs/* domains rather than vendor subdomains.

**Top 25 tech-market docs hosts and hosted vendor docs subdomains**

| Host | Layout | Citation rows | Distinct URLs | Occ / URL |
| --- | --- | --- | --- | --- |
| learn.microsoft.com | subdomain | 30037 | 6532 | 4.85 |
| grafana.com | subdir_path | 16301 | 1224 | 13.97 |
| docs.aws.amazon.com | subdomain | 16185 | 3449 | 4.94 |
| docs.datadoghq.com | subdomain | 9471 | 859 | 12 |
| docs.cloud.google.com | subdomain | 8054 | 1741 | 4.92 |
| developers.cloudflare.com | subdomain | 7399 | 581 | 13.62 |
| docs.newrelic.com | subdomain | 6270 | 447 | 15.34 |
| docs.dynatrace.com | subdomain | 4554 | 351 | 14.03 |
| opentelemetry.io | subdir_path | 4297 | 195 | 22.99 |
| elastic.co | subdir_path | 3501 | 421 | 9.09 |
| docs.pagerduty.com | subdomain | 3408 | 145 | 25.72 |
| docs.github.com | subdomain | 3147 | 781 | 4.17 |
| signoz.io | subdir_path | 2061 | 151 | 14.21 |
| docs.gitlab.com | subdomain | 1978 | 333 | 6.26 |
| docs.oracle.com | subdomain | 1733 | 655 | 2.75 |
| docs.victoriametrics.com | subdomain | 1608 | 131 | 13.09 |
| docs.firehydrant.com | subdomain | 1545 | 81 | 20.79 |
| prometheus.io | subdir_path | 1527 | 70 | 23.1 |
| ibm.com | subdir_path | 1474 | 499 | 3.15 |
| kubernetes.io | subdir_path | 1458 | 105 | 15.13 |

Showing 20 of 25 rows (Top 25 tech docs hosts). Full CSV: /research/github-repos-and-docs-architecture-in-ai-search/dataset.csv

_Sep 1 to Nov 19, 2026 organic citations. Switch views to inspect top 25 tech docs hosts or hosted vendor subdomain platforms._

> Focused docs hubs like CloudZero (35.51 occ/URL), PagerDuty (25.72), and Langfuse (20.77) punch far above their page count.

## 65.0% of the top 60 live tech docs hosts serve /llms.txt and 38.3% expose .md endpoints

Live HTTP fingerprinting of the top 60 AI-cited tech documentation hosts shows rapid adoption of machine-readable documentation standards. Exactly 39 of 60 hosts (65.0%) return HTTP 200 on /llms.txt, and 23 of 60 (38.33%) expose Markdown-native .md endpoints, outpacing Parse's broader November check of 246 general root domains, where 107 (43.50%) served /llms.txt.

Leading technical teams across multiple stacks ship both /llms.txt and .md endpoints, including docs.aws.amazon.com, docs.datadoghq.com, docs.pagerduty.com, elastic.co, docs.github.com, signoz.io, docs.firehydrant.com, langfuse.com, docs.cloudzero.com, and docs.langchain.com. On stack share, Custom or Enterprise CMS powers 26 of the 60 hosts, Next.js powers 12, Docusaurus powers 7, ReadMe powers 4, Astro/Starlight powers 3, Gatsby powers 3, Mintlify powers 2, GitBook powers 1, Redocly powers 1, and 1 host (grafana.com) errored on the probe.

**Documentation platforms across top 60 live AI-cited tech docs hosts**

| Item | Value |
| --- | --- |
| Custom / Enterprise CMS | 26 hosts (43.3%) |
| Next.js (Custom) | 12 hosts (20.0%) |
| Docusaurus | 7 hosts (11.7%) |
| ReadMe | 4 hosts (6.7%) |
| Astro / Starlight | 3 hosts (5.0%) |
| Gatsby | 3 hosts (5.0%) |
| Mintlify | 2 hosts (3.3%) |
| GitBook | 1 host (1.7%) |
| Redocly | 1 host (1.7%) |
| Probe fetch error | 1 host (1.7%) |

_Live HTTP stack and /llms.txt probe across the top 60 cited tech docs hosts (Nov 20, 2026): 39 of 60 (65.0%) served /llms.txt; 23 of 60 (38.33%) served .md endpoints._

> Custom Next.js and Docusaurus sites lead top-60 adoption alongside ReadMe and Mintlify; two-thirds of the top docs hosts already expose /llms.txt.

## Study scope, counting rules, and observational boundaries

This study covers organic buyer prompts only across September 1 to November 19, 2026 for ChatGPT Search (3,897,894 citation rows) and Google AI Mode (1,258,109 rows), plus November 1 to November 19, 2026 for Perplexity (10,827 rows). Tech-market cuts filter to 361 active markets across nine technical Parse industry groups (1,521,062 total citation rows). Paired three-engine docs-vs-blog comparisons use 146 matched tech questions answered by all three engines between November 1 and November 19, 2026.

Brand recommendation lift (163,874 answer-brand pairs from October 20 to November 19, 2026) measures observed co-occurrence on GitHub-citing tech questions and does not prove that adding a repo alone forces a #1 rank; well-known projects naturally attract both GitHub stars and owned-domain citations. Similarly, the 24.1% occurrence-per-URL gap between /docs/* and docs.* reflects observational citations across existing sites rather than a before/after domain migration experiment.

## What DevRel, docs, and growth engineering teams should do next

Treat your public GitHub repositories and product documentation as core AI acquisition assets, not secondary developer chores. Put plain-English architecture summaries, installation quickstarts, supported integrations, and canonical links to your primary website at the top of every repo README, and mirror multi-page manuals as clean Markdown files inside the repo where ChatGPT Search looks first.

At the same time, recognize the engine split: pair server-rendered product docs (/docs/* or docs.*) for ChatGPT Search with deep technical blog comparisons on /blog/* and active engineering participation in r/devops, r/kubernetes, and r/selfhosted for Google AI Mode and Perplexity. Check your own cited docs, GitHub repos, and rival domains directly with Parse MCP tools (search_cited_pages, query_metrics, fetch_live_pages, check_brand).

**DevRel and documentation AI visibility checklist**

| Surface | Study benchmark | Engineering and DevRel action |
| --- | --- | --- |
| GitHub repo roots and Markdown blobs | 88.55% of all GitHub citations | Lead READMEs with plain-English use cases, setup commands, and canonical links back to your main product site. |
| GitHub + owned-site pairing | 22.23% vs 10.69% #1 rate (ChatGPT) | Cross-link your GitHub org, README, and owned /docs pages so answers attribute and rank your brand. |
| Google AI Mode Issues & Discussions | 5.54% share (36.9x ChatGPT) | Close stale bug threads with clear workarounds and link canonical docs inside GitHub Discussions. |
| Docs vs /blog/* engine split | ChatGPT 2.38x docs; Perplexity 0.10x | Pair crawlable HTML /docs/* guides with deep technical comparisons on /blog/* on your root domain. |
| Machine-readable docs (/llms.txt + .md) | 65.0% /llms.txt; 38.33% .md (top 60) | Expose /llms.txt and clean .md twins alongside static server-rendered HTML documentation. |

> Combine readable READMEs and Markdown docs on GitHub with server-rendered /docs/* and /blog/* pages on your primary domain.

Related: [Plan documentation updates around buyer prompts](https://parse.gl/use-cases/plan-content) · [Research technical domains shaping your market](https://parse.gl/use-cases/research-a-market) · [Inspect live cited docs and repos via Parse MCP](https://parse.gl/mcp) · [Why AI agents fail to read SaaS pricing and changelog pages](https://parse.gl/research/why-ai-agents-fail-to-read-pricing-and-changelog-pages) · [When does AI cite documentation pages?](https://parse.gl/research/do-documentation-pages-get-cited-by-ai) · [DevRel and GitHub AI visibility playbook](https://parse.gl/blog/devrel-and-github-ai-visibility-playbook) · [Docs as an AI acquisition channel](https://parse.gl/blog/docs-as-an-ai-acquisition-channel)

## Method

We analyzed 5,166,830 organic AI citation rows across ChatGPT Search (3,897,894) and Google AI Mode (1,258,109) from September 1 to November 19, 2026, plus Perplexity (10,827) from November 1 to November 19, 2026. That corpus includes 41,065 github.com citation rows (43,179 occurrences across 10,318 distinct URLs), 1,521,062 tech-market citation rows across 361 active markets in nine technical Parse industry groups, 163,874 answer-brand pairs from October 20 to November 19, 2026, and live HTTP platform, /llms.txt, and .md checks across the top 60 cited tech docs hosts alongside 246 root-domain checks.

## Data

- [Full study dataset (CSV)](https://parse.gl/research/github-repos-and-docs-architecture-in-ai-search/dataset.csv): All 207 rows across GitHub URL anatomy, top 25 repos, #1 brand recommendation lift, developer ecosystems, subreddits, docs vs blog splits, top 25 docs hosts, and /llms.txt platform probes.

## Sources

- [Stack Overflow: 2025 Developer Survey (AI)](https://survey.stackoverflow.co/2025/ai)
- [llms.txt specification (llmstxt.org)](https://llmstxt.org/)
- [Ahrefs: AI search traffic by page type](https://ahrefs.com/blog/ai-search-traffic-by-page-type-ahrefs/)
- [Ahrefs: LLM citations guide](https://ahrefs.com/blog/llm-citations/)
- [Semrush: How technical SEO factors affect AI citations](https://www.semrush.com/blog/technical-seo-impact-on-ai-search-study/)

## For agents

- [Study dataset (CSV)](https://parse.gl/research/github-repos-and-docs-architecture-in-ai-search/dataset.csv)
- Any brand's shares and rivals, with 95% ranges: `https://agent.parse.gl/v1/tools/check_brand?subject=%3Cbrand-domain%3E`
- Sample answers in a market: `https://agent.parse.gl/v1/tools/search_answers?args=%7B%22filter%22%3A%7B%22market%22%3A%5B%22%3Cmkt_id%3E%22%5D%7D%7D`
- Cited pages in a market: `https://agent.parse.gl/v1/tools/search_cited_pages?args=%7B%22filter%22%3A%7B%22market%22%3A%5B%22%3Cmkt_id%3E%22%5D%7D%7D`
- Search the index: `https://parse.gl/api/public/search?q=<words>`

Reuse: Figures and tables on this page are free to republish with attribution: a link to https://parse.gl/research/github-repos-and-docs-architecture-in-ai-search beside them. A standard followed link (dofollow) is preferred.

- No account: Public figures and up to 5 examples per list, about 120 brands a day per address.
- Free account: $5 in credit, your brand's first check (20 buyer questions) and a free weekly check.
- After your first top-up: Exports and deeper search results. The first top-up starts at $5.
- Live checks: $0.01 per question per engine ($0.05 on Gemini and Claude).
- Full public answers and pages: 25 free per day, then $0.005 each.
- Public answers older than 90 days: $0.001 each the first time your workspace counts or lists one, then yours.
- An agent can save work before signup: `POST https://agent.parse.gl/v1/workspaces`
- Connect an assistant: `https://agent.parse.gl/mcp`

[Prices](https://parse.gl/pricing.md) · [Map of the site](https://parse.gl/llms.txt)
