# GitHub and DevRel for AI visibility: the 41,065-citation playbook

> Across 41,065 GitHub citations, 88.6% hit repo roots and Markdown docs. Pairing GitHub with your site lifts ChatGPT #1 wins 34.5%. Get the DevRel playbook.

HTML: https://parse.gl/blog/devrel-and-github-ai-visibility-playbook · Site index: https://parse.gl/llms.txt · Published: 2026-11-20 · Updated: 2026-11-21

AI engines don't treat GitHub as a source code index; they treat it as a structured Markdown documentation store. Across **41,065** organic `github.com` citations in Parse's [GitHub and docs architecture study](https://parse.gl/research/github-repos-and-docs-architecture-in-ai-search), **88.55%** hit repository roots (`59.11%`) or Markdown docs files (`29.44%`), while only `0.68%` of `/blob/` citations point to code. Yet GitHub alone rarely wins the `#1` recommendation: pairing a GitHub citation with an owned-site citation lifts ChatGPT Search `#1` win rates by **34.5%** (`22.23%` vs `16.53%` own-site alone) and reaches **42.05%** on Google AI Mode.

We analyzed **5,171,139** organic AI citation rows from September 1 to November 19, 2026 (`3,897,894` ChatGPT Search, `1,258,109` Google AI Mode, and `10,827` Perplexity in November 1-19) alongside **163,874** tech-market brand-mention pairs across **361** active markets in nine tech industries (`Software`, `Information Technology`, `Artificial Intelligence`, `Data and Analytics`, `Internet Services`, `Apps`, `Collaboration`, `Science and Engineering`, and `Privacy and Security`). Parse's live index covers **853,414 active brands** across **1,774 markets** and **703 industries**, backed by **744,460** answers and **4,053,878** citations across **73,847** buyer questions (August 23 to November 20, 2026).

- **Of 41,065 GitHub citations hitting repo roots (59.11%) or Markdown docs blobs (29.44%):** 88.55% (Parse, Sep-Nov 2026)
- **ChatGPT #1 brand win-rate lift when GitHub pairs with own site (22.23% vs 16.53%):** +34.5% (Parse, Oct-Nov 2026)
- **More citations for github.com than all Stack Overflow / Stack Exchange sites combined (356.6× on ChatGPT):** 71.3× (Parse, Sep-Nov 2026)
- **Higher share of GitHub Issues + Discussions on Google AI Mode vs ChatGPT Search (5.54% vs 0.15%):** 36.9× (Parse, Sep-Nov 2026)

## What AI engines actually cite on GitHub

Developer relations teams often assume AI assistants crawl SDK source directories to verify implementation details. Our URL-anatomy breakdown of **41,065** `github.com` citation rows (`43,179` total occurrences across `10,318` distinct deduplicated URLs) shows the opposite: AI retrieval reads prose READMEs and Markdown documentation pages almost exclusively, while ignoring source code.

In the table below, we split every `github.com` citation row by URL path pattern and compare how ChatGPT Search, Google AI Mode, and Perplexity pull from each surface.

| GitHub URL pattern                          | Total rows | Share of GitHub | Distinct URLs | ChatGPT share | Google AI Mode share | Perplexity share |
| ------------------------------------------- | ---------: | --------------: | ------------: | ------------: | -------------------: | ---------------: |
| Repo root & README (`org/repo`)             |     24,274 |          59.11% |         5,242 |        56.63% |               77.20% |           34.04% |
| Markdown/text docs (`/blob/*.md`, `README`) |     12,088 |          29.44% |         3,927 |        32.67% |                5.94% |           51.06% |
| GitHub marketing & features                 |      2,337 |           5.69% |           178 |         5.83% |                4.72% |            0.00% |
| Org or user profile pages                   |        887 |           2.16% |           279 |         1.99% |                3.38% |            2.13% |
| Code or config `/blob/` files               |        502 |           1.22% |           240 |         1.27% |                0.90% |            2.13% |
| Repository Wiki (`/wiki`)                   |        276 |           0.67% |           114 |         0.59% |                1.22% |            2.13% |
| GitHub Issues (`/issues`)                   |        215 |           0.52% |           144 |         0.10% |                3.54% |            2.13% |
| Tree or raw directories                     |        183 |           0.45% |            27 |         0.51% |                0.00% |            0.00% |
| GitHub Discussions (`/discussions`)         |        119 |           0.29% |            56 |         0.05% |                2.00% |            0.00% |
| Releases, topics, PRs & other               |        184 |           0.44% |           111 |         0.35% |                1.10% |            6.38% |

Two operational lessons jump straight off that table. First, across all **12,590** `/blob/` file citations (`12,088` Markdown/text plus `502` code or config files), **96.01%** are `.md`, `.mdx`, `.rst`, `.adoc`, `.txt`, or `README` files, whereas only **85 rows (`0.68%`)** point to actual source code. Second, **Google AI Mode cites GitHub Issues (`3.54%`) and Discussions (`2.00%`) at `5.54%` combined, which is `36.9×` higher than ChatGPT Search (`0.15%`)**. Meanwhile, curated `awesome-*` lists accounted for **795** citations across **273** distinct `awesome-*` repositories, proving that third-party category indexes on GitHub still feed buyer shortlists.

## Why GitHub alone loses the #1 slot (and how own-site pairing wins)

Putting your entire go-to-market story on GitHub without strong product and documentation pages on your primary domain caps your win rate. To test whether a GitHub citation translates into `#1` product recommendations, we matched **82,097** ChatGPT Search and **81,568** Google AI Mode brand-mention pairs from October 20 to November 19, 2026 on tech-market questions where GitHub appeared in the citation pool.

The table below measures `#1` recommendation win rates and average recommendation rank across all five citation-backing combinations.

| Engine and citation backing               | Brands | Answer-brand pairs | Any recommendation | #1 recommendation rate | Average rec position |
| ----------------------------------------- | -----: | -----------------: | -----------------: | ---------------------: | -------------------: |
| ChatGPT: GitHub + own site                |    599 |              2,686 |             100.0% |                 22.23% |                 3.96 |
| ChatGPT: own site only (no GitHub)        |  3,056 |             24,441 |             100.0% |                 16.53% |                 4.72 |
| ChatGPT: third-party only (no GitHub)     |    636 |              1,872 |             100.0% |                 14.16% |                 5.48 |
| ChatGPT: GitHub only (no own site)        |    544 |              1,945 |             100.0% |                 10.69% |                 5.54 |
| ChatGPT: uncited brand mention            |  5,201 |             51,153 |             99.96% |                  8.99% |                 7.31 |
| Google AI Mode: GitHub + own site         |     66 |                 88 |             100.0% |                 42.05% |                 2.58 |
| Google AI Mode: own site only (no GitHub) |  1,360 |              4,828 |             100.0% |                 32.19% |                 3.71 |
| Google AI Mode: GitHub only (no own site) |    219 |                417 |             100.0% |                 31.18% |                 3.94 |
| Google AI Mode: third-party only          |  2,132 |              9,593 |             100.0% |                 19.32% |                 4.65 |
| Google AI Mode: uncited brand mention     |  6,652 |             66,642 |             99.99% |                  9.20% |                 6.50 |

Look at what happens on ChatGPT Search: citing a repo **without** citing the brand's own website drops your `#1` win rate to **10.69%** (avg rank `5.54`), trailing own-site citations (`16.53%`) and third-party reviews (`14.16%`). Pairing **GitHub + own site** hits **22.23%** (`3.96` avg position), a **34.5% relative lift** over own-site alone. On Google AI Mode, GitHub + own site reaches **42.05%** (`2.58` avg position), a **30.6% lift** over own-site alone (`32.19%`).

Individual top-cited repositories confirm two distinct winning structures in our Top 25 repo leaderboard. Product-code repositories with comprehensive READMEs drive massive question reach: `arize-ai/phoenix` led all repos across **251** buyer questions (`625` occurrences), followed by `signoz/signoz` (`186` questions), `louislam/uptime-kuma` (`182` questions, `40.32%` `#1` rate when mentioned, boosted by `14.90%` Wiki citations), `openobserve/openobserve` (`176` questions), `grafana/loki` (`160` questions, `47.02%` `#1` rate), and `promptfoo/promptfoo` (`101` questions, `44.17%` `#1` rate). Meanwhile, dedicated public documentation repos on GitHub convert at remarkable `#1` rates via `/blob/` Markdown alone: `langchain-ai/docs` (`141` questions, `99.58%` `/blob/`, `50.34%` `#1` when mentioned), `langfuse/langfuse-docs` (`117` questions, `100%` `/blob/`, `40.70%` `#1`), `clickhouse/clickhouse-docs` (`116` questions, `100%` `/blob/`), `open-telemetry/opentelemetry.io` (`76` questions, `100%` `/blob/`, `60.20%` `#1`), and `backstage/backstage` (`85` questions, `57.34%` `#1`).

## Where developers go in AI answers: GitHub vs registries, Stack Overflow, and Reddit

[GitHub's Octoverse report](https://github.blog/news-insights/octoverse/octoverse-a-new-developer-joins-github-every-second-as-ai-leads-typescript-to-1/) counted over 180 million developers, while [Stack Overflow's 2025 Developer Survey](https://survey.stackoverflow.co/2025/ai) highlighted growing skepticism toward generic AI answers. Inside AI citation pools, that developer shift looks stark: GitHub dominates Q&A forums and package registries alike, while Google AI Mode leans heavily on technical subreddits.

Review how developer ecosystems stack up across September 1 to November 19, 2026 (`Sep-Nov` rows) and in our normalized November 1-19 three-engine comparison.

| Developer ecosystem                     | Sep-Nov total rows | ChatGPT rows | Google AI Mode rows | Perplexity rows (Nov 1-19) | Nov 1-19 answer reach (ChatGPT / Google / Perplexity) |
| --------------------------------------- | -----------------: | -----------: | ------------------: | -------------------------: | ----------------------------------------------------- |
| `reddit.com`                            |             60,264 |        6,968 |              53,270 |                         26 | 0.27% / 9.96% / 1.56%                                 |
| `github.com`                            |             41,065 |       36,019 |               4,999 |                         47 | 4.86% / 0.83% / 2.57%                                 |
| `*.github.io`                           |              8,066 |        7,512 |                 552 |                          2 | 1.40% / 0.09% / 0.18%                                 |
| `docs.github.com`                       |              4,813 |        4,527 |                 284 |                          2 | 0.34% / 0.05% / 0.09%                                 |
| `huggingface.co`                        |              1,781 |        1,528 |                 252 |                          1 | 0.12% / 0.03% / 0.09%                                 |
| Stack Overflow network                  |                576 |          101 |                 475 |                          0 | 0.01% / 0.08% / 0.00%                                 |
| `pypi.org`                              |                215 |          171 |                  40 |                          4 | 0.05% / 0.001% / 0.28%                                |
| `npmjs.com`                             |                200 |          156 |                  44 |                          0 | 0.03% / 0.01% / 0.00%                                 |
| `gist.github.com`                       |                130 |            9 |                 120 |                          1 | -                                                     |
| `hub.docker.com` & other pkg registries |                 65 |           41 |                  24 |                          0 | -                                                     |

`github.com` out-cites the entire Stack Overflow and Stack Exchange network **71.3× overall** (`41,065` vs `576`) and **356.6× on ChatGPT Search** (`36,019` vs `101`). It also beats PyPI, npm, Docker Hub, crates.io, pkg.go.dev, rubygems.org, nuget.org, and packagist.org **combined** (`480` total rows) by **85.6×**. Even `*.github.io` project sites (`8,066` rows) and `huggingface.co` (`1,781` rows) draw far more citations than traditional package pages, matching the third-party distribution we tracked in [AI visibility for developer tools](https://parse.gl/blog/ai-visibility-for-developer-tools).

On Google AI Mode, however, GitHub alone isn't enough. In our [1,390-market engine divergence study](https://parse.gl/research/chatgpt-vs-google-market-and-source-divergence), ChatGPT Search slashed Reddit citations by `98.6%` between July and November, while Google AI Mode cited Reddit in `9.96%` of November answers. Across developer subreddits in September-November, Google AI Mode pulled `r/devops` **1,408 times** (vs `9` on ChatGPT), `r/selfhosted` **730 times** (vs `1`), `r/sysadmin` **512 times** (vs `2`), `r/kubernetes` **481 times** (vs `5`), `r/webdev` **444 times** (vs `2`), and `r/dataengineering` **187 times** (vs `0`). Pair GitHub proof with authentic practitioner participation using our [Reddit AI citations strategy](https://parse.gl/blog/reddit-ai-citations-strategy).

## How to structure READMEs, docs repos, and Issues for AI retrieval

Treating GitHub purely as an engineering host leaves half your AI visibility on the table. Follow these four DevRel moves in sequence so repositories feed ChatGPT Search, Google AI Mode, and Perplexity without starving your primary brand site.

**Step 1 · Move 1**
**Rewrite `README.md` as an answer-ready product brief.** Put the exact category label, supported runtimes, deployment options, quickstart snippet, and a clean comparison or limits table in the opening 250 words. Include explicit absolute links to your owned `/docs` and `/pricing` pages so ChatGPT Search pairs GitHub with your domain (`22.23%` `#1` rate vs `10.69%` alone).
**Step 2 · Move 2**
**Mirror clean Markdown docs in a public repo or `/docs/` folder.** Follow the `langfuse/langfuse-docs` and `clickhouse/clickhouse-docs` pattern by keeping `.md`/`.mdx` guides public with self-contained H2 sections (`120-200` words per concept) and canonical domain links. Never let a GitHub docs mirror trigger cross-domain canonical confusion against your main web docs.
**Step 3 · Move 3**
**Earn placement in active `awesome-*` repos and Hugging Face.** Open clean pull requests in curated `awesome-*` lists (`795` citations across `273` repos) with a factual one-sentence description naming your primary use case. For AI or ML tools, publish model cards, eval scripts, and dataset links on `huggingface.co` (`1,781` citations) pointing back to your repo and website.
**Step 4 · Move 4**
**Close the loop on GitHub Issues, Discussions, and dev subreddits.** Because Google AI Mode pulls `5.54%` of its GitHub links from Issues and Discussions (`36.9×` ChatGPT), unresolved configuration threads resurface in buyer troubleshooting queries. Post clear final resolutions naming the fixed release version and linking the permanent doc URL, then reinforce those answers on `r/devops` or `r/selfhosted` when engineers ask.

Also audit how your owned site handles traffic coming from those README links. Our [docs acquisition architecture guide](https://parse.gl/blog/docs-as-an-ai-acquisition-channel) shows why `/docs/*` subdirectories earn `24.1%` higher citation density per URL than subdomains, and our [pricing-page readability audit](https://parse.gl/blog/why-ai-agents-cannot-read-your-pricing-page) explains why shipping server-rendered pricing keeps AI extractors from hallucinating once a buyer checks cost.

**Do not starve your brand domain to feed GitHub**
Repositories cited without an accompanying citation to your own website win `#1` on ChatGPT Search only `10.69%` of the time, barely half the `22.23%` rate when GitHub and your domain appear together. Every high-traffic `README.md`, release note, and package card on `pypi.org` or `npmjs.com` should link cleanly to canonical web documentation and server-rendered product specs on your main domain.

## Run this workflow with your agent

Before rewriting READMEs across ten repositories, check which GitHub URLs, docs pages, and threads ChatGPT Search and Google AI Mode already cite in your category. Connect Claude, ChatGPT, Codex, or Cursor to [Parse MCP](https://parse.gl/mcp) (`https://agent.parse.gl/mcp`). Index searches, excerpts, and the shared work log are free; fresh checks (`ask_ai_engines`) and live page checks (`fetch_live_pages`) cost **$0.01 each** within your monthly cap, and nothing publishes without approval.

Run this prompt in your assistant:

```text
Connect to Parse MCP and run check_brand and query_metrics for "<our-domain.com>"
over the last 90 days across ChatGPT Search and Google AI Mode. Use search_cited_pages
to list every github.com URL, awesome-* repo, and competitor docs page cited in our
market, and inspect sample answers via search_answers where a repo appears without
our own domain. Call fetch_live_pages on our primary GitHub README and top docs URL
to verify plain-HTML/Markdown clarity, then save our DevRel fix backlog with log_work.
```

That gives your team a concrete backlog linking [content planning](https://parse.gl/use-cases/plan-content) and [high-impact pages to pitch](https://parse.gl/use-cases/find-pages-to-pitch) to measurable movement via `track` and `list_work`, backed by our full [GitHub and docs architecture study](https://parse.gl/research/github-repos-and-docs-architecture-in-ai-search).

## Sources

- [GitHub Repos, Package Registries, and Docs Architecture in AI Search (Parse)](https://parse.gl/research/github-repos-and-docs-architecture-in-ai-search)
- [When does AI cite documentation pages? (Parse)](https://parse.gl/research/do-documentation-pages-get-cited-by-ai)
- [ChatGPT Search vs. Google AI Mode across 1,390 markets (Parse)](https://parse.gl/research/chatgpt-vs-google-market-and-source-divergence)
- [Does ranking #1 in ChatGPT Search get you cited? Inside 5.27M retrieved pages (Parse)](https://parse.gl/research/chatgpt-retrieval-rank-vs-citation-rate)
- [Octoverse: a new developer joins GitHub every second as AI leads TypeScript to #1 (GitHub)](https://github.blog/news-insights/octoverse/octoverse-a-new-developer-joins-github-every-second-as-ai-leads-typescript-to-1/)
- [AI section, 2025 Stack Overflow Developer Survey](https://survey.stackoverflow.co/2025/ai)

## For agents

- 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/blog/devrel-and-github-ai-visibility-playbook 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)
