What is Apify Website Content Crawler?
Apify Website Content Crawler is an Apify Actor for turning a website into reusable text and files. A customer supplies one or more start URLs, and the Actor follows links below that URL path. It is commonly run against documentation, a knowledge base, a blog, or another text-heavy section rather than sent out to discover the public web on its own.
After loading a page, the Actor can remove navigation, headers, cookie notices, and other elements before saving the main content as plain text, Markdown, or HTML. It can also download linked documents when that option is enabled. Results are stored in an Apify dataset for export or use through an API.
Genuine signed traffic presents the token ApifyWebsiteContentCrawler, with Cloudflare recording the full user agent as ApifyWebsiteContentCrawler/1.0 (+https://apify.com/apify/website-content-crawler). Apify registers this agent for Web Bot Auth and publishes verification keys at https://api.apify.com/.well-known/http-message-signatures-directory. Signature validation is stronger evidence than the header alone.
The crawler can use raw HTTP for simpler pages or a headless browser for sites that need JavaScript rendering. Its scope is set by the person running it through start URLs, depth and page limits, and include or exclude patterns. That setup means two visits from this user agent may represent very different jobs, from one small documentation section to a large recursive crawl.
Apify has not published a stable robots.txt commitment for this Actor in the documentation reviewed here, so its behavior is classified as unknown. Cloudflare's directory lists it as not following robots.txt. A robots rule can still state a site owner's preference, but sites that require enforcement should use the verified signature with an edge access policy.
The extracted material is often fed to vector databases, retrieval systems, custom GPTs, or other LLM applications. That can affect answers produced by the customer's application, but it does not add a page to a public AI search index by itself. A request also does not prove that the content will train a model; the Apify customer chooses what happens to the resulting dataset.
