From 84cb44293f7c33f78e2a9a7652e1f07686da9815 Mon Sep 17 00:00:00 2001 From: masnwilliams <43387599+masnwilliams@users.noreply.github.com> Date: Wed, 22 Jul 2026 06:18:13 +0000 Subject: [PATCH 1/3] Reframe FAQ unsupported-sites list as bot-detection guidance The flat "Unsupported Websites" list overstated reality: Kernel browsers navigate these sites fine. Friction shows up on login flows, high-volume scraping, and aggressive-vendor sites, not on page loads. Replace the list with guidance on where resistance actually occurs and which mitigations to use. Co-Authored-By: Claude Opus 4.8 --- browsers/faq.mdx | 19 +++++++++++-------- 1 file changed, 11 insertions(+), 8 deletions(-) diff --git a/browsers/faq.mdx b/browsers/faq.mdx index 47651e57..2ee19d3c 100644 --- a/browsers/faq.mdx +++ b/browsers/faq.mdx @@ -19,13 +19,16 @@ 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 +## Sites with heavier bot detection -There are some websites that are not supported by Kernel browsers due to their restrictions around automation and associated bot detection. These include: +Kernel browsers can navigate to most websites, including popular ones with a reputation for aggressive automation defenses (LinkedIn, Facebook, Instagram, X, Amazon, Reddit, and similar). Loading a page and interacting with it is not the same problem as staying undetected through a login flow or at scale — which is where friction actually shows up. -- LinkedIn -- Facebook -- Instagram -- X (Twitter) -- Amazon -- Reddit +Where you're most likely to hit resistance: + +- **Login and account-creation flows** — repeated logins, especially from new IPs, are a common trigger for challenges and account locks. Use [Managed Auth](/auth/overview) to keep sessions persistently logged in rather than re-authenticating each run. +- **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). +- **Sites running aggressive 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. + + + Before automating a target site, test it manually first — see the [bot detection guide](/browsers/bot-detection/overview) for the recommended approach and mitigations. + From b6fcf9d7575b72e4cc182468b9ae6c05e382462f Mon Sep 17 00:00:00 2001 From: masnwilliams <43387599+masnwilliams@users.noreply.github.com> Date: Wed, 22 Jul 2026 06:20:23 +0000 Subject: [PATCH 2/3] Present Managed Auth as the answer for logged-in workflows Drop login/account-creation from the "where you'll hit resistance" list so it doesn't frame login as a limitation. Managed Auth handles that, so point to it positively instead. Co-Authored-By: Claude Opus 4.8 --- browsers/faq.mdx | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/browsers/faq.mdx b/browsers/faq.mdx index 2ee19d3c..2f989934 100644 --- a/browsers/faq.mdx +++ b/browsers/faq.mdx @@ -21,14 +21,15 @@ If you're experiencing slower-than-expected browser creation times, review your ## Sites with heavier bot detection -Kernel browsers can navigate to most websites, including popular ones with a reputation for aggressive automation defenses (LinkedIn, Facebook, Instagram, X, Amazon, Reddit, and similar). Loading a page and interacting with it is not the same problem as staying undetected through a login flow or at scale — which is where friction actually shows up. +Kernel browsers can navigate to most websites, including popular ones with a reputation for aggressive automation defenses (LinkedIn, Facebook, Instagram, X, Amazon, Reddit, and similar). Loading and interacting with a page is a different problem from staying undetected at scale — which is where friction tends to show up. Where you're most likely to hit resistance: -- **Login and account-creation flows** — repeated logins, especially from new IPs, are a common trigger for challenges and account locks. Use [Managed Auth](/auth/overview) to keep sessions persistently logged in rather than re-authenticating each run. - **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). - **Sites running aggressive 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. + Before automating a target site, test it manually first — see the [bot detection guide](/browsers/bot-detection/overview) for the recommended approach and mitigations. From ba58603dc174c923a91762a4e31de854680f3861 Mon Sep 17 00:00:00 2001 From: masnwilliams <43387599+masnwilliams@users.noreply.github.com> Date: Wed, 22 Jul 2026 06:22:50 +0000 Subject: [PATCH 3/3] Reframe as education, drop supported/unsupported claims Remove any claim about whether specific sites can or cannot be automated, and stop naming individual sites. Explain that detection is site- and configuration-specific and what drives it. Co-Authored-By: Claude Opus 4.8 --- browsers/faq.mdx | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/browsers/faq.mdx b/browsers/faq.mdx index 2f989934..fd0ac4df 100644 --- a/browsers/faq.mdx +++ b/browsers/faq.mdx @@ -19,17 +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. -## Sites with heavier bot detection +## Bot detection varies by site -Kernel browsers can navigate to most websites, including popular ones with a reputation for aggressive automation defenses (LinkedIn, Facebook, Instagram, X, Amazon, Reddit, and similar). Loading and interacting with a page is a different problem from staying undetected at scale — which is where friction tends to show up. +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. -Where you're most likely to hit resistance: +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). -- **Sites running aggressive 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. +- **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. - Before automating a target site, test it manually first — see the [bot detection guide](/browsers/bot-detection/overview) for the recommended approach and mitigations. + 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.