CCBot
Common Crawl · Unconfirmed · robots.txt: Yes
Crawls a sample of the web for Common Crawl's free, openly downloadable archive of web pages.
Block CCBot
User-agent: CCBot
Disallow: /
Common Crawl says CCBot stops crawling your site once robots.txt disallows it. Its pages we checked do not say whether pages already in the archive are removed; it separately runs an opt-out registry.
Allow CCBot
User-agent: CCBot
Allow: /
An allow group only changes anything if a broader rule would block CCBot. Under the robots.txt standard (RFC 9309, section 2.2.1) a crawler follows the group that names it and uses the User-agent: * group only when no group does — so this group lets it in even if your * group says Disallow: /. Token matching is case-insensitive.
Put these lines in /robots.txt at the root of each host (each subdomain has its own file). robots.txt is a request to well-behaved crawlers, not access control.
Already have a robots.txt? Paste it into the robots.txt checker to see whether it blocks CCBot on a given path, and which line decides.
Block or allow it at the server
robots.txt asks; a server rule refuses. Every rule here matches CCBot, spelled as in the User-Agent Common Crawl documents (“CCBot/2.0”), and matches it case-sensitively. The server answers 403.
What a User-Agent rule cannot do: any client can send any User-Agent. Access control by User-Agent is an unreliable technique, since the User-Agent header can be set to anything at all, at the whim of the end user.
(Apache HTTP Server 2.4 documentation). A fake CCBot is refused by the block rule along with the real one, and a crawler that hides its name passes. The “only the real one” rule is the check: it lets the name in only from Common Crawl's published addresses.
Addresses in the “only the real one” rules: Common Crawl's list index.commoncrawl.org/ccbot.json, 5 ranges, fetched 8 Oct 2026, list dated 11 Aug 2026. Operators change their lists; compare the date with the live list before you rely on it.
The IP rules compare the address your server sees. Behind a CDN or load balancer that is the proxy's address, so every claim would be refused: restore the client address first, or put the rule at the CDN.
Syntax from each server's own documentation, fetched 9 Oct 2026: nginx (rewrite module, map module, geo module); Apache (Access Control, <If>, expressions, mod_authz_core, mod_authz_host); Caddy (request matchers, respond); Cloudflare (custom rule example, operators, values and lists, http.user_agent). Every line form above is listed with its quote in server-rules-sources.json.
Who blocks it
Of the 1,000 most-visited domains on Tranco list PY35J (generated 2026-10-08), we read 508 robots.txt files on 2026-10-09 and ran each through the same RFC 9309 matcher as the checker, for the path /. 86 block CCBot from the whole site by name, 30 block it through their User-agent: * group, and 17 name it with partial rules (some paths closed, the home page open). 8 more name it only to let it in.
86
block it by name 16.9%
30
block it through * 5.9%
17
name it, partial rules 3.3%
Percentages are of the 508 files we could read, not of all 1,000 sites.
Highest-ranked sites that block CCBot by name
- amazon.com rank 27
- tiktok.com rank 58
- yahoo.com rank 61
- msn.com rank 72
- vimeo.com rank 85
- chatgpt.com rank 87
- amazonvideo.com rank 111
- snapchat.com rank 134
- gravatar.com rank 154
- tumblr.com rank 156
Each links to the site's live robots.txt, which may have changed since 2026-10-09.
robots.txt is only what a site asks for. A site can also turn a crawler away at its firewall or CDN, or let an operator in under a licensing deal, and neither shows in its robots.txt. A block through * stops every crawler the file does not name, so it says nothing about this one in particular. The files we could not read are not counted: 222 of the 1,000 domains are infrastructure names with no website at the bare domain (CDN and DNS zones, for example), 59 answered our request with 401 or 403, 93 failed (timeout, TLS or server error), 59 have no robots.txt (404 and similar) and 59 answered with an HTML page instead of a robots.txt file. Every agent's count, side by side.
Facts
- Operator
- Common Crawl
- Purpose
- Unconfirmed by the operator
Common Crawl describes its purpose as a free, open copy of the web for research and analysis by anyone. Its pages we checked do not say whether the archive is used to train AI models, so we do not file it under training, search or user fetch.
- Obeys robots.txt
- Yes. Common Crawl says CCBot checks robots.txt before fetching, obeys Crawl-delay, honours link-level nofollow and keeps re-checking robots.txt for changes.
- In your server logs
- The user-agent string contains "CCBot/2.0". Common Crawl warns that other crawlers falsely identify themselves as CCBot.
- How to verify it
- CCBot runs on dedicated IP ranges with reverse DNS in crawl.commoncrawl.org (not yet over IPv6); check with a reverse and forward lookup, or match the IP against the published list.
Published list: index.commoncrawl.org/ccbot.json — 4 IPv4 and 1 IPv6 ranges when we fetched it, list dated 11 Aug 2026. Always match against the live list; operators update them. To count real and fake CCBot requests in your own server log against this list, drop the log into the log reader.
What Common Crawl says
Quoted word for word from the operator's documentation.
“To prevent Common Crawl from crawling your website, include the following in your robots.txt : User-agent: CCBot Disallow: /”
“Common Crawl is a 501(c)(3) non-profit organization dedicated to providing a copy of the Internet to Internet researchers, companies and individuals at no cost for the purpose of research and analysis.”
“Common Crawl's dataset is a sample of the web, and we do not generally archive any entire website but a randomly selected subset of it.”
“CCBot is an automated crawler, checking first the robots.txt , and if crawling a page is allowed, fetches pages using HTTP GET requests.”
“We obey the Crawl-delay parameter for robots.txt .”
“We currently honor the nofollow attribute as it applies to links embedded on your site.”
“Add these lines to your robots.txt file and our crawler will stop crawling your website:”
“We will periodically continue to check if the robots.txt file has been updated.”
“You may also wish to be added to our opt-out registry.”
“Please note that we are aware of crawlers falsely identifying themselves as CCBot. We recommend verifying UserAgent strings to ensure authenticity.”
“CCBot is now run on dedicated IP address ranges with reverse DNS (except over IPv6 where reverse DNS is not yet supported.)”
Sources
- Common Crawl: CCBot — fetched and checked 2026-09-22
- Common Crawl: FAQ — fetched and checked 2026-09-22
- Common Crawl: CCBot IP ranges (ccbot.json) — fetched and checked 2026-09-22