Why runs get blocked
Challenges and unusual-traffic pages, and why we don't try to bypass them.
Search engines sometimes show a challenge page. When that happens the run ends and is logged as blocked_by_target. Blocked runs are free.
A verification check on your own website
If your own website shows a human-verification check (a challenge page) when a run lands on it, the run stops straight away and is logged as a verification check on your site. We never try to get past it. These runs still count towards your daily click allowance, but they don't add to the 3-in-a-row not-found pause. You'll get one notification per website per day while it keeps happening. To fix it, turn the check off or allow-list visits in your site's challenge settings, or switch to Serpfull Bot protection, which recognises our click runs and lets them through while still blocking bad bots.
We don't solve CAPTCHAs, spoof browser fingerprints, fake user agents or rotate proxies. If the block rate for a search term stays high, lower its daily target or spread runs across more hours.
Uppdaterad