
Bot Management stops bots. Not your customers.
Customers and partners pass, scrapers and credential stuffing don’t.
- Invisible to most users
- Allow, monitor or block
- Stops scraping and ATO

Bot Management. What it is and what it does.
Bot Management is part of the Link11 WAAP platform. Three challenge levels separate customers, partners and search engines from scrapers, credential stuffing and purchase bots — in front of login, catalog and checkout, usually without a human noticing.
Bots look like customers. Your protection should know the difference.
- 24/7 SupportSecurity threats don’t wait for business hours, and neither do we. Our specialists are available around the clock to help you when needed.
- GDPR-compliantLink11’s European location ensures your content remains compliant with strict GDPR regulations and EU data protection laws.
- Fully managed serviceOur fully managed solution, maintained by security experts around the clock, ensures your protection is always up to date, 24/7, 365 days a year.
The bot looks like your best customer. Blunt defenses do more harm than good.
Three situations where a captcha or a country block is the wrong answer.
Environment, client and behavior are verified without interrupting the user.
Decisions are made per category and application: monitor, allow or block.
Verification sits in front of login, catalog and checkout, in the same pass as WAF and DDoS protection.
Where bots strike first. And where they now bounce off.
The iGaming platform Ventures Lab sees brute-force login attempts and scraper bots every few hours.
Link11 blocks them, and the team sees what is happening in real time.
Case study: Ventures LabAt a UK online shop, sudden high volumes of bot traffic slowed the site.
Tuned with the Link11 team, bot detection blocked the bots with minimal false positives: better performance, fewer customers dropping off.
In an app there is no browser to verify — and emulators imitate every device.
The Mobile SDK signs every request and authenticates the device, for iOS and Android.



Who is human and who is not. In one view.
Which share of traffic was challenged, which share passed and which category triggered what.
Mostly invisible to customers. End of the line for bots.
Before you connect. The technical details.
- Onboarding: DNS change, reverse proxy
- Challenge levels: Passive, active, interactive
- Actions: Monitor, allow, block
- Mobile apps: SDK for iOS and Android
- Passive
- The page is delivered with a verification script; environment data is evaluated without the user noticing. Most accurate, least disruptive.
- Active
- A script has to verify the client before the response is sent. The default level.
- Interactive
- The user solves a visible task. The most disruptive level — and therefore the last.
- Repetition
- No answer or a wrong answer leads to the next challenge, not straight to a ban.
- Threshold
- The client is only banned from a configurable threshold — for example through a dynamic rule.
- Categories
- Known bot categories can be monitored, allowed or blocked per application.
- Direct traffic
- Only traffic that passes through the platform is verified.
- AI assistants
- Copilot and Gemini crawlers currently cannot be told apart from the Bing and Google spiders — they are counted as search crawlers.
They’re always just one phone call away — I’ve called them on weekends, days, and nights, and I always get a response. With Link11, I have direct access to security experts.

Questions before you decide. Answered directly.
Will this block Google too?
Only if you want it to. You allow the bots you want and lock out the rest — decided by bot type, behavior and origin. Search and AI crawlers have their own filters whose action you set.
Will our users now get CAPTCHAs?
Usually not. The passive check runs invisibly with the page load, the active one via a brief redirect. A visible task is the interactive method — and a client that fails a check first gets another one, not an immediate ban.
What about AI crawlers?
They have their own dashboard. It shows, per crawler, how much it requests and what was passed, and you decide globally or per path whether it is monitored or blocked. One limitation: Copilot and Gemini currently cannot be separated from the Bing and Google spiders.
How does this protect our app?
Through the Mobile SDK. It signs the app, authenticates the device and adds a cryptographic HMAC signature to every request. The platform can then tell that a request comes from a real app user and not from a bot or emulator.
What does Bot Management cost?
Bot Management is part of the WAAP platform. Core includes bot challenges, Bot Management is an optional add-on, and Advanced Bot Management is part of Enterprise (see pricing); larger setups get an individual quote based on scope and operating model.
Let’s talk
Your business stays online. We’ll show you how.



