Scrapy

Generic scraping framework often used to build AI training datasets; obeys robots.txt only when ROBOTSTXT_OBEY is on.

Scrapy is operated by Zyte (open-source framework) and classified here as model training. These agents collect text and images that may end up in a training corpus. Disallowing one withholds new content from the next model. It does not withdraw anything collected before the disallow, and it does not remove the site from any answer engine.

Disallowing scrapy withholds content crawled from that point on from Zyte (open-source framework)'s training data. It does not withdraw pages collected in earlier crawls, it does not reach copies already sitting in third-party datasets, and it does not remove the site from any answer surface.

robots.txt token

scrapy

Operator

Zyte (open-source framework)

Purpose

Model training

Honors robots.txt

yes

Documentation

https://scrapy.org/

Scrapy/2.17.0 (+https://scrapy.org)

curl -A 'Scrapy/2.17.0 (+https://scrapy.org)' https://example.com/

Replace the host with your own. A 403, a challenge page or an empty body means the edge is blocking the agent whatever robots.txt says.

Zyte (open-source framework) runs no other agent in this registry.

Does blocking Scrapy remove me from datasets built with Scrapy?

No, not by itself. Scrapy collects content for training, not for the index that answers questions. Zyte (open-source framework) operates no separate answer crawler in this registry, so there is no answer surface to lose here. Content collected before the disallow is not withdrawn.

How do I verify Scrapy requests are genuine?

Scrapy is an open-source framework, not a service. Anyone can run it and set any user-agent string, so traffic identifying as Scrapy cannot be attributed to a particular operator at all. Treat it as unattributed automated traffic and rate-limit by address.

See whether your robots.txt admits Scrapy today, and whether your edge agrees with it.