Parse
IndexPricing
Sign in
  1. Research
Research
GitHub repos, package registries, and docs architecture in AI search

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

Published Nov 20, 2026

On this page
  • GitHub URL anatomy
  • Issues and Discussions
  • Top 25 GitHub repos
  • #1 brand win lift
  • Dev ecosystem shares
  • Technical subreddits
  • Docs vs blog inversion
  • Subdomain vs subfolder
  • Top 25 docs hosts
  • /llms.txt and docs CMS
  • Study scope
  • DevRel & docs playbook
  • How we measured
  • Sources
  • More like this
  • GitHub URL anatomy
  • Issues and Discussions
  • Top 25 GitHub repos
  • #1 brand win lift
  • Dev ecosystem shares
  • Technical subreddits
  • Docs vs blog inversion
  • Subdomain vs subfolder
  • Top 25 docs hosts
  • /llms.txt and docs CMS
  • Study scope
  • DevRel & docs playbook
  • How we measured
  • Sources
  • More like this

Dimitry ApollonskyFounder, Parse

DataWhat reviewed means

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.

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).

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%).

GitHub links hitting READMEs or Markdown docs
88.55%

24,274 repo roots + 12,088 Markdown blobs (41,065 rows)

96.01% of /blob/ links are Markdown; 1.22% overall are code/config

ChatGPT #1 win rate with GitHub + own site
22.23%

vs 16.53% own-site alone (+34.5% relative lift)

Google AI Mode reaches 42.05% vs 32.19% own-site alone

ChatGPT docs-to-blog citation ratio in tech
2.38x

19.19% docs vs 8.07% blogs across 1,141,291 rows

Google AI Mode flips to 0.20x; Perplexity flips to 0.10x

Top 60 live tech docs hosts serving /llms.txt
65.0%

39 of 60 serve /llms.txt; 23 of 60 (38.33%) serve .md URLs

Compared with 43.50% (107 of 246) across general root domains

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

  • Repository root and README59.11%24,274 rows
  • Markdown or text docs (/blob/)29.44%12,088 rows
  • GitHub product and marketing pages5.69%2,337 rows
  • Org or user profile pages2.16%887 rows
  • Source code or config (/blob/)1.22%502 rows
  • Repository wikis0.67%276 rows
  • GitHub Issues0.52%215 rows
  • Tree or raw directories0.45%183 rows
  • GitHub Discussions0.29%119 rows
  • Releases and tags0.23%93 rows
  • 0%20%40%60%
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).

Takeaway

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%

11,767 of 36,019 ChatGPT rows vs 297 of 4,999 Google rows

Perplexity reached 51.06% (24 of 47 rows in Nov)

Issues + Discussions: Google vs ChatGPT
5.54% vs 0.15%

277 of 4,999 Google rows vs 56 of 36,019 ChatGPT rows

36.9x higher troubleshooting thread reliance on Google AI Mode

Google AI Mode GitHub links hitting repo roots
77.20%

3,859 of 4,999 Google GitHub citation rows

Compared with 56.63% on ChatGPT Search (20,399 rows)

Share of GitHub citations going to releases/tags
0.23%

93 of 41,065 rows (78 ChatGPT, 15 Google AI Mode)

Changelog and version summaries earn more value inside README/docs

Takeaway

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

Questions · Top 10 of 25

  • arize-ai/phoenix251
  • signoz/signoz186
  • louislam/uptime-kuma182
  • openobserve/openobserve176
  • grafana/loki160
  • langchain-ai/docs141
  • owasp/devsecopsguideline131
  • github/docs120
  • langfuse/langfuse-docs117
  • grafana/grafana117
  • 0100200300
