Zipchat Shopping Assistant
SafeUser-agent: ZipchatBot
Category: AI & LLM Bots
SEO impact if blocked: 2/10
1 crawler operated by Zipchat
Zipchat operates 1 crawler in our directory, filed under AI & LLM Bots. Its crawl behaviour is rated safe.
Blocking Zipchat carries an SEO impact score of 2/10. Blocking impact is rated: Low - No SEO ranking impact.
Our recommendation for Zipchat: Generally safe to allow; provides legitimate crawling value.
| Operator | Zipchat |
|---|---|
| Crawler in directory | 1 |
| Categories | AI & LLM Bots |
| SEO impact if blocked | 2/10 |
| Crawl behaviour | 1 rated safe |
| Official crawler docs | Zipchat crawler documentation |
Zipchat runs 1 crawler in our database. Grouped by the job each one does:
ZipchatBotThe highest-priority token is Tier 3. That makes Zipchat a lower-priority operator for most sites: worth a deliberate decision, but rarely the one that decides your visibility.
None of Zipchat'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.
A robots.txt file cannot say "Zipchat"; it can only name Zipchat's tokens, one group at a time. With a single token, one group is the whole policy.
# One token controls everything Zipchat fetches through it
User-agent: ZipchatBot
Disallow: /private/
Allow: /
User-agent: *.* group, so copy any Disallow lines you still want it to obey.User-agent: Zipchat block all of Zipchat's crawlers?No. robots.txt matches crawler tokens, not company names. Use the token ZipchatBot.
No. Each token is read separately. Blocking one leaves the rest following whatever group applies to them.
A one-paragraph brief for every Zipchat token in our database, covering what it does, how it treats robots.txt and how often large sites write rules for it:
ZipchatBot, Tier 3): a user-triggered agent that fetches a page when a person asks an assistant or app to open it. Rated safe. Zipchat Shopping Assistant's operator does not clearly document how it treats robots.txt. Write the Zipchat Shopping Assistant rule anyway, then confirm in your logs that its requests stop. Not tracked in our robots.txt study.The errors we see most often with Zipchat's crawlers in the files and firewalls we test:
All three hide inside a file that looks correct, so check Zipchat's crawlers from outside after every change.
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 Zipchat's marketing. Zipchat has one token in our database, so the whole picture fits in one place.
ZipchatBot in our recordsWe first recorded ZipchatBot on October 11, 2026. Zipchat documents it on zipchat.ai, and we recheck that page before each release. No file in our top-10,000 scans names ZipchatBot, 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, ZipchatBot sits 103th by priority (Tier 3), level with AIWebIndex-Agent, alphalens-bot, amazon-QBusiness, Anomura. 81 of the 104 share its safe rating. Other operators with a crawler that fetches a page when a person asks an assistant or app to open it: ChatGPT Agent (OpenAI, Tier 1), ChatGPT Operator (OpenAI, Tier 1), ChatGPT-User (OpenAI, Tier 1), ChatGPT-User/2.0 (OpenAI, Tier 1), Claude-SearchBot (Anthropic, Tier 1). A policy for ZipchatBot is usually a policy for these too.
ZipchatBotTeams 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 ZipchatBot entry reads:
User-agent: ZipchatBot
Allow: /
Paste the line into the validator with one of your own URLs before it goes live. Revisit the ZipchatBot entry once a quarter, or when Zipchat publishes a new token next to it.
ZipchatBot on your own siteBecause Zipchat runs only ZipchatBot in our records, one check covers the whole operator. Search your access logs for the string ZipchatBot 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 Zipchat publishes about the crawler, since that page is the only authority on its behaviour. A Tier 3 crawler rated safe rarely needs more than a quarterly look, and our log checker does the counting for you.
From our robots.txt study of the Tranco top 10,000 (5,583 valid files, fetched October 20, 2026):
None of the tokens for Zipchat'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 Zipchat's crawlers too.
ZipchatBot, add Disallow lines for the paths to keep private and Allow lines for exceptions. The longest matching rule wins.User-agent group per decision and repeat any shared rules inside it.This rule covers the single crawler Zipchat operates. Add it to the robots.txt file at the root of your domain.
These Zipchat rules ask; they do not enforce. If a Zipchat 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.
Text size
Saved on this device only. Drag the round button to move it. Accessibility statement