Solution
Rank tracking dies the moment a search engine shows a challenge. Solve it inline so the daily crawl finishes on schedule instead of half empty.
Who this is for
SEO agencies, rank-tracker and SERP-API vendors, and in-house growth teams tracking thousands of keywords across locales. The job is one scheduled fan-out: the same keyword set multiplied by device and country, finished before the client logs in. Whoever owns it is measured on coverage, not on any single query.
The problem
The search engine serves its interstitial exactly when query volume on an IP crosses a threshold, so the challenge lands in the middle of a fan-out rather than at the start. A half-collected SERP set is worse than none, because the rank deltas look real and are not. Solve success has to be even across locales: a good US number hides a broken run in DE.
Works with
[ 04 ]Questions about this one
reCAPTCHA v2 in most locales, with Enterprise on some properties. Both take a sitekey and the page URL, and the token goes back on the form the interstitial itself posts.
No. Proxy and locale are per-task parameters, so one key fans out across every market. Results are returned per task, which is what lets you group success by country afterwards.
Roughly one per blocked branch of the fan-out, not one per keyword. Interstitials appear after a volume threshold on an IP, so the solve count tracks your IP pool more closely than your keyword count.
Partly, and most teams do both. Rotation lowers how often the interstitial appears. It does nothing once the interstitial is already on screen, and that is the part the solve covers.
Create a key, paste it into the sample above, and watch a real token come back. No card, no sales call.
