Apify Crawler
CautionUser-agent: ApifyBot
Category: Scrapers
SEO impact if blocked: 2/10
Apify
1 crawler operated by Apify
Who Apify is, for site owners
Apify operates 1 crawler in our directory, filed under Scrapers. Its crawl behaviour is rated caution.
Blocking Apify carries an SEO impact score of 2/10. Blocking impact is rated: Low - No SEO ranking impact.
Our recommendation for Apify: Generally safe to allow; provides legitimate crawling value.
Apify at a glance
| Operator | Apify |
|---|---|
| Crawler in directory | 1 |
| Categories | Scrapers |
| SEO impact if blocked | 2/10 |
| Crawl behaviour | 1 rated caution |
Crawler operated by Apify
What Apify's crawlers are for
Apify runs 1 crawler in our database. Grouped by the job each one does:
- a utility crawler:
ApifyBot
The highest-priority token is Tier 6. That makes Apify a lower-priority operator for most sites: worth a deliberate decision, but rarely the one that decides your visibility.
How site owners treat Apify
How often site owners write rules for Apify's tokens, from our own robots.txt study of the Tranco top 10,000:
| Token | Files naming it | Files blocking it |
|---|---|---|
ApifyBot | 46 (0.8%) | Not measured |
A Apify 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 Apify
A robots.txt file cannot say "Apify"; it can only name Apify's tokens, one group at a time. With a single token, one group is the whole policy.
# One token controls everything Apify fetches through it
User-agent: ApifyBot
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 search visibility check after any change to see the result for each Apify token, including firewall refusals.
Test yourself: does User-agent: Apify block all of Apify's crawlers?
No. robots.txt matches crawler tokens, not company names. Use the token ApifyBot.
Test yourself: if you block one Apify token, are the others blocked too?
No. Each token is read separately. Blocking one leaves the rest following whatever group applies to them.
Each Apify crawler, explained
A one-paragraph brief for every Apify token in our database, covering what it does, how it treats robots.txt and how often large sites write rules for it:
- Apify Crawler (
ApifyBot, Tier 6): a utility crawler that harvests pages for a dataset or data product. Rated caution. 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. 0.8% of top-site robots.txt files name it.
Common mistakes with Apify's crawlers
The errors we see most often with Apify's crawlers in the files and firewalls we test:
- Treating Apify's crawlers as an AI or search crawler. Blocking it has little effect on visibility; decide based on load and what it does with your data.
- Relying on robots.txt alone when Apify's crawlers is rated caution or aggressive. Back the rule with a server-side block.
- Blocking Apify's crawlers by IP alone. Ranges change; match the token and verify with logs.
All three hide inside a file that looks correct, so check Apify's crawlers from outside after every change.
What our own data shows about Apify
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 Apify's marketing. Apify has one token in our database, so the whole picture fits in one place.
ApifyBot in our records
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. ApifyBot is outside our tracked token set, but 46 of 5,583 top-site files already name it, which is enough to show owners treat it as a real crawler.
Among the 39 data scrapers in our database, ApifyBot sits fourth by priority (Tier 6), level with Amazon Kendra, Barkrowler, BLEXBot, Brightbot. 6 of the 39 share its caution rating. Other operators with a crawler that harvests pages for a dataset or data product: FirecrawlAgent (Firecrawl, Tier 2), iaskspider (iAsk, Tier 2), NovaAct (Amazon, Tier 2), CloudflareBrowserRenderingCrawler (Cloudflare, Tier 3), Amazon Kendra (Amazon, Tier 6). A policy for ApifyBot is usually a policy for these too.
A decision record for ApifyBot
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 ApifyBot entry reads:
- Operator and job: Apify; it harvests pages for a dataset or data product.
- Priority and behaviour: Tier 6, rated caution, blocking impact low.
- Suggested starting point: Allow by default; revisit if it costs you bandwidth.
- Enforcement: ApifyBot's operator does not clearly document how it treats robots.txt. Write the ApifyBot rule anyway, then confirm in your logs that its requests stop.
User-agent: ApifyBot
Allow: /Paste the line into the validator with one of your own URLs before it goes live. Revisit the ApifyBot entry sooner than most: a caution rating means Apify traffic deserves a monthly look at your logs.
Checking ApifyBot on your own site
Because Apify runs only ApifyBot in our records, one check covers the whole operator. Search your access logs for the string ApifyBot 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. Apify 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 6 crawler rated caution rarely needs more than a quarterly look, and our log checker does the counting for you.
How top sites treat Apify'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 Apify'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 Apify's crawlers too.
More questions about Apify
- Will blocking Apify affect my Google rankings?
- Only if one of its tokens is a Google search crawler. None of Apify's tokens are Googlebot, so classic Google rankings are unaffected.
- How quickly does a robots.txt change take effect for Apify?
- 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 Apify on some sections and block it on others?
- Yes. Inside the group for
ApifyBot, addDisallowlines for the paths to keep private andAllowlines for exceptions. The longest matching rule wins. - Does blocking Apify delete content it already collected?
- No. robots.txt only controls future visits. For content already collected, check whether Apify offers a removal or opt-out process.
- Is a firewall block better than robots.txt for Apify?
- 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 Apify 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 bot crawlability test to see the outcome from outside, including any firewall layer.
How to block or allow Apify in robots.txt
This rule covers the single crawler Apify operates. Add it to the robots.txt file at the root of your domain.
Block Apify completely
User-agent: ApifyBot
Disallow: /
Allow Apify explicitly
User-agent: ApifyBot
Allow: /
These Apify rules ask; they do not enforce. If a Apify 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 Apify
What crawler does Apify run?
Apify operates 1 crawler in our directory: Apify Crawler (user-agent ApifyBot).
Should I block Apify?
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 Apify in robots.txt?
Add the following to robots.txt at your domain root: User-agent: ApifyBot then Disallow: /.
Does blocking Apify 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 Apify 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.