Explore the data (25 rows)
arize-ai/phoenixArize Phoenix25162573.5326.1318.2419.28
signoz/signozSigNoz18644180.618.9418.2918.38
louislam/uptime-kumaUptime Kuma18278278.695.7540.1940.32
openobserve/openobserveOpenObserve17653090.617.1413.7613.88
grafana/lokiGrafana Loki16040556.0443.746.7547.02
langchain-ai/docsLangChain LangGraph1412410.4299.5834.2750.34
owasp/devsecopsguidelineOWASP (unattributed / GitHub mentioned)13117801001.1714.29
github/docsGitHub12017701007.5520.34
langfuse/langfuse-docsLangfuse117244010040.340.7
grafana/grafanaGrafana11721146.6352.416.4118.6
clickhouse/clickhouse-docsClickHouse116350010017.4117.94
semgrep/semgrepSemgrep11121687.1412.3837.1937.37
open-telemetry/semantic-conventions-genaiOpenTelemetry1033744.9695.0438.2740.26
promptfoo/promptfooPromptfoo10118654.145.3644.1744.17
clickhouse/clickstackClickStack9517699.360.6418.8420.47
pgvector/pgvectorpgvector9024676.9223.089.959.95
bunnyway/documentationBunny872199.2790.737.6912.39
backstage/backstageBackstage8518332.666.351.957.34
confident-ai/deepevalDeepEval8414792.415.5219.0119.29
microsoftdocs/azure-ai-docsAzure AI Document Intelligence7710501007.6125
open-telemetry/opentelemetry.ioOpenTelemetry76123010052.2160.2
vllm-project/vllmvLLM7520516.9272.6424.5525.79
evidentlyai/evidentlyEvidently7319995.034.9735.4837.67
microsoft/opentelemetry-semantic-conventionsOpenTelemetry72134010019.3321.5
snyk/user-docsSnyk70131010022.3327.06
Ranked by distinct organic buyer questions citing the repo, Sep 1 to Nov 19, 2026 across ChatGPT Search, Google AI Mode, and Perplexity.

Takeaway

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

  • ChatGPT Search
  • Google AI Mode
  • GitHub + own site
  • ChatGPT Search22.23%597 of 2,686
  • Google AI Mode42.05%37 of 88
  • Own site (no GitHub)
  • ChatGPT Search16.53%4,039 of 24,441
  • Google AI Mode32.19%1,554 of 4,828
  • GitHub (no own site)
  • ChatGPT Search10.69%208 of 1,945
  • Google AI Mode31.18%130 of 417
  • Third-party (no GitHub)
  • ChatGPT Search14.16%265 of 1,872
  • Google AI Mode19.32%1,853 of 9,593
  • No attributed citation
  • ChatGPT Search8.99%4,597 of 51,153
  • Google AI Mode9.20%6,134 of 66,642
  • 0%20%40%60%
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%).

Takeaway

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

Citation rows and distinct buyer questions across ChatGPT Search and Google AI Mode (Sep 1 to Nov 19, 2026) plus Perplexity (Nov 1 to 19, 2026).

Citation rows · Top 10 of 22

  • reddit.com · Google AI Mode53,270
  • github.com · ChatGPT Search36,019
  • *.github.io · ChatGPT Search7,512
  • reddit.com · ChatGPT Search6,968
  • github.com · Google AI Mode4,999
  • docs.github.com · ChatGPT Search4,527
  • huggingface.co · ChatGPT Search1,528
  • *.github.io · Google AI Mode552
  • stackoverflow_network · Google AI Mode475
  • docs.github.com · Google AI Mode284
  • 020,00040,00060,000
