Caution Reported Scrapers

Apify Crawler

Operated by Apify

Quick Facts

User-Agent:
ApifyBot
Category:
Scrapers
Operator:
Apify
Safety:
Use Caution
Blocking Impact:
Low - No SEO ranking impact
SEO Impact Score:
2/10
Official docs:
None published by Apify

Reported, not operator documented

Apify has not published a crawler page that names ApifyBot. It is listed here on our own evidence. Verified by AI Crawler Check: 46 of the 5,583 valid robots.txt files in the Tranco top 10,000 carry a rule for ApifyBot, so site owners treat it as a real crawler name (how we measure this). That proves the spelling is in use, not who sends it. Token used by crawlers run on the Apify platform by its customers.

What that means for you: the ApifyBot rule on this page is the best available spelling, but Apify has made no statement of purpose, crawl rate or robots.txt compliance. Treat a ApifyBot request in your logs as a clue, not proof of who sent it, and add a firewall rule if that traffic matters to you. If the operator publishes documentation, this profile moves to Official docs.

What is Apify Crawler?

Apify Crawler is a developer-facing extraction agent operated by Apify. It fetches and structures web content on behalf of applications and AI agents built on Apify's platform. Traffic volume depends on how third-party developers configure it, so monitor your logs if you see heavy activity.

Apify Crawler is a developer-facing extraction agent operated by Apify. It fetches and structures web content on behalf of applications and AI agents built on Apify's platform. Traffic volume depends on how third-party developers configure it, so monitor your logs if you see heavy activity.
Apify Crawler uses the user-agent token ApifyBot. 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 Apify Crawler?

✅ No SEO Impact - Blocking Apify Crawler does not affect your rankings in Google, Bing, or any other search engine. Apify 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.

How to block Apify Crawler with robots.txt

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

Block completely (robots.txt)
User-agent: ApifyBot Disallow: /
Allow all (robots.txt)
User-agent: ApifyBot Allow: /
Block private only (robots.txt)
User-agent: ApifyBot Disallow: /private/ Disallow: /api/ Disallow: /admin/ Allow: /
Nginx server block
# Nginx: Hard-block Apify Crawler if ($http_user_agent ~* "ApifyBot") { return 403 "Bot blocked"; }
Apache .htaccess
# Apache: Hard-block Apify Crawler SetEnvIfNoCase User-Agent "ApifyBot" 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 Apify Crawler safe to allow?

Apify Crawler is rated Caution in this directory. It is a Reported token: Apify has not published documentation for it, so its purpose, crawl rate and robots.txt behaviour are not confirmed by the operator, and anyone can send the same user-agent string. Allow or block it on its stated purpose, and back the robots.txt rule with a firewall rule if the traffic matters to you.
Apify publishes no IP ranges or reverse-DNS pattern for Apify Crawler, so the user-agent string cannot be verified. Rate-limit unusual volume instead of trusting the name.

What does Apify Crawler do?

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

  • Extracts and structures web content for developer applications
  • Powers AI agents built on the operator platform
  • Volume depends on third-party developer configuration
  • Monitor logs if you notice heavy activity
  • Can be rate-limited via robots.txt or server rules

Apify Crawler in context

Apify Crawler is a utility crawler operated by Apify. In plain terms, it harvests pages for a dataset or data product. Our database files it under data scrapers and ranks it Tier 6, the lowest priority: scrapers and tools that offer most sites little or nothing. 37 of the 39 data scrapers in our database share this tier.

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

How site owners treat Apify Crawler

In our own scan of the Tranco top 10,000 (5,583 valid robots.txt files), 46 files (0.8%) name ApifyBot in a User-agent line. That shows site owners treat the token as a real crawler worth a rule. It does not, on its own, prove who operates it.

Does it follow robots.txt?

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

Apify crawlers and close alternatives

Apify runs only this one crawler in our database, so a single User-agent: ApifyBot group controls everything Apify fetches through it.

Other data scrapers that do the same job (harvests pages for a dataset or data product) include Amazon Kendra from Amazon, Barkrowler from Babbar, BLEXBot from WebMeUp, coccocbot-web from Unknown, Crawl4AI from Unknown, crawler4j from Unknown. Deciding about Apify Crawler is usually a decision about the whole group, so check how your file treats these too.

