Skip to content

Reframe FAQ 'Unsupported Websites' as bot-detection education #459

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
masnwilliams merged 3 commits into from
Jul 22, 2026
Merged

Reframe FAQ 'Unsupported Websites' as bot-detection education #459

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
84cb442
Reframe FAQ unsupported-sites list as bot-detection guidance
masnwilliams Jul 22, 2026
b6fcf9d
Present Managed Auth as the answer for logged-in workflows
masnwilliams Jul 22, 2026
ba58603
Reframe as education, drop supported/unsupported claims
masnwilliams Jul 22, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 12 additions & 8 deletions browsers/faq.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,13 +19,17 @@ If you're experiencing slower-than-expected browser creation times, review your
- Browsers persist independently of CDP. Depending on your timeout configuration, it will continue running even if the CDP connection closes. You can reconnect to the same `cdp_ws_url` if you're unexpectedly disconnected.
- We recommend implementing reconnect logic, as network interruptions or lifecycle events can cause CDP sessions to close. Detect disconnects and automatically re-establish a CDP connection when this occurs.

## Unsupported Websites
## Bot detection varies by site

There are some websites that are not supported by Kernel browsers due to their restrictions around automation and associated bot detection. These include:
Websites differ widely in how aggressively they detect and challenge automation, and the same site can behave differently depending on how you approach it. Rather than a fixed list of "supported" and "unsupported" sites, it's more useful to understand what drives that friction and how to reduce it.

- LinkedIn
- Facebook
- Instagram
- X (Twitter)
- Amazon
- Reddit
What tends to increase bot-detection friction:

- **High-volume or high-concurrency scraping** — many requests from the same exit IP raise the block rate. Spread load across [proxies](/proxies/overview) and reuse [Profiles](/auth/profiles).
- **Aggressive detection vendors** (Cloudflare, DataDome, PerimeterX, Imperva, Akamai) — these can challenge even anonymous page loads. Enable [stealth mode](/browsers/bot-detection/stealth) and consider [computer controls](/browsers/computer-controls) for more human-like interaction.

For workflows behind a login, [Managed Auth](/auth/overview) handles the login flow and keeps sessions persistently authenticated across runs.

<Info>
Because behavior is site- and configuration-specific, test your target site manually before automating — see the [bot detection guide](/browsers/bot-detection/overview) for the recommended approach and mitigations.
</Info>
Loading