Explore the data (22 rows)
reddit.comGoogle AI Mode53,27020,29517,226
github.comChatGPT Search36,0198,79120,278
*.github.ioChatGPT Search7,5122,7064,195
reddit.comChatGPT Search6,9681,696226
github.comGoogle AI Mode4,9992,2172,576
docs.github.comChatGPT Search4,5279912,955
huggingface.coChatGPT Search1,528355724
*.github.ioGoogle AI Mode552325264
stackoverflow_networkGoogle AI Mode475218160
docs.github.comGoogle AI Mode284120190
huggingface.coGoogle AI Mode252138126
pypi.orgChatGPT Search1719877
npmjs.comChatGPT Search1567325
gist.github.comGoogle AI Mode1207870
stackoverflow_networkChatGPT Search101388
github.comPerplexity472614
npmjs.comGoogle AI Mode442614
pypi.orgGoogle AI Mode403724
reddit.comPerplexity26160
other_pkg_registriesChatGPT Search231615
hub.docker.comChatGPT Search18917
hub.docker.comGoogle AI Mode171115
Switch views between Sep 1 to Nov 19 totals and Nov 1 to Nov 19 matched-window citation and answer shares.

Takeaway

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.
  • Stack Overflow: 2025 Developer Survey (AI)

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

Google AI Mode · Top 10 of 15

  • r/devops1,408
  • r/saas1,144
  • r/selfhosted730
  • r/sysadmin512
  • r/kubernetes481
  • r/webdev444
  • r/cybersecurity285
  • r/dataengineering187
  • r/localllama176
  • r/machinelearning108
  • 05001,0001,500
Explore the data (15 rows)
r/devops1,4176881,4089241
r/saas1,3286411,144184327
r/selfhosted7313887301138
r/sysadmin514316512290
r/kubernetes486214481597
r/webdev446260444246
r/cybersecurity287160285280
r/dataengineering187130187046
r/machinelearning18764108794
r/localllama1861341761042
r/node1025010118
r/aws83558219
r/homelab794379032
r/python38243805
r/reactjs37273702
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).

Takeaway

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

  • ChatGPT Search
  • Google AI Mode
  • Perplexity
  • Docs surfaces
  • ChatGPT Search19.19%219,035 of 1,141,291
  • Google AI Mode5.58%21,108 of 377,951
  • Perplexity4.18%76 of 1,820
  • Blog surfaces
  • ChatGPT Search8.07%92,131 of 1,141,291
  • Google AI Mode27.72%104,752 of 377,951
  • Perplexity41.10%748 of 1,820
  • 0%20%40%60%
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).

Takeaway

Documentation drives ChatGPT Search, whereas editorial and blog guides drive Google AI Mode and Perplexity; B2B tech teams need both surfaces in sync.
  • Ahrefs: AI search traffic by page type

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

