For teams testing extraction and AI pipelines
Build a test set of real pages, each with its text and a picture
Crawl a site you have the right to use into a fixed set of real pages, each with its Markdown and a screenshot to check labels against.
The problem
An extraction prompt works on the five pages it was written against and fails on the sixth. Testing it properly takes a few hundred real pages, kept fixed so results compare from run to run, with a picture of each so a person can check what the right answer was.
How domscout handles it
A crawl from a seed URL, limited to the origins you allow, returns each page's Markdown and a screenshot from one durable job, and always obeys robots.txt. Store the results as your fixed set, label the right answer for each page with the screenshot beside it, and run every prompt, model or rule change against the same pages. Use sites you own or have permission to use this way.
Where it shows up
- A regression set for an extraction prompt or schema.
- A labelled sample for comparing models on your own content.
- Fixed fixtures for a scraper's test suite.
The request
POST /crawl. Crawl starts at Business. A crawl stops at 500 pages and depth 5, needs an explicit HTTPS origin allowlist, and always obeys robots.txt. Each page costs what the same capture costs on its own, 1 credit here.
Go further
More in Data extraction and search: Crawling a whole site · Structured data from web pages · AI extraction to a JSON Schema · Semantic search over your content · Content behind clicks · Company research from websites · All use cases
Give your product a browser.
Get clean web content and visual proof into your workflow in minutes.