Zipchat

1 crawler operated by Zipchat

Who Zipchat is, for site owners

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.

Zipchat at a glance

OperatorZipchat
Crawler in directory1
CategoriesAI & LLM Bots
SEO impact if blocked2/10
Crawl behaviour1 rated safe
Official crawler docsZipchat crawler documentation

Crawler operated by Zipchat

What Zipchat's crawlers are for

Zipchat runs 1 crawler in our database. Grouped by the job each one does:

  • a user-triggered agent: ZipchatBot

The 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.

How site owners treat Zipchat

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.

Writing one policy for Zipchat

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: /
  1. Decide per job, not per company. Training, search and user-triggered fetching have different trade-offs, even from the same operator.
  2. Name every token you mean. A token you leave out follows User-agent: *.
  3. Repeat shared rules. A named group ignores the * group, so copy any Disallow lines you still want it to obey.
  4. Verify from outside. Run the AI crawler checker after any change to see the result for each Zipchat token, including firewall refusals.
Test yourself: does User-agent: Zipchat block all of Zipchat's crawlers?

No. robots.txt matches crawler tokens, not company names. Use the token ZipchatBot.

Test yourself: if you block one Zipchat token, are the others blocked too?

No. Each token is read separately. Blocking one leaves the rest following whatever group applies to them.

Each Zipchat crawler, explained

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:

  • Zipchat Shopping Assistant (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.

Common mistakes with Zipchat's crawlers

The errors we see most often with Zipchat's crawlers in the files and firewalls we test:

  1. Assuming a robots.txt rule will stop Zipchat's crawlers. User-triggered fetches act for a person, and some operators say robots.txt may not apply to them. Check the operator's statement above.
  2. Blocking Zipchat's crawlers as if it were a bulk crawler. It fetches one page because a person asked; blocking it means that person's assistant cannot read your page.
  3. Counting Zipchat's crawlers visits as crawl volume. Each request maps to a real user question, which makes the paths it requests a useful signal of what people ask about you.

All three hide inside a file that looks correct, so check Zipchat's crawlers from outside after every change.

What our own data shows about Zipchat

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 records

We 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.

A decision record for ZipchatBot

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 ZipchatBot entry reads:

  • Operator and job: Zipchat; it fetches a page when a person asks an assistant or app to open it.
  • Priority and behaviour: Tier 3, rated safe, blocking impact low.
  • Suggested starting point: Allow by default; revisit if it costs you bandwidth.
  • Enforcement: ZipchatBot's operator does not clearly document how it treats robots.txt. Write the ZipchatBot rule anyway, then confirm in your logs that its requests stop.
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.

Checking ZipchatBot on your own site

Because 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.

How top sites treat Zipchat'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 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.

More questions about Zipchat

Will blocking Zipchat affect my Google rankings?
Only if one of its tokens is a Google search crawler. None of Zipchat's tokens are Googlebot, so classic Google rankings are unaffected.
How quickly does a robots.txt change take effect for Zipchat?
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 Zipchat on some sections and block it on others?
Yes. Inside the group for ZipchatBot, add Disallow lines for the paths to keep private and Allow lines for exceptions. The longest matching rule wins.
Does blocking Zipchat delete content it already collected?
No. robots.txt only controls future visits. For content already collected, check whether Zipchat offers a removal or opt-out process.
Is a firewall block better than robots.txt for Zipchat?
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 Zipchat review

  1. 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.
  2. Decide the outcome per crawler. Use the briefs above to choose allow, limit or block for each token.
  3. Write the group. Add or edit one User-agent group per decision and repeat any shared rules inside it.
  4. Publish and wait. Allow about a day for crawlers to fetch the new file.
  5. 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 Zipchat in robots.txt

This rule covers the single crawler Zipchat operates. Add it to the robots.txt file at the root of your domain.

Block Zipchat completely
User-agent: ZipchatBot Disallow: /
Allow Zipchat explicitly
User-agent: ZipchatBot Allow: /

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.

Frequently asked questions about Zipchat

What crawler does Zipchat run?
Zipchat operates 1 crawler in our directory: Zipchat Shopping Assistant (user-agent ZipchatBot).
Should I block Zipchat?
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 Zipchat in robots.txt?
Add the following to robots.txt at your domain root: User-agent: ZipchatBot then Disallow: /.
Does blocking Zipchat 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 Zipchat 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.
WhatsApp us