Citation rows · Top 10 of 12

  • Other brand pages722,138
  • Homepage217,745
  • Subdirectory /blog/*160,760
  • Subdomain docs.*107,813
  • Subdirectory /docs/*70,030
  • Subdomain help.*/support.*/kb.*63,556
  • Subdomain learn.*32,322
  • Subdomain developer.*/api.*22,178
  • Subdirectory /learn/* or /guides/*20,347
  • Subdirectory /help/* or /support/*11,445
  • 0200,000400,000600,000800,000
Explore the data (12 rows)
Other brand pages722,138158,97821,6714.80.15
Homepage217,74514,44111,94515.651.38
Subdirectory /blog/*160,76035,2108,3104.580.57
Subdomain docs.*107,81322,4521,6765.10.51
Subdirectory /docs/*70,03011,7511,0716.330.69
Subdomain help.*/support.*/kb.*63,55618,3011,4163.580.55
Subdomain learn.*32,3226,982634.870.87
Subdomain developer.*/api.*22,1784,7214454.980.93
Subdirectory /learn/* or /guides/*20,3474,2859464.791.8
Subdirectory /help/* or /support/*11,4453,0584323.871.1
Subdomain blog.*7,3781,7803674.161.59
Subdirectory /developer/* or /api/*2,0886432463.511.28
Sep 1 to Nov 19, 2026 tech-market citations across tracked brand domains.

Takeaway

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.
  • Semrush: How technical SEO factors affect AI citations

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

Leading documentation hosts in tech markets by citation rows and occurrences per distinct URL.

Citation rows · Top 10 of 25

  • learn.microsoft.com30,037
  • grafana.com16,301
  • docs.aws.amazon.com16,185
  • docs.datadoghq.com9,471
  • docs.cloud.google.com8,054
  • developers.cloudflare.com7,399
  • docs.newrelic.com6,270
  • docs.dynatrace.com4,554
  • opentelemetry.io4,297
  • elastic.co3,501
  • 010,00020,00030,00040,000
Explore the data (25 rows)
learn.microsoft.comsubdomain30,0376,5324.85
grafana.comsubdir_path16,3011,22413.97
docs.aws.amazon.comsubdomain16,1853,4494.94
docs.datadoghq.comsubdomain9,47185912
docs.cloud.google.comsubdomain8,0541,7414.92
developers.cloudflare.comsubdomain7,39958113.62
docs.newrelic.comsubdomain6,27044715.34
docs.dynatrace.comsubdomain4,55435114.03
opentelemetry.iosubdir_path4,29719522.99
elastic.cosubdir_path3,5014219.09
docs.pagerduty.comsubdomain3,40814525.72
docs.github.comsubdomain3,1477814.17
signoz.iosubdir_path2,06115114.21
docs.gitlab.comsubdomain1,9783336.26
docs.oracle.comsubdomain1,7336552.75
docs.victoriametrics.comsubdomain1,60813113.09
docs.firehydrant.comsubdomain1,5458120.79
prometheus.iosubdir_path1,5277023.1
ibm.comsubdir_path1,4744993.15
kubernetes.iosubdir_path1,45810515.13
langfuse.comsubdir_path1,4167320.77
docs.cloudzero.comsubdomain1,3914135.51
help.sap.comsubdir_path1,3635662.46
developers.google.comsubdomain1,2904353.15
openobserve.aisubdir_path1,2187418.91
Sep 1 to Nov 19, 2026 organic citations. Switch views to inspect top 25 tech docs hosts or hosted vendor subdomain platforms.

Takeaway

Focused docs hubs like CloudZero (35.51 occ/URL), PagerDuty (25.72), and Langfuse (20.77) punch far above their page count.
  • Ahrefs: LLM citations guide

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

  • Custom / Enterprise CMS26 hosts43.3%
  • Next.js (Custom)12 hosts20.0%
  • Docusaurus7 hosts11.7%
  • ReadMe4 hosts6.7%
  • Astro / Starlight3 hosts5.0%
  • Gatsby3 hosts5.0%
  • Mintlify2 hosts3.3%
  • GitBook1 host1.7%
  • Redocly1 host1.7%
  • Probe fetch error1 host1.7%
  • 0102030
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.

Takeaway

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.
  • llms.txt specification (llmstxt.org)

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

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.
Google AI Mode Issues & Discussions5.54% share (36.9x ChatGPT)Close stale bug threads with clear workarounds and link canonical docs inside GitHub Discussions.
GitHub repo roots and Markdown blobs88.55% of all GitHub citationsLead READMEs with plain-English use cases, setup commands, and canonical links back to your main product site.
GitHub + owned-site pairing22.23% vs 10.69% #1 rate (ChatGPT)Cross-link your GitHub org, README, and owned /docs pages so answers attribute and rank your brand.
Docs vs /blog/* engine splitChatGPT 2.38x docs; Perplexity 0.10xPair crawlable HTML /docs/* guides with deep technical comparisons on /blog/* on your root domain.

Takeaway

Combine readable READMEs and Markdown docs on GitHub with server-rendered /docs/* and /blog/* pages on your primary domain.
  • Plan documentation updates around buyer prompts
  • Research technical domains shaping your market
  • Inspect live cited docs and repos via Parse MCP
  • Why AI agents fail to read SaaS pricing and changelog pages
  • When does AI cite documentation pages?
  • DevRel and GitHub AI visibility playbook
  • Docs as an AI acquisition channel

How we measured

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.

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

Get the data

Full study 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

  1. Stack Overflow: 2025 Developer Survey (AI) (opens in a new tab) · accessed November 20, 2026
  2. llms.txt specification (llmstxt.org) (opens in a new tab) · accessed November 20, 2026
  3. Ahrefs: AI search traffic by page type (opens in a new tab) · accessed November 20, 2026
  4. Ahrefs: LLM citations guide (opens in a new tab) · accessed November 20, 2026
  5. Semrush: How technical SEO factors affect AI citations (opens in a new tab) · accessed November 20, 2026

More like this

Why AI agents fail to read SaaS pricing and changelog pages
47.3% of 74 active top-SaaS /pricing endpoints fail plain-HTML delivery (14.9% WAF, 17.6% sales-gated, 9.5% JS-only, 5.4% partial JS) with 2.88% text-to-HTML.
When does AI cite documentation pages?
In Aug to Nov 2026, ChatGPT Search reached documentation on 16.75% of cited answers (6.60% of links) vs 4.50% on Google AI Mode (1.76% of links).
Most-cited domains in ChatGPT Search and Google AI Mode
Top-100 AI source leaderboards plus our Nov 2026 90-day refresh across 3.07M citations: docs lead ChatGPT Search while YouTube and Reddit lead Google AI Mode.
ChatGPT Search vs Google AI Mode: which sources each engine cites
Only 1 of the top 10 root domains (amazon.com) overlaps between ChatGPT Search and Google AI Mode across 3.07M citations (Aug to Nov 2026).
Which subreddits appear behind AI brand recommendations?
Practitioner subreddits led behind AI brand picks: r/devops ranked #1 across 7,771 subreddits while r/technology landed at #819.
Does being cited in AI answers mean being recommended?
Cited brands made AI's shortlist 99.3% of the time, yet took the #1 recommendation only 21.9% of the time.
Which brand-owned pages does AI cite by industry?
ChatGPT Search sends 35.16% of owned citations to homepages, Google AI Mode sends 19.87% to blogs, and docs peak at 24.91% in Software across 45 Aug to Nov 2026 industries.
HTML token bloat vs. Markdown twins and llms.txt across 300 AI-cited sites
46.00% of 300 top AI-cited sites serve /llms.txt and 15.00% honor Accept: text/markdown, cutting median page weight 25.41x across 62 paired pages while 19.67% fail plain HTTP fetch.
How AI recommends MCP and agent-native tools across 911,413 answers
94.96% of 6,292 MCP mentions across 911,413 answers happened unprompted (surging +127.12% on ChatGPT Search), while narrow agent/API topics flip #1 55.00% of the time.
For agents: this page as Markdown, https://parse.gl/research/github-repos-and-docs-architecture-in-ai-search.md. JSON, MCP · free for the last 90 days, checks from $0.01
Open in ChatGPT (opens in a new tab) Open in Claude (opens in a new tab)

This page

As Markdown: https://parse.gl/research/github-repos-and-docs-architecture-in-ai-search.md
As CSV: https://parse.gl/research/github-repos-and-docs-architecture-in-ai-search/dataset.csv
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.

Read and search

Any brand's shares and rivals, with 95% ranges: GET https://agent.parse.gl/v1/tools/check_brand?subject=%3Cbrand-domain%3E
Sample answers in a market: GET 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: GET 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: GET https://parse.gl/api/public/search?q=<words>

Connect

Connect an assistant: https://agent.parse.gl/mcp

An agent can save work before signup: POST https://agent.parse.gl/v1/workspaces

What it costs

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.

Prices: https://parse.gl/pricing.md

Map of the site: https://parse.gl/llms.txt

See which GitHub repos and docs pages earn AI citations in your market

Start free in your browser.
Parse

Index

  • Brands
  • Markets
  • Topics
  • How we measure

For agents

  • Docs
  • Connect
  • Workflows
  • llms.txt

Parse

  • Use cases
  • Pricing
  • Research
  • Blog
  • Compare

Company

  • About
  • Contact
  • Corrections

© 2026 Parse, Inc. All rights reserved.

Privacy PolicyTerms of Service