diff --git a/CLAUDE.md b/CLAUDE.md
index bff107b..2b5b1ee 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -36,19 +36,21 @@ Key features:
 
 **Use this when:** Working with sites that already provide feeds but need enhancement (e.g., content modification, filtering, or expanding truncated content).
 
-## WebDriverAbstract - JavaScript/XHR-Heavy Sites
+## WebDriverAbstract - JavaScript/XHR-Heavy Sites (NOT AVAILABLE)
 
 **File:** [Bridge_Docs/04_WebDriverAbstract.md](Bridge_Docs/04_WebDriverAbstract.md)
 
-For websites that heavily rely on JavaScript or XMLHttpRequest (XHR) to load content. Uses Selenium WebDriver with a real browser instance.
+**IMPORTANT: DO NOT USE WebDriverAbstract!**
 
-Important notes:
-- Requires a running Selenium server (Docker image or local ChromeDriver)
-- Very resource-intensive - only use when other methods fail
-- Must explicitly wait for elements to appear after page loads or interactions
-- Always call `$this->cleanUp()` in a finally block
+This server does not have Selenium WebDriver available. WebDriverAbstract cannot be used for bridge creation.
 
-**Use this when:** The target website loads content dynamically via JavaScript and cannot be scraped with standard HTML parsing methods.
+**If a website requires WebDriverAbstract** (i.e., content is loaded entirely via JavaScript and cannot be accessed through other methods), **state that a bridge cannot be created for this website** due to the lack of Selenium support on the server.
+
+Alternative approaches to try before giving up:
+- Check if the website has a hidden API or JSON endpoint that can be accessed directly
+- Look for RSS/Atom feeds that might exist
+- Examine network requests in browser dev tools to find data sources
+- Try XPathAbstract or BridgeAbstract with different parsing strategies
 
 ## XPathAbstract - XPath-Based Bridges