Data study · The open-source tooling around AI search

80.8% of the GitHub Stars Given to AI Bot Blocklist Projects Went to a Single Community List

KGWritten by Kriszta GrenyoPublished October 20263 min read

We found 470 GitHub projects built to block AI crawlers, from robots.txt lists to firewall rules. They drew 3,560 recorded stars, and one shared list, ai.robots.txt, took 2,875 of them.

Analysis of 470 original AI crawler blocking repositories first seen Jan 2023 to Oct 2026 · GH Archive via BigQuery, October 2026

Key findings

  1. 1

    We counted 470 original GitHub repos built to block or list AI crawlers between January 2023 and October 20, 2026.

  2. 2

    Together they collected 3,560 recorded stars. The ai.robots.txt community list took 2,875 of them (80.8%).

  3. 3

    Only 56 of the 470 repos (11.9%) received any star, and just 41 (8.7%) were updated in three or more separate months.

  4. 4

    New blocking repos keep appearing: 50 in 2023, 89 in 2024, 156 in 2025 and 175 in 2026 so far.

  5. 5

    The leading list drew 124 pull request events in 2025, nearly double the 67 in 2024, and got code pushes in all 12 months of 2025.

  6. 6

    Its share of all GitHub stars peaked in 2025 at 27.9 per million, up from 17.0 per million in 2024.

Summary

Picture a small publisher who checks her server bill and sees traffic doubled, but sales did not. The extra visits came from AI crawlers. She asks a developer friend how to block them, and the friend points her to a list on GitHub that names every known AI bot. That list is where most of the blocking movement lives.

AI companies send crawlers to read websites for training data and live answers. Site owners who want to opt out need an up-to-date list of those crawlers for their robots.txt file or firewall. Developers have published hundreds of such lists and tools on GitHub.

The movement is real but thin. Of 470 repos we found, one shared list collected 80.8% of all stars. Most of the rest are one-off copies that never got a single star.

What we measured

We used GH Archive, the public log of GitHub events, in Google BigQuery. We kept repos whose names pair a blocking word with an AI crawler, bot or scraper word, or that describe AI-focused robots.txt rules. We removed probable forks (repos with no forks and at most two stars that share a name with an earlier forked repo) and repos about chatbots or blockchain that matched by accident. A repo's first recorded event stands in for its creation date.

For each repo we counted stars, forks, code pushes, pull request events, issue events and releases. For the leading list we tracked those counts by quarter. To compare years we divided its stars by all stars GH Archive recorded that year.

One shared list carries the whole movement

80.8%of stars on AI bot blocking repos went to ai.robots.txt

We grouped the 470 repos by the year they first appeared.

AI crawler blocking repos by year first seen
Year first seenReposStarsStars excluding the leading listRepos with 1+ starActive 3+ months
2023502929125
2024893,4575822311
202515664641615
2026 (to Oct 20)1751010510
Total4703,5606855641

Source: aisearchoptimization.net analysis of 470 original AI crawler blocking repositories first seen Jan 2023 to Oct 2026 · GH Archive via BigQuery, October 2026

Every year more people publish their own blocklist, but almost nobody stars or reuses them. The leading list also took 136 of the group's 216 forks (63.0%).

The leading list peaked in 2025

27.9stars per million GitHub stars for ai.robots.txt in 2025, up from 17.0 in 2024

Quarterly activity on the ai.robots.txt repository, as recorded by GH Archive.

ai.robots.txt activity by quarter
StarsCode pushesPull request events
2024 Q1
70
6
3
2024 Q2
381
52
14
2024 Q3
463
115
27
2024 Q4
352
19
23
2025 Q1
792
27
35
2025 Q2
406
55
60
2025 Q3
171
26
10
2025 Q4
140
20
19
2026 Q1
74
5
0
2026 Q2
19
1
1
2026 Q3
5
6
3
2026 Q4 (to Oct 20)
2
0
1

Events

QuarterStarsCode pushesPull request eventsIssue eventsReleases
2024 Q1706310
2024 Q2381521494
2024 Q3463115271413
2024 Q4352192343
2025 Q17922735244
2025 Q240655601810
2025 Q3171261061
2025 Q4140201960
2026 Q1745040
2026 Q2191110
2026 Q356310
2026 Q4 (to Oct 20)20100

