Ceramic AI TerraCotta
CautionUser-agent: TerraCotta
Category: AI & LLM Bots
SEO impact if blocked: 2/10
Ceramic AI
1 crawler operated by Ceramic AI
https://ceramic.ai/Who Ceramic AI is, for site owners
Ceramic AI operates 1 crawler in our directory, filed under AI & LLM Bots. Its crawl behaviour is rated caution.
Blocking Ceramic AI carries an SEO impact score of 2/10. Blocking impact is rated: Low - No SEO ranking impact.
Our recommendation for Ceramic AI: Generally safe to allow; provides legitimate crawling value.
Ceramic AI at a glance
| Operator | Ceramic AI |
|---|---|
| Crawler in directory | 1 |
| Categories | AI & LLM Bots |
| SEO impact if blocked | 2/10 |
| Crawl behaviour | 1 rated caution |
| Website | ceramic.ai |
| Official crawler docs | Ceramic AI crawler documentation |
Crawler operated by Ceramic AI
What Ceramic AI's crawlers are for
Ceramic AI runs 1 crawler in our database. Grouped by the job each one does:
- a training crawler:
TerraCotta
The highest-priority token is Tier 2. That puts Ceramic AI among the operators whose crawlers have a direct effect on whether AI answers or search results can include your pages.
How site owners treat Ceramic AI
None of Ceramic AI's tokens were among the names tracked in our robots.txt study of the Tranco top 10,000, which usually means few large sites write rules for them yet. Your own logs are the best evidence of how often they visit.
Writing one policy for Ceramic AI
A robots.txt file cannot say "Ceramic AI"; it can only name Ceramic AI's tokens, one group at a time. With a single token, one group is the whole policy.
# One token controls everything Ceramic AI fetches through it
User-agent: TerraCotta
Disallow: /private/
Allow: /- Decide per job, not per company. Training, search and user-triggered fetching have different trade-offs, even from the same operator.
- Name every token you mean. A token you leave out follows
User-agent: *. - Repeat shared rules. A named group ignores the
*group, so copy anyDisallowlines you still want it to obey. - Verify from outside. Run the website crawlability test after any change to see the result for each Ceramic AI token, including firewall refusals.
Test yourself: does User-agent: Ceramic AI block all of Ceramic AI's crawlers?
No. robots.txt matches crawler tokens, not company names. Use the token TerraCotta.
Test yourself: if you block one Ceramic AI token, are the others blocked too?
No. Each token is read separately. Blocking one leaves the rest following whatever group applies to them.
Each Ceramic AI crawler, explained
A one-paragraph brief for every Ceramic AI token in our database, covering what it does, how it treats robots.txt and how often large sites write rules for it:
- Ceramic AI TerraCotta (
TerraCotta, Tier 2): a training crawler that collects pages to train AI models. Rated caution. Ceramic AI TerraCotta's operator does not clearly document how it treats robots.txt. Write the Ceramic AI TerraCotta rule anyway, then confirm in your logs that its requests stop. Not tracked in our robots.txt study.
Common mistakes with Ceramic AI's crawlers
The errors we see most often with Ceramic AI's crawlers in the files and firewalls we test:
- Assuming that blocking Ceramic AI's crawlers removes you from AI answers. It is a training crawler; AI answers are fed by retrieval and user-triggered crawlers with different tokens.
- Blocking Ceramic AI's crawlers with a broad
User-agent: *rule that also catches search engines. NameTerraCottain its own group instead. - Expecting a Ceramic AI's crawlers block to remove content already collected. robots.txt only affects future visits.
All three hide inside a file that looks correct, so check Ceramic AI's crawlers from outside after every change.
What our own data shows about Ceramic AI
Everything below comes from the AI Crawler Check bot database and our two most recent robots.txt scans of the Tranco top 10,000, not from Ceramic AI's marketing. Ceramic AI has one token in our database, so the whole picture fits in one place.
TerraCotta in our records
We first recorded TerraCotta on September 22, 2026. Ceramic AI documents it on ceramic.ai, and we recheck that page before each release. No file in our top-10,000 scans names TerraCotta, so any rule you write for it puts you ahead of almost every large site.
Among the 104 AI and LLM crawlers in our database, TerraCotta sits 83th by priority (Tier 2), level with AddSearchBot, AI2Bot, AI2Bot-DeepResearchEval, aiHitBot. 22 of the 104 share its caution rating. Other operators with a crawler that collects pages to train AI models: ClaudeBot (Anthropic, Tier 1), Google-Extended (Google, Tier 1), GPTBot (OpenAI, Tier 1), Meta-ExternalAgent (Meta, Tier 1), AI2Bot (Allen Institute for AI, Tier 2). A policy for TerraCotta is usually a policy for these too.
A decision record for TerraCotta
Teams that review crawlers once a quarter keep one short entry per token, so anyone can see why a rule exists and when it was last checked. Filled in from our data, the TerraCotta entry reads:
- Operator and job: Ceramic AI; it collects pages to train AI models.
- Priority and behaviour: Tier 2, rated caution, blocking impact low.
- Suggested starting point: Your licensing call: Disallow to refuse training, Allow to permit it.
- Enforcement: TerraCotta's operator does not clearly document how it treats robots.txt. Write the TerraCotta rule anyway, then confirm in your logs that its requests stop.
User-agent: TerraCotta
Allow: /Paste the line into the validator with one of your own URLs before it goes live. Revisit the TerraCotta entry sooner than most: a caution rating means Ceramic AI traffic deserves a monthly look at your logs.
Checking TerraCotta on your own site
Because Ceramic AI runs only TerraCotta in our records, one check covers the whole operator. Search your access logs for the string TerraCotta over the last 30 days, note how many requests it made and which paths it asked for, then compare that with what your robots.txt allows. Match the requests against what Ceramic AI publishes about the crawler, since that page is the only authority on its behaviour. A Tier 2 crawler rated caution is worth confirming every month, and our log checker does the counting for you.
How top sites treat Ceramic AI's crawlers
From our robots.txt study of the Tranco top 10,000 (5,583 valid files, fetched October 20, 2026):
None of the tokens for Ceramic AI's crawlers is tracked by name in our study. For scale, 20.1% of top-site files block at least one AI training crawler and 4.3% refuse every unnamed crawler with User-agent: * and Disallow: /, which would catch Ceramic AI's crawlers too.
More questions about Ceramic AI
- Will blocking Ceramic AI affect my Google rankings?
- Only if one of its tokens is a Google search crawler. None of Ceramic AI's tokens are Googlebot, so classic Google rankings are unaffected.
- How quickly does a robots.txt change take effect for Ceramic AI?
- Crawlers cache robots.txt, commonly for up to a day. Expect a change to apply within about 24 hours, and confirm it in your logs.
- Can I allow Ceramic AI on some sections and block it on others?
- Yes. Inside the group for
TerraCotta, addDisallowlines for the paths to keep private andAllowlines for exceptions. The longest matching rule wins. - Does blocking Ceramic AI delete content it already collected?
- No. robots.txt only controls future visits. For content already collected, check whether Ceramic AI offers a removal or opt-out process.
- Is a firewall block better than robots.txt for Ceramic AI?
- A firewall enforces the decision, while robots.txt asks politely. Many operators recommend robots.txt because blocking their IPs can stop them reading your rules at all. Use robots.txt first, and add a firewall rule only if requests continue.
A five-minute Ceramic AI review
- Confirm the token. Compare the user-agent in your logs with the tokens listed on this page. A close spelling is not the same crawler.
- Decide the outcome per crawler. Use the briefs above to choose allow, limit or block for each token.
- Write the group. Add or edit one
User-agentgroup per decision and repeat any shared rules inside it. - Publish and wait. Allow about a day for crawlers to fetch the new file.
- Confirm the result. Check your logs, then run the AI crawlability test to see the outcome from outside, including any firewall layer.
How to block or allow Ceramic AI in robots.txt
This rule covers the single crawler Ceramic AI operates. Add it to the robots.txt file at the root of your domain.
Block Ceramic AI completely
User-agent: TerraCotta
Disallow: /
Allow Ceramic AI explicitly
User-agent: TerraCotta
Allow: /
These Ceramic AI rules ask; they do not enforce. If a Ceramic AI token ignores them, block it at the server or CDN. Paths are case-sensitive, and each rule matches the token, not the full user-agent string.
Frequently asked questions about Ceramic AI
What crawler does Ceramic AI run?
Ceramic AI operates 1 crawler in our directory: Ceramic AI TerraCotta (user-agent TerraCotta).
Should I block Ceramic AI?
Generally safe to allow; provides legitimate crawling value. The SEO impact score for blocking is 2/10, where 10 means blocking costs you the most visibility.
How do I block Ceramic AI in robots.txt?
Add the following to robots.txt at your domain root: User-agent: TerraCotta then Disallow: /.
Does blocking Ceramic AI hurt my search rankings?
Blocking impact is rated: Low - No SEO ranking impact. Google's own ranking crawler is Googlebot, which this operator does not run, so blocking Ceramic AI does not by itself remove you from Google's index. What it can change is whether AI assistants and analytics tools can read your pages.