We first recorded ApifyBot on September 22, 2026. We could not find a page where Apify names it, so treat the token as reported rather than documented.

Which rule Apify Crawler actually follows

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

User-agent: *
Disallow: /private/

User-agent: ApifyBot
Disallow: /drafts/
  1. Find the group. Apify Crawler looks for a group naming ApifyBot. 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 Apify 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 Apify Crawler if the file also has a User-agent: ApifyBot group?

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

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

Often, yes. Apify Crawler is a utility crawler, so pages it cannot fetch can drop out of the answers or results it supports.

Related: how AI engines choose their sources

Test yourself: is User-agent: apifybot the same as User-agent: ApifyBot?

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

Should you allow Apify Crawler? Decide by situation

Recommended setting for Apify Crawler by type of site
If you are...Recommended setting
You publish content and want AI answers to cite itLow stakes either way. It does not decide whether AI answers cite you.
You license content and want to stop AI trainingBlocking it does not stop training, because Apify Crawler is a utility crawler. Block the operator's training crawler instead.
You run an online shopConsider blocking it, especially on price and stock pages that competitors scrape.
Your server is under load from botsRate-limit before blocking. It is rated caution in our database.

Check Apify Crawler on your own site

  1. Open /robots.txt on your domain and search for ApifyBot. If it is not named, it follows User-agent: *.
  2. List the Disallow lines in the group Apify 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 Apify Crawler even when robots.txt allows it, and that never shows in the file.
  4. Run our AI search visibility check to see how Apify Crawler and every other crawler we track are treated in one pass, including firewall refusals.

Common mistakes with Apify Crawler

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

  1. Treating Apify Crawler as an AI or search crawler. Blocking it has little effect on visibility; decide based on load and what it does with your data.
  2. Relying on robots.txt alone when Apify Crawler is rated caution or aggressive. Back the rule with a server-side block.
  3. Blocking Apify Crawler by IP alone. Ranges change; match the token and verify with logs.

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

Spotting Apify Crawler in your logs

robots.txt says what Apify 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 "ApifyBot" /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 "ApifyBot" /var/log/nginx/access.log \
  | awk '{print $7}' | sort | uniq -c | sort -rn | head -20

Check the requests are genuine

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

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

Frequently Asked Questions

What user-agent string does Apify Crawler use?
Apify Crawler is reported to identify itself with ApifyBot. Evidence that the spelling is in real use comes from our own robots.txt study: 46 of the 5,583 valid robots.txt files in the Tranco top 10,000 name it (fetched October 20, 2026), not from Apify, which has not published crawler documentation naming it. Use it in robots.txt as the best available match, and treat a request carrying it as a clue rather than proof of who sent it.
Is Apify Crawler safe?
Apify Crawler is rated Caution in this directory. It is a Reported token: Apify has not published documentation for it, so its purpose, crawl rate and robots.txt behaviour are not confirmed by the operator, and anyone can send the same user-agent string. Allow or block it on its stated purpose, and back the robots.txt rule with a firewall rule if the traffic matters to you.
Will blocking Apify Crawler hurt my SEO?
✅ No SEO Impact - Blocking Apify Crawler does not affect your rankings in Google, Bing, or any other search engine. Apify 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 Apify Crawler in robots.txt?
Add the following lines to your /robots.txt file:
User-agent: ApifyBot
Disallow: /

This instructs Apify Crawler not to crawl any path on your site. To block only specific sections, replace / with the path (e.g., Disallow: /blog/).
Does Apify Crawler respect robots.txt?
Not documented. Apify has published no statement that Apify Crawler reads robots.txt. A rule for ApifyBot will stop a client that chooses to honour it; for enforcement, add a firewall or CDN rule as well.
How do I verify if Apify Crawler is crawling my site?
Search your access logs for ApifyBot (for example grep -i "ApifyBot" /var/log/nginx/access.log). Because the operator publishes no IP ranges or reverse-DNS pattern, a match shows that something used the name, not that Apify sent it.
WhatsApp us