Source: aisearchoptimization.net analysis of 470 original AI crawler blocking repositories first seen Jan 2023 to Oct 2026 · GH Archive via BigQuery, October 2026

Stars peaked in early 2025 at 792 in one quarter. Measured against all GitHub stars, the list drew 17.0 per million in 2024, 27.9 in 2025 and 8.7 in 2026. Recorded activity in 2026 is low partly because GH Archive captured fewer events that year, so the decline may be overstated.

Updates come in bursts as new AI bots appear

22months with code pushes to the leading list between 2024 and 2025

Code pushes show how often the list itself changes.

ai.robots.txt yearly maintenance activity
Months with pushesCode pushesPull request events
2024
10
192
67
2025
12
128
124
2026 (to Oct 20)
5
12
5

Count

YearMonths with pushesCode pushesPull request eventsReleases
2024101926720
20251212812415
2026 (to Oct 20)51250

Source: aisearchoptimization.net analysis of 470 original AI crawler blocking repositories first seen Jan 2023 to Oct 2026 · GH Archive via BigQuery, October 2026

The list received pushes in every month of 2025. Pull request events nearly doubled from 2024 to 2025, which may mean more outside contributors were submitting new bot names. Small one-off lists cannot keep pace with that, which may help explain why users gather around one shared source.

What this means

If you decide to block AI crawlers, rely on a maintained list, not a copy you found once and never updated. New AI bots appear several times a year, and a stale robots.txt lets them through. Also know the trade-off. Blocking every AI crawler can keep your business out of AI answers that customers now use to choose a provider. If AI brand visibility matters to you, block the training bots and keep the answer bots.

Many businesses want to block training crawlers but still allow the bots that power AI search answers. That takes a deliberate robots.txt, not a blanket ban. Our free AI visibility audit checks which AI crawlers can reach your site and whether your current rules help or hurt your LLM SEO.

Limits

We matched repo names only. Blocking rules published inside larger projects, or under names without our keywords, are missed. Some name matches may still be unrelated.

GH Archive recorded far fewer star, fork and pull request events in 2026 and had capture gaps in October 2025 and August to October 2026. 2026 counts understate real activity.

Stars measure interest, not how many websites use a list. Many sites copy a list directly without starring it.

Repos are counted by first recorded event, and fork removal is a name-based heuristic.

Embed this research

Add the charts from this study to your page. The embed links back here.

<iframe src="https://aisearchoptimization.net/embed/data-studies/ai-bot-blocklist-github-stars" title="One List Holds 81% of AI Bot Blocklist Stars on GitHub" width="100%" height="720" style="border:0" loading="lazy"></iframe>

Cite this study

APA

Grenyo, K. (2026). One List Holds 81% of AI Bot Blocklist Stars on GitHub. AI Search Optimization. https://aisearchoptimization.net/resources/data-studies/ai-bot-blocklist-github-stars

Plain link

One List Holds 81% of AI Bot Blocklist Stars on GitHub - AI Search Optimization - https://aisearchoptimization.net/resources/data-studies/ai-bot-blocklist-github-stars

Download the data (CSV)

Frequently asked questions

How many GitHub projects block AI crawlers?

We counted 470 original repos from January 2023 to October 20, 2026 whose names describe blocking or listing AI crawlers. New ones rose from 50 in 2023 to 175 in 2026 so far.

Which AI bot blocklist is most popular?

The community list ai.robots.txt holds 2,875 of the 3,560 recorded stars in the group (80.8%) and 136 of its 216 forks.

How often is the leading list updated?

It received code pushes in 10 months of 2024 and all 12 months of 2025. Pull request events rose from 67 in 2024 to 124 in 2025.

Should my business block AI crawlers?

It depends on your goals. Blocking all AI crawlers can keep you out of AI search answers. Many businesses block training crawlers while allowing the bots used for live AI answers.

See where AI search leaves you out

Run the free AI visibility audit. If you want the fixes done for you, the plan is a flat $299/month.