Caution Official docs AI & LLM Bots

Kimi Crawler

Operated by Moonshot AI

Quick Facts

User-Agent:
KimiBot
Category:
AI & LLM Bots
Operator:
Moonshot AI
Safety:
Use Caution
Blocking Impact:
Low - No SEO ranking impact
SEO Impact Score:
2/10
Official docs:
www.kimi.ai

Confirmed by the operator

Moonshot AI names KimiBot on its own documentation page, linked above. The token, purpose and robots.txt behaviour on this profile come from that page, re-checked on October 19, 2026.

What is Kimi Crawler?

Kimi Crawler is an AI data-collection crawler operated by Moonshot AI. It gathers public web content to build or refine training datasets for large language models. Like other AI training crawlers, Kimi Crawler does not influence your search-engine rankings, so you can block it via robots.txt without any SEO penalty if you wish to opt out of AI training.

Kimi Crawler is an AI data-collection crawler operated by Moonshot AI. It gathers public web content to build or refine training datasets for large language models. Like other AI training crawlers, Kimi Crawler does not influence your search-engine rankings, so you can block it via robots.txt without any SEO penalty if you wish to opt out of AI training.
Kimi Crawler uses the user-agent token KimiBot. You can control it via robots.txt, meta tags (noai), or the emerging llms.txt standard. Robots.txt is voluntary; for hard enforcement, combine it with server-level IP blocking.

What happens if you block Kimi Crawler?

✅ No SEO Impact - Blocking Kimi Crawler does not affect your rankings in Google, Bing, or any other search engine. Kimi Crawler is an AI crawler, not a traditional search indexer. You can freely block it via User-agent / Disallow: / without any SEO penalty.
Generally safe to allow; provides legitimate crawling value.

Want to see whether Kimi Crawler actually visits you? Read how do I monitor AI bot traffic to my website?

How to block Kimi Crawler with robots.txt

<code>User-agent: KimiBot</code> - Matching is case-insensitive. Robots.txt is fetched from the root of each subdomain separately.

Block completely (robots.txt)
User-agent: KimiBot Disallow: /
Allow all (robots.txt)
User-agent: KimiBot Allow: /
Block private only (robots.txt)
User-agent: KimiBot Disallow: /private/ Disallow: /api/ Disallow: /admin/ Allow: /
Nginx server block
# Nginx: Hard-block Kimi Crawler if ($http_user_agent ~* "KimiBot") { return 403 "Bot blocked"; }
Apache .htaccess
# Apache: Hard-block Kimi Crawler SetEnvIfNoCase User-Agent "KimiBot" bad_bot Order Allow,Deny Allow from all Deny from env=bad_bot
Meta robots tag
<meta name="robots" content="noindex, nofollow">
X-Robots-Tag header
X-Robots-Tag: noindex, nofollow

Is Kimi Crawler safe to allow?

Kimi Crawler is generally legitimate but warrants caution. It is operated by Moonshot AI. Review its crawl behaviour in your logs and apply robots.txt or rate-limiting if its activity is heavier than you expect.
Verify by reverse-DNS lookup: legitimate Kimi Crawler requests resolve to Moonshot AI's domain.

What does Kimi Crawler do?

Understanding Kimi Crawler's purpose helps you decide whether to allow or block it.

  • Collects public web content to train large language models
  • Builds and refreshes AI training datasets
  • Harvests text, code, and structured data for model improvement
  • Does NOT affect search-engine rankings
  • Can be blocked to opt out of AI training without SEO loss

Kimi Crawler in context

Kimi Crawler is a training crawler operated by Moonshot AI. In plain terms, it collects pages to train AI models. Our database files it under AI and LLM crawlers and ranks it Tier 2, important crawlers from established AI and search operators. 74 of the 104 AI and LLM crawlers in our database share this tier.

Its safety rating is caution and its blocking impact is low. So the decision about Kimi Crawler rests on what you want from Moonshot AI, not on its behaviour. How we rate safety and impact.

How site owners treat Kimi Crawler

Our robots.txt study of the Tranco top 10,000 did not track KimiBot as a named token, so we do not publish an adoption figure for it. If you run a large site, your own logs are the best evidence of how often it visits.

Does it follow robots.txt?

Kimi Crawler's operator does not clearly document how it treats robots.txt. Write the Kimi Crawler rule anyway, then confirm in your logs that its requests stop.

Moonshot AI crawlers and close alternatives

Kimi Crawler is one of 3 Moonshot AI crawlers in our database. A User-agent: KimiBot group controls Kimi Crawler only; the other Moonshot AI tokens below need their own lines.

  • KimiBot: this crawler (Tier 2)
  • Kimi-SearchBot: Kimi Search, builds a search or answer index (Tier 2)
  • Kimi-User: Kimi (Moonshot AI), fetches a page when a person asks an assistant or app to open it (Tier 2)

To give Kimi Crawler the same answer as its siblings, stack User-agent: KimiBot with their lines above one set of rules; to treat Kimi Crawler differently, give it its own group.

Other AI and LLM crawlers that do the same job (collects pages to train AI models) include ClaudeBot from Anthropic, Google-Extended from Google, GPTBot from OpenAI, Meta-ExternalAgent from Meta, AI2Bot from Allen Institute for AI, aiHitBot from aiHit. Deciding about Kimi Crawler is usually a decision about the whole group, so check how your file treats these too.

We first recorded KimiBot on September 22, 2026. Moonshot AI documents it on kimi.ai, and we recheck that page before each release.

