Channel3Bot
Channel3Bot is listed as a search crawler, and its operator is unclear in the community reference. In October 2026, 55 sites block it, a 0.9% share of readable files.
Who runs Channel3Bot?
| Fact | Channel3Bot reference entry |
|---|---|
| Operator | “Unclear at this time.” |
| Purpose | “AI Search Crawlers” |
| Does Channel3Bot obey robots.txt? | “Unclear at this time.” |
| Frequency | “Unclear at this time.” |
| Cloudflare managed list for Channel3Bot | No |
These facts quote the stored community ai.robots.txt reference.
The listed use here is search. Reading a page to answer a user has a different purpose from building a model with it. Owners may allow the requested visit.
How many sites block it?
Within 6,171 readable robots.txt files, the name appears in 57, or 0.9%. Instructions blocking every path, Disallow: /, appear in 55, a 0.9% share. No whole-site ban is recorded for 6,116 files.
For the top 1,000 ranks, its name appears in 18 files out of 552, or 3.3%. Whole-site blocks total 18. Blocking is more common among the leading sites, at 3.3%. Lower in the ranking, blocking reaches 37 files out of 5,619, a 0.7% share.
| Readable files | Named by | Named share | Blocked by | Blocked share |
|---|---|---|---|---|
| Channel3Bot, all ranks | 57 | 0.9% | 55 | 0.9% |
| Channel3Bot, top 1,000 | 18 | 3.3% | 18 | 3.3% |
| Channel3Bot, remaining ranks | 39 | 0.7% | 37 | 0.7% |
For this entry, we counted whole-site bans attached to its own name, leaving general rules for all crawlers out of the total. Of 55 blocks, 1 does not also appear in our count of files naming it. Looking just at named files gives 54 blocks and 3 without a whole-site block. For 6,114 readable files, we found no mention by name. We ignore capitalization and repeated names.
How to block or allow it
These lines go in robots.txt at the root. User-agent: * yields to a group naming Channel3Bot under the robots.txt standard.
Block the whole site
User-agent: Channel3Bot
Disallow: /Allow access
User-agent: Channel3Bot
Allow: /It's the 110th most-named crawler of the 171 we counted in the crawler index.
How we counted
For Channel3Bot, on 19 October 2026, we requested robots.txt from Tranco’s top 10,000 sites. An 8-second wait or a file over 262,144 bytes ended a read. Shares exclude unreachable, unavailable and oversized files. Collection and repeat readings used scripts/robots_2026_08_06.py (robots.py at app commit 07104ff). See the full survey method.
Common questions
Does a User-agent line mean it is blocked?
A name identifies the crawler addressed by a group. The survey found 3 files with that name and no recorded whole-site ban, out of 57.
What do the top-ranked sites show?
Leading files record 3.3% with the name and 3.3% blocking it. Across all readable files, the corresponding shares are 0.9% and 0.9%.
Which nearby entry can I compare?
The nearby GoogleOther-Image entry reports 57 files that name it and 177 whole-site blocks, 2.9% of readable files. Here, 57 files mention the name and 55 block access, or 0.9%.