Bot intelligence record
Apify Website Content Crawler
Review firstUse the ApifyWebsiteContentCrawler identifier to separate Apify feed fetching or subscription-style retrieval from normal visitor requests in server logs.
- Operator
- Apify
- Family
- Apify
- Type
- Feed
- Source type
- Verified Directory
- Last checked
- 2026-05-20
User-Agent Pattern
ApifyApifyWebsiteContentCrawler
User-agent strings are identification signals, not proof of identity. Confirm important allow, block, or rate-limit decisions with logs, DNS or IP evidence, request behavior, or operator documentation when available.
Robots.txt Snippet
Click snippet to copyUser-agent: ApifyWebsiteContentCrawler Disallow: /Click the snippet to copy it, or highlight the text manually.
Handling Guidance
DependsUse this record as bot intelligence, then verify the request source and behavior before allowing, blocking, or rate limiting.
Feed fetching, subscription updates, podcast retrieval, or content syndication checks.
Record Details
Structured data- Operator
- Apify
- Family
- Apify
- Type
- Feed
- Purpose
- Feed Fetch
- Identity type
- Verified Bot
- Confidence
- Medium
- Last verified
- 2026-04-19
- Last checked
- 2026-05-20
- Source type
- Verified Directory
- Verification
- Validate the identifying user-agent or signature against the operator documentation before creating hard allow rules.
- Spoofing risk
- User-agent strings can be spoofed. For allow-listing or low-friction rules, pair the published identifier with operator documentation or cryptographic verification when available.
Notes
Apify Website Content Crawler is listed in the Botcrawl directory as a feed retrieval bot from Apify. The primary identifier for log review is ApifyWebsiteContentCrawler.
Identification
- User-agent pattern:
ApifyWebsiteContentCrawler - Family: Apify
- Type: Feed
- Kind: Fetcher
Common use
Feed fetching, subscription updates, podcast retrieval, or content syndication checks.
Verification and handling
Confirm the user-agent against server logs and use published operator documentation, IP ranges, reverse DNS, or other trust signals when available.
Directory guidance marks the risk level as Neutral and the blocking decision as Depends. Do not rely on the user-agent string alone because user-agent strings can be copied or spoofed.
Robots.txt handling: No.
Evidence and Source
- Validate the identifying user-agent or signature against the operator documentation before creating hard allow rules.
- Match `ApifyWebsiteContentCrawler` as a case-insensitive substring in HTTP user-agent logs. Review bot_aliases for alternate names or product labels. Use bot_http_agent for full user-agent examples when the client sends a longer browser-like string. Do not treat a user-agent match alone as proof of identity for allow-listing.
- Feed fetching, subscription updates, podcast retrieval, or content syndication checks.
- User-agent strings can be spoofed. For allow-listing or low-friction rules, pair the published identifier with operator documentation or cryptographic verification when available.
Monitor This Bot In Edge
Botcrawl EdgeUse Botcrawl Edge to see matching traffic, create allow or block rules, and control this bot across connected sites.