WebDriver detection is a technique websites use to identify browsers being controlled by automation tools like Selenium or Puppeteer. It checks for specific properties and behaviors that only appear in automated browser sessions.
Automation frameworks that control a browser through the WebDriver protocol leave behind detectable traces, such as the navigator.webdriver property being set to true. Detection scripts check for this property, along with other automation-specific signals like missing browser plugins, unusual window sizes, or inconsistent JavaScript execution timing. When these checks find enough matching signals, the site treats the visitor as a bot and may block access, show a CAPTCHA, or silently serve different content. Many detection scripts run multiple WebDriver-related checks together to reduce false positives from legitimate browsers.
Treat it as a signal about how the target defends itself, not a one-time obstacle.
USER-country-de-session-task01Pairing a stable session label with a real residential exit is one of the simplest ways to reduce how often webdriver detection gets triggered in the first place. Rotate "task01" only when a deliberately fresh identity is needed.
Most modern defenses combine several signals into a score, rather than checking for one single thing.
Residential and mobile exits reduce how often this defense triggers in the first place, which is cheaper than solving it after.
Human-like pacing reduces detections tied to this concept more reliably than any single technical fix.
Anti-bot vendors update rules often -- retest this whenever a job’s success rate drops without a code change.
A ticket resale site blocks a checkout attempt after detecting the navigator.webdriver flag set to true, a telltale sign of an automated browser.
WebDriver detection is one of the most common first-line defenses against browser automation, so scrapers that skip masking this property get blocked quickly and easily. Understanding this check helps explain why many scraping setups patch or override WebDriver-related properties before running any automated session.
It is a boolean flag in the JavaScript environment of the browser that automation tools using the WebDriver protocol set to true, making it one of the simplest ways for a website to detect an automated session.
Yes, several scraping frameworks include patches or stealth plugins that override the navigator.webdriver property and other automation traces, though sites keep adding new detection methods in response.
Ready to put this into practice? Read the Docs
Start a free trial and test with real targets -- no credit card, no sales call.