proxies + delays only fix half of it — google's serp blocking leans on behavioral + tls fingerprint, not just ip. if you're getting captcha'd AND temp-banned even on fresh residential, the request fingerprint is probably the flag: header order, tls/ja3, missing the little browser-y things a real chrome sends. things that move the needle more than decoy traffic: match a real browser's header order exactly, slow the per-ip rate hard (serp tolerates way fewer rps than people think — single digits per minute per ip), and when a captcha fires hand it to a solver instead of burning the ip. segmented batches help mostly because they lower per-ip rate as a side effect — that's the real lever, not the batching. and mixing dc decoy traffic with residential usually hurts, the dc ips drag your trust score down.