Parallel

Common mistakes with Parallel's crawlers

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

1. Assuming a robots.txt rule will stop Parallel'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 Parallel'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 Parallel'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 Parallel's crawlers from outside after every change.

Spotting Parallel in your logs

robots.txt says what Parallel Fetcher and Parallel Web Crawler may do; your access logs show what they 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 "Shap-User|ShapBot" /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 "Shap-User|ShapBot" /var/log/nginx/access.log \
  | awk '{print $7}' | sort | uniq -c | sort -rn | head -20

Check the requests are genuine

Anyone can send these user-agents, so confirm the source before acting on a match:

• Shap-User: we hold no published IP list, so use reverse DNS where Parallel documents a hostname and treat an unverifiable Parallel Fetcher request with caution. Check it separately from Parallel Web Crawler.
• ShapBot: we hold no published IP list, so use reverse DNS where Parallel documents a hostname and treat an unverifiable Parallel Web Crawler request with caution. Check it separately from Parallel Fetcher.

What our own data shows about Parallel

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 Parallel's marketing. It covers 2 Parallel tokens in turn.

Shap-User in our records

We first recorded Shap-User on September 22, 2026. We could not find a page where Parallel names it, so treat the token as reported rather than documented. Shap-User is outside our tracked token set, but 55 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, Shap-User sits 100th 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 Shap-User is usually a policy for these too.

A decision record for Shap-User

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 Shap-User entry reads:

• Operator and job: Parallel; 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: Shap-User's operator does not clearly document how it treats robots.txt. Write the Shap-User rule anyway, then confirm in your logs that its requests stop.

User-agent: Shap-User
Allow: /

Paste the line into the validator with one of your own URLs before it goes live. Revisit the Shap-User entry once a quarter, or when Parallel publishes a new token next to it.

ShapBot in our records

We first recorded ShapBot on September 22, 2026. Parallel documents it on docs.parallel.ai, and we recheck that page before each release. No file in our top-10,000 scans names ShapBot, 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, ShapBot sits 101th by priority (Tier 3), level with AIWebIndex-Agent, alphalens-bot, amazon-QBusiness, Anomura. 22 of the 104 share its caution rating. Other operators with a crawler that builds a search or answer index: AddSearchBot (AddSearch, Tier 2), AIWebIndex (Lyrenth, Tier 2), atlassian-bot (Atlassian, Tier 2), AzureAI-SearchBot (Microsoft, Tier 2), Cloudflare-AI-Search (Cloudflare, Tier 2). A policy for ShapBot is usually a policy for these too.

A decision record for ShapBot

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

• Operator and job: Parallel; it builds a search or answer index.
• Priority and behaviour: Tier 3, rated caution, blocking impact low.
• Suggested starting point: Allow by default; revisit if it costs you bandwidth.
• Enforcement: ShapBot's operator does not clearly document how it treats robots.txt. Write the ShapBot rule anyway, then confirm in your logs that its requests stop.

User-agent: ShapBot
Allow: /

Paste the line into the validator with one of your own URLs before it goes live. Revisit the ShapBot entry sooner than most: a caution rating means Parallel traffic deserves a monthly look at your logs.

How top sites treat Parallel'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 Parallel'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 Parallel's crawlers too.

More questions about Parallel

Will blocking Parallel affect my Google rankings?

Only if one of its tokens is a Google search crawler. None of Parallel's tokens are Googlebot, so classic Google rankings are unaffected.

How quickly does a robots.txt change take effect for Parallel?

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 Parallel on some sections and block it on others?

Yes. Inside the group for Shap-User, add Disallow lines for the paths to keep private and Allow lines for exceptions. The longest matching rule wins.

Does blocking Parallel delete content it already collected?

No. robots.txt only controls future visits. For content already collected, check whether Parallel offers a removal or opt-out process.

Is a firewall block better than robots.txt for Parallel?

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.