Worker 2.0: Enhanced Browser Authenticity

Worker 2.0 is live. Same campaigns, same credits. The browser layer underneath is what changed.
This is a product note, not a ranking essay. If you want the leak background, read what NavBoost actually stores. Here is what shipped.
TL;DR
Worker 2.0 is the authenticity layer that plays a NavBoosted session plan. It has to pass Sannysoft and BrowserLeaks in CI, runs 80-plus real device profiles, and curves mouse and scroll instead of drawing straight lines. The public browser test is the same idea, in your tab. We do not claim zero detections.
Browser authenticity
Sessions now pass the two public checks we run in CI:
- Sannysoft automation detection
- BrowserLeaks fingerprint consistency
We score WebGL renderer, canvas output, and navigator properties on every profile. A pass on those two sites is not a promise that Google will count the session. Google's filter is proprietary. The leak named squashed and unsquashed click objects (Content Warehouse commit). Interpreting that pair as "our test equals Google's bot filter" is not supported.
The point of the test is to catch the cheap tells (headless Chrome, navigator.webdriver, SwiftShader GPUs) before you spend credits. How a bot detection test works is the longer guide.
80-plus browser profiles
The library is real device configs, not a single stealth UA:
- 50 desktop: Windows Chrome, Mac Chrome, Edge, Linux, with GPU strings and screen sizes that match the claimed OS
- 30-plus mobile: iPhone Safari and Android Chrome with device metrics that agree with the user agent
Each profile is checked so user agent, platform, renderer, and hardware claims do not contradict each other. Reusing one fingerprint across "users" is how cheap tools get ignored. We do not do that.
Behavior on the page
Mouse paths are curved (bezier), not straight lines. Scroll has momentum and pauses. Timing jitters. Scroll cadence follows the page instead of a metronome.
That mix is the session plan you configure in the wizard (satisfy / compare / soft miss, dwell, horizon). Worker 2.0 is the layer that plays the plan without looking like a scripted dump of identical clicks.
Admin monitor and the public test
The Worker Monitor (admin) shows success rate, timing, queue depth, on-demand authenticity checks, session logs, and threshold alerts.
Public-facing: the free Browser Test reports how the current browser looks to a fingerprinting script. Use it on your own machine, or as a sanity check when you are evaluating a CTR tool. PixelScan and CreepJS are useful second opinions.
Implementation notes
Built on rebrowser-puppeteer to cut the usual automation flags. Evasion covers 15-plus detection vectors: WebGL GPU strings, canvas and AudioContext normalization, and platform-appropriate config per profile.
What we are not claiming
We are not claiming zero detections, GSC-verified clicks, or traffic that Google cannot tell from a random organic visitor. Worker 2.0 raises the authenticity bar on our side. Google still ignores garbage.
Rollout
Already on for every campaign. No toggle, no migration. Credits still never expire.
| Package | Credits | Price | |---------|---------|-------| | Trial | 150 | free to start | | Starter | 400 | $49 | | Pro | 2,000 | $149 | | Agency | 8,000 | $399 |
FAQ
What is NavBoosted Worker 2.0?
Worker 2.0 is the traffic-worker update that plays a session plan in a real browser profile. Same campaigns, same credits. The authenticity layer changed: public-test CI gates, 80-plus device configs, curved mouse, and jittered timing.
Which bot detection tests does Worker 2.0 pass?
Sessions are checked against Sannysoft automation detection and BrowserLeaks fingerprint consistency in CI. We also score WebGL, canvas, and navigator on every profile. A pass is not a promise that Google will count the session.
Do I need to migrate existing campaigns?
No. Worker 2.0 is already on for every campaign. No toggle. Credits still never expire. Packages stay Trial 150, Starter 400 for $49, Pro 2,000 for $149, Agency 8,000 for $399.
Where can I test a browser myself?
Use the free NavBoosted browser test, or run Sannysoft, BrowserLeaks, PixelScan, or CreepJS. The public test is a sanity check, not Google's filter.
Questions: contact. How the planner works if you want the mix. Start a 150-credit trial if you already have a query.

Emily Highsmith
SEO Research & Content
SEO researcher and content strategist specializing in search engine ranking factors, user engagement signals, and technical SEO. Passionate about demystifying how search algorithms work.
Continue Reading
Bot Detection Test: What SEO Campaigns Need to Check
A bot detection test is how you find out whether a CTR browser looks automated before you spend credits. Google can ignore junk traffic. Sannysoft, BrowserLeaks, PixelScan, and our 47-signal check are the public bar. Not Akamai's Bot Manager.
How to Increase CTR in SEO
Improve organic CTR by beating the click rate that is normal for your current position. Titles, snippets, schema, and session quality. Not hope. Advanced Web Ranking publishes the position curve. Your GSC file is the one that matters.