When sites fight back
Some sites block automation on purpose. The escalation order for getting through, why the first check is the network and not the browser, and the tiers that aren't worth it for a solo builder.
Most sites let a normal browser through. A few are built to keep automation out, with services like Cloudflare, DataDome, or Akamai watching for anything that doesn't look human. When you hit one, the instinct is to reach for a heavier browser. Usually that's the wrong first move.
Check the network before you blame the browser
The most common wasted effort in scraping is fixing the browser when the block was never about the browser. Many blocks happen at the network layer: the fingerprint of the connection itself, how your client negotiates TLS and HTTP, doesn't match a real browser, and you get a 403 before the page logic ever runs. The recurring community lesson is to check this first. A plain request with a browser-matched network fingerprint sometimes gets through where a full browser is blocked, and it's far cheaper to try. If a hosted fetch or a normal browser gets a 403, suspect the network layer before reaching for a fancier browser.
Then: a real logged-in browser, done right
If it really is the browser, the next rung is the one from Part 2: a real, warmed-up, logged-in browser on a home connection. A genuine session is the hardest thing for these systems to flag, because it isn't faking anything, and it handles most moderately-defended sites. That's not a compromise. It's the strongest ordinary tool you have.
Only then: stealth tooling
For the hard tier, aggressive bot-detection that blocks even a normal automated browser, there's purpose-built stealth tooling. Two things to know before going there.
First, there's no single winner. It's a benchmark culture, where the right tool depends on the specific site, and the community keeps a running comparison across tools and targets. Test against your actual target instead of trusting a name.
Second, the names change every few months. As of late 2026, the ones that hold up are Camoufox, Patchright, and SeleniumBase's stealth mode, while the once-standard undetected-chromedriver is fading, blocked by the big detectors more often now. Treat any specific tool as current, not permanent, and re-check before you build on it.
Reach for this tier only after a normal browser has actually been blocked, and after you've ruled out the network layer. It's heavier and higher-maintenance than everything else in this series.
The tiers that aren't worth it for a solo builder
Three categories look like upgrades and usually aren't, if you're one person reusing your own real sessions.
Managed browser clouds. They run hundreds of browsers in their cloud so you don't own servers, which is genuinely useful for scale. But their datacenter connections and generic fingerprints are often worse for logged-in scraping than your own real, warmed-up browser. You'd trade away the exact thing that gets you through.
Multi-identity antidetect browsers. Built to run many separate fake identities at once, for agencies and multi-account operations. If you run one identity per site, the problem they solve doesn't exist for you, and the community's own read is that connection quality matters far more than which of these you pay for.
Fully agent-driven browser libraries. Tools where an agent decides every click on every run. They're well-known names, but they draw real "worked once, fell apart on repeat" reports. The pattern that holds up is the one from Part 3: let an agent discover the flow once, compile it to a script, and fall back to the agent only when the site changes.
The series in one line
Start with the lightest tool that gets the data. Move up a rung only when the current one is actually blocked, and when you do, check the network before the browser. Most of the time you never leave the bottom of the ladder.
The skill that encodes all of this, the decision guide and the connect-and-drive patterns, is free to download from the series landing page. Take it, wire in your own setup, and start at the bottom.
Sources
- The escalation order, the network-first diagnosis, and the read on which tools hold up come from the r/webscraping and r/antidetectbrowser communities, as of late 2026.