200 OK · 2 KB · Looks like success
- Status
- 200 OK
- Size
- 2 KB (data pages are ~48 KB)
- Body
- no results container; a script and a "checking your browser" message
- Cookies
- a short-lived cookie is set
- Timing
- answered in 40 ms, faster than real pages
What it really is. A verification step from the site's bot detection, not data. Bot-detection products judge the whole session (browser behaviour, cookies, request order, timing) and can answer with status 200.
Options, and what each one costs
- Slow down and keep sessions longer-livedOften stops the checks from firing at all, and it is the most durable fix. Costs throughput, so a large job takes longer.
- Use a real browser where the site expects oneReliable when the site truly needs a browser, but slow and heavy to run at scale, and more to keep working as the site changes. Appropriate only within what the site permits.
- Ask for an official API, export or data agreementThe most reliable and lowest-maintenance route when it exists; depends on the site offering one and on commercial terms.
- If the checks persist, stop and reportNot a workaround, a decision: better to hand back a clear gap than invented data. Always appropriate.