Which rule Kimi Crawler actually follows

Kimi Crawler reads exactly one group in robots.txt, the most specific one that names KimiBot, and never combines rules across groups. This short file shows the trap:

User-agent: *
Disallow: /private/

User-agent: KimiBot
Disallow: /drafts/
  1. Find the group. Kimi Crawler looks for a group naming KimiBot. One exists, so it ignores User-agent: * completely.
  2. Apply only that group. It is refused /drafts/ and nothing else.
  3. The surprise. /private/ is open to Kimi Crawler, because that rule lives in the * group it no longer reads. To keep it out of both, repeat Disallow: /private/ inside its own group.
Test yourself: does a rule under User-agent: * apply to Kimi Crawler if the file also has a User-agent: KimiBot group?

No. Once a group names it, Kimi Crawler reads only that group. Put every rule you want it to follow inside its own group.

Test yourself: will blocking Kimi Crawler remove your pages from AI answers?

No. Kimi Crawler collects training data. Blocking it changes what future models learn, not which pages AI answers cite today.

Test yourself: is User-agent: kimibot the same as User-agent: KimiBot?

Yes. RFC 9309 makes user-agent matching case-insensitive. Paths are a different story: Disallow: /Blog/ does not block /blog/.

Should you allow Kimi Crawler? Decide by situation

Recommended setting for Kimi Crawler by type of site
If you are...Recommended setting
You publish content and want AI answers to cite itYour call. Kimi Crawler is a training crawler, so blocking it does not remove you from AI answers; retrieval crawlers do that job.
You license content and want to stop AI trainingBlock it by name with User-agent: KimiBot and Disallow: /.
You run an online shopAllow it unless your logs show it is costly.
Your server is under load from botsRate-limit before blocking. It is rated caution in our database.

Check Kimi Crawler on your own site

  1. Open /robots.txt on your domain and search for KimiBot. If it is not named, it follows User-agent: *.
  2. List the Disallow lines in the group Kimi Crawler follows and test your key URLs against them; the longest match wins, and Allow wins a tie.
  3. Look beyond the file. A firewall or bot manager can refuse Kimi Crawler even when robots.txt allows it, and that never shows in the file.
  4. Run our AI search crawlability check to see how Kimi Crawler and every other crawler we track are treated in one pass, including firewall refusals.

Common mistakes with Kimi Crawler

The errors we see most often with Kimi Crawler in the files and firewalls we test:

  1. Assuming that blocking Kimi Crawler removes you from AI answers. It is a training crawler; AI answers are fed by retrieval and user-triggered crawlers with different tokens.
  2. Blocking Kimi Crawler with a broad User-agent: * rule that also catches search engines. Name KimiBot in its own group instead.
  3. Expecting a Kimi Crawler block to remove content already collected. robots.txt only affects future visits.

All three hide inside a file that looks correct, so check Kimi Crawler from outside after every change.

Spotting Kimi Crawler in your logs

robots.txt says what Kimi Crawler may do; your access logs show what it actually did.

Count requests

On a server with standard Nginx or Apache logs, this counts matching requests per day (adjust the log path for your host):

grep -iE "KimiBot" /var/log/nginx/access.log \
  | awk '{print $4}' | cut -d: -f1 | sort | uniq -c

And this shows which paths it requested most, which is the quickest way to see whether your Disallow lines are being respected:

grep -iE "KimiBot" /var/log/nginx/access.log \
  | awk '{print $7}' | sort | uniq -c | sort -rn | head -20

Check the requests are genuine

Anyone can send the Kimi Crawler user-agent, so confirm the source before acting on a match:

  • KimiBot: we hold no published IP list, so use reverse DNS where the operator documents a hostname and treat an unverifiable Kimi Crawler request with caution.

Frequently Asked Questions

What is the official user-agent string for Kimi Crawler?
The official user-agent string for Kimi Crawler is: KimiBot. Use this exact string in robots.txt, Nginx, Apache, or Cloudflare firewall rules to target this bot. Matching in robots.txt is case-insensitive. Verify a request genuinely comes from Kimi Crawler by performing a reverse-DNS lookup on the source IP.
Is Kimi Crawler safe?
Kimi Crawler is generally legitimate but warrants caution. It is operated by Moonshot AI. Review its crawl behaviour in your logs and apply robots.txt or rate-limiting if its activity is heavier than you expect.
Will blocking Kimi Crawler hurt my SEO?
✅ No SEO Impact - Blocking Kimi Crawler does not affect your rankings in Google, Bing, or any other search engine. Kimi Crawler is an AI crawler, not a traditional search indexer. You can freely block it via User-agent / Disallow: / without any SEO penalty.
How do I block Kimi Crawler in robots.txt?
Add the following lines to your /robots.txt file:
User-agent: KimiBot
Disallow: /

This instructs Kimi Crawler not to crawl any path on your site. To block only specific sections, replace / with the path (e.g., Disallow: /blog/).
Does Kimi Crawler respect robots.txt?
Kimi Crawler is operated by Moonshot AI and is expected to fetch and parse /robots.txt before crawling, following RFC 9309. For hard enforcement, combine robots.txt with server-level IP or user-agent blocking.
How do I verify if Kimi Crawler is crawling my site?
Search your web server access logs for the string KimiBot (case-insensitive: grep -i "KimiBot" /var/log/nginx/access.log). Filter by user-agent in your log analytics tool (GoAccess, AWStats, etc.).

Related Bots

WhatsApp us