ChatGLM Spider
CautionUser-agent: ChatGLM-Spider
Category: AI & LLM Bots
SEO impact if blocked: 2/10
Zhipu AI
1 crawler operated by Zhipu AI
https://www.zhipuai.cn/Who Zhipu AI is, for site owners
Zhipu AI operates 1 crawler in our directory, filed under AI & LLM Bots. Its crawl behaviour is rated caution.
Blocking Zhipu AI carries an SEO impact score of 2/10. Blocking impact is rated: Low - No SEO ranking impact.
Our recommendation for Zhipu AI: Generally safe to allow; provides legitimate crawling value.
Zhipu AI at a glance
| Operator | Zhipu AI |
|---|---|
| Crawler in directory | 1 |
| Categories | AI & LLM Bots |
| SEO impact if blocked | 2/10 |
| Crawl behaviour | 1 rated caution |
| Website | www.zhipuai.cn |
Crawler operated by Zhipu AI
What Zhipu AI's crawlers are for
Zhipu AI runs 1 crawler in our database. Grouped by the job each one does:
- a training crawler:
ChatGLM-Spider
The highest-priority token is Tier 2. That puts Zhipu 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 Zhipu AI
How often site owners write rules for Zhipu AI's tokens, from our own robots.txt study of the Tranco top 10,000:
| Token | Files naming it | Files blocking it |
|---|---|---|
ChatGLM-Spider | 109 (2%) | Not measured |
A Zhipu AI token can be blocked without being named, through a User-agent: * group with Disallow: /, so its blocking share can be higher than its naming share.
All counts come from 5,583 valid files fetched October 20, 2026.
Writing one policy for Zhipu AI
A robots.txt file cannot say "Zhipu AI"; it can only name Zhipu AI's tokens, one group at a time. With a single token, one group is the whole policy.
# One token controls everything Zhipu AI fetches through it
User-agent: ChatGLM-Spider
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 AI crawlability test after any change to see the result for each Zhipu AI token, including firewall refusals.
Test yourself: does User-agent: Zhipu AI block all of Zhipu AI's crawlers?
No. robots.txt matches crawler tokens, not company names. Use the token ChatGLM-Spider.
Test yourself: if you block one Zhipu 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 Zhipu AI crawler, explained
A one-paragraph brief for every Zhipu AI token in our database, covering what it does, how it treats robots.txt and how often large sites write rules for it:
- ChatGLM Spider (
ChatGLM-Spider, Tier 2): a training crawler that collects pages to train AI models. Rated caution. ChatGLM Spider's operator does not clearly document how it treats robots.txt. Write the ChatGLM Spider rule anyway, then confirm in your logs that its requests stop. 2% of top-site robots.txt files name it.
Common mistakes with Zhipu AI's crawlers
The errors we see most often with Zhipu AI's crawlers in the files and firewalls we test:
- Assuming that blocking Zhipu 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 Zhipu AI's crawlers with a broad
User-agent: *rule that also catches search engines. NameChatGLM-Spiderin its own group instead. - Expecting a Zhipu 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 Zhipu AI's crawlers from outside after every change.
What our own data shows about Zhipu 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 Zhipu AI's marketing. Zhipu AI has one token in our database, so the whole picture fits in one place.
ChatGLM-Spider in our records
We first recorded ChatGLM-Spider on June 18, 2026. We could not find a page where Zhipu AI names it, so treat the token as reported rather than documented. ChatGLM-Spider is outside our tracked token set, but 109 of 5,583 top-site files already name it, which is enough to show owners treat it as a real crawler.
Among the 104 AI and LLM crawlers in our database, ChatGLM-Spider sits 28th 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 ChatGLM-Spider is usually a policy for these too.
A decision record for ChatGLM-Spider
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 ChatGLM-Spider entry reads:
- Operator and job: Zhipu 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: ChatGLM-Spider's operator does not clearly document how it treats robots.txt. Write the ChatGLM-Spider rule anyway, then confirm in your logs that its requests stop.
User-agent: ChatGLM-Spider
Allow: /Paste the line into the validator with one of your own URLs before it goes live. Revisit the ChatGLM-Spider entry sooner than most: a caution rating means Zhipu AI traffic deserves a monthly look at your logs.
Checking ChatGLM-Spider on your own site
Because Zhipu AI runs only ChatGLM-Spider in our records, one check covers the whole operator. Search your access logs for the string ChatGLM-Spider 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. Zhipu AI publishes no page about the crawler that we could find, so judge it by the requests you actually see rather than by its name. A Tier 2 crawler rated caution is worth confirming every month, and our log checker does the counting for you.
How top sites treat Zhipu 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 Zhipu 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 Zhipu AI's crawlers too.
More questions about Zhipu AI
- Will blocking Zhipu AI affect my Google rankings?
- Only if one of its tokens is a Google search crawler. None of Zhipu AI's tokens are Googlebot, so classic Google rankings are unaffected.
- How quickly does a robots.txt change take effect for Zhipu 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 Zhipu AI on some sections and block it on others?
- Yes. Inside the group for
ChatGLM-Spider, addDisallowlines for the paths to keep private andAllowlines for exceptions. The longest matching rule wins. - Does blocking Zhipu AI delete content it already collected?
- No. robots.txt only controls future visits. For content already collected, check whether Zhipu AI offers a removal or opt-out process.
- Is a firewall block better than robots.txt for Zhipu 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 Zhipu 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 visibility checker to see the outcome from outside, including any firewall layer.
How to block or allow Zhipu AI in robots.txt
This rule covers the single crawler Zhipu AI operates. Add it to the robots.txt file at the root of your domain.
Block Zhipu AI completely
User-agent: ChatGLM-Spider
Disallow: /
Allow Zhipu AI explicitly
User-agent: ChatGLM-Spider
Allow: /
These Zhipu AI rules ask; they do not enforce. If a Zhipu 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 Zhipu AI
What crawler does Zhipu AI run?
Zhipu AI operates 1 crawler in our directory: ChatGLM Spider (user-agent ChatGLM-Spider).
Should I block Zhipu 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 Zhipu AI in robots.txt?
Add the following to robots.txt at your domain root: User-agent: ChatGLM-Spider then Disallow: /.
Does blocking Zhipu 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 Zhipu 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.