diff --git a/browsers/faq.mdx b/browsers/faq.mdx
index 47651e5..6836d97 100644
--- a/browsers/faq.mdx
+++ b/browsers/faq.mdx
@@ -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>