MyCentralAIScraperBot
MyCentralAIScraperBot has 52 recorded blocks in October 2026, or 0.8%, and 51 files naming it. Its operator is unclear in the community reference.
Who runs MyCentralAIScraperBot?
| Fact | MyCentralAIScraperBot reference entry |
|---|---|
| Operator | “Unclear at this time.” |
| Purpose | “AI data scraper” |
| Does MyCentralAIScraperBot obey robots.txt? | “Unclear at this time.” |
| Frequency | “Unclear at this time.” |
| Cloudflare managed list for MyCentralAIScraperBot | No |
These facts quote the stored community ai.robots.txt reference.
“Operator and data use is unclear at this time.”
This entry’s stated use is quoted above. Using a page as a search result can send people to it. Training models uses its contents for another purpose, which an owner may refuse.
How many sites block it?
Our readable sample has 52 whole-site blocks, 0.8% of 6,171 files, with Disallow: / as the instruction. Of that full sample, 51 name this crawler, or 0.8%. The count without a whole-site block is 6,119.
From the highest 1,000 ranks, 552 files could be read. Its naming count is 6, or 1.1%, and the block count is 5. Blocking is more common among the leading sites, at 0.9%. Compare 47 blocks among the 5,619 readable files below those ranks, or 0.8%.
| Readable files | Named by | Named share | Blocked by | Blocked share |
|---|---|---|---|---|
| MyCentralAIScraperBot, all ranks | 51 | 0.8% | 52 | 0.8% |
| MyCentralAIScraperBot, top 1,000 | 6 | 1.1% | 5 | 0.9% |
| MyCentralAIScraperBot, remaining ranks | 45 | 0.8% | 47 | 0.8% |
Only whole-site blocks recorded against this crawler’s name count here. Rules addressed to every crawler are outside this count. Of 52 blocks, 7 do not also appear in our count of files naming it. We found 45 files naming it and blocking the whole site, along with 6 files naming it without that ban. Another 6,120 files omit the name. We ignore capitalization and repeated names.
How to block or allow it
Place the group in your root robots.txt file. Per the robots.txt standard, a named group for MyCentralAIScraperBot overrides User-agent: *.
Block the whole site
User-agent: MyCentralAIScraperBot
Disallow: /Allow access
User-agent: MyCentralAIScraperBot
Allow: /It's the 117th most-named crawler of the 171 we counted in the crawler index.
How we counted
For MyCentralAIScraperBot, on 19 October 2026, we requested robots.txt from Tranco’s top 10,000 sites. Each file had 8 seconds to arrive, up to 262,144 bytes. Missing, unreachable and oversized files do not contribute to these shares. Repeat readings are included, using scripts/robots_2026_08_06.py (robots.py at app commit 07104ff). See the full survey method.
Common questions
What does naming this crawler tell me?
This survey includes 6 files with the name and no whole-site ban, out of 51 naming files.
Are leading sites different?
Its name appears in 1.1% of readable leading files and 0.8% overall. Blocking affects 0.9% in the leading group and 0.8% in all ranks.
How does the nearby crawler compare?
The nearby bigsur.ai entry reports 50 files that name it and 52 whole-site blocks, 0.8% of readable files. Here, 51 files mention the name and 52 block access, or 0.8%.