Skip to content

Add measured site difficulty index to FAQ #358

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

Open
ulziibay-kernel wants to merge 4 commits into
base: main
Choose a base branch
from
+49 −5
Open

Add measured site difficulty index to FAQ #358

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
2758526
Add tiered site difficulty index to FAQ
ulziibay-kernel May 11, 2026
6c3d853
Replace tier guesses with measured block rates
ulziibay-kernel May 11, 2026
d1565a9
Simplify difficulty index: drop per-site block-rate numbers
ulziibay-kernel May 11, 2026
c55e4a6
Drop methodology section from difficulty index
ulziibay-kernel May 11, 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
54 changes: 49 additions & 5 deletions browsers/faq.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,13 +19,57 @@ 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
## Site difficulty index

There are some websites that are not supported by Kernel browsers due to their restrictions around automation and associated bot detection. These include:
A rough grouping of sites by how much friction we see when running stealth Kernel browsers against the public landing page. This list is incomplete and will grow over time.

- LinkedIn
### Hard — significant friction observed

Most or all sessions were blocked or challenged.

- Yelp
- Glassdoor
- Indeed
- TripAdvisor

### Light — partial friction observed

Some sessions were blocked or challenged.

- Yellow Pages
- Zillow

### Clear — no blocks observed at this layer

All sessions returned a usable page. These sites still deploy bot detection — login flows, deep navigation, and high-volume scraping behave very differently — but the public landing page renders cleanly.

- Airbnb
- Amazon
- Booking.com
- Cars.com
- Crunchbase
- eBay
- Etsy
- Facebook
- Facebook Marketplace
- GitHub
- Google Maps
- Google Search
- IMDb
- Instagram
- X (Twitter)
- Amazon
- LinkedIn
- Medium
- Pinterest
- Reddit
- Shopify storefronts (Gymshark)
- Target
- TikTok
- Walmart
- Wikipedia
- X (Twitter)
- Yahoo Finance
- YouTube

<Info>
Hitting friction on a site that's listed under Clear? Check your [proxy type](/browsers/bot-detection/overview#choosing-a-proxy-type) and confirm you're not running headless — those are the two most common causes of unexpected detection.
</Info>
Loading