Page-level bot traffic control for landing pages and sensitive routes.
Protected Pages let you apply traffic rules directly to the destination that matters: landing pages, forms, signup flows, payment pages, and other routes where risky visits should be handled before they cause damage.
- Apply route-level rules to specific pages
- Allow, redirect, block, or rate-limit traffic
- Use country, referrer, schedule, and repeat-visit controls
- Review every outcome in Traffic Log
- USClean browserAllowed
- GBProxy / VPNRedirected
- DEDatacenterRedirected
- FRKnown botBlocked
When to use Protected Pages.
Landing pages
Protect ad landing pages where fake clicks, proxy users, and datacenter visits can waste spend.
Forms and lead flows
Reduce low-quality submissions before they reach your CRM or sales team.
Signup and onboarding routes
Add route-level checks to registration, trial, or onboarding pages.
Sensitive pages
Keep payment, invite, or gated pages behind a visible decision layer.
How a Protected Page handles a visit.
-
Step 1
Visitor opens protected URL
The click lands directly on the protected destination.
-
Step 2
KillBot checks page policy and visitor signals
IP, ASN, country, referrer, behavior, and the page's own rules are evaluated together.
-
Step 3
Clean traffic reaches the real page
Allowed visitors land on the destination unchanged.
-
Step 4
Risky traffic is redirected, blocked, or rate-limited
The outcome is recorded in Traffic Log with reason and decision.
What a Protected Page controls.
| Control | What it does | Why it matters |
|---|---|---|
| Protection mode | Controls allow, redirect, block, or rate-limit behavior. | Lets teams start safely before using hard blocks. |
| Redirect target | Defines where risky traffic should go. | Keeps sensitive pages away from suspicious visits. |
| Country and referrer rules | Applies local rules to specific pages. | Avoids one global policy for every route. |
| Schedule windows | Changes behavior by time or campaign window. | Useful for campaign-specific traffic flows. |
| Repeat-visit handling | Spots suspicious repeat activity. | Helps control scrapers, checkers, and repeat abuse. |
| Traffic Log visibility | Records outcome and reason. | Makes routing decisions reviewable. |
Protected Pages vs Smart Links.
The right layer depends on where the traffic decision needs to happen.
Protected Pages
- Best when the visitor lands directly on the real page
- Decision happens close to the final destination
- Best for landing pages, forms, signup, payment, sensitive routes
- Local page rules matter
Smart Links
- Best when traffic first passes through a routing, tracking, or redirect domain
- Decision happens before the final destination opens
- Best for campaign links, redirect domains, affiliate flows, tracker domains
- Link-layer screening matters
Common questions.
What is a Protected Page?
A Protected Page is a route in KillBot where you apply page-level rules — country, referrer, schedule, repeat-visit, and protection mode — directly to a real destination URL on your site.
Should I use Protected Pages or Smart Links?
Use Protected Pages when visitors land directly on the real page. Use Smart Links when traffic first passes through a routing, tracking, or redirect domain.
Can I redirect risky traffic instead of blocking it?
Yes. Redirect mode is the default safer rollout — risky visits are sent to a configured safe URL instead of the protected page. Use it to verify the pattern in the Traffic Log before moving to stricter blocking.
Does each Protected Page have its own rules?
Yes. Country, referrer, schedule, repeat-visit, and redirect rules are configured per Protected Page. A campaign landing page can have different controls than a payment page on the same account.
Can I review what happened to each visit?
Every visit appears in the Traffic Log with IP, country, ASN, matched category, reason, source route, and final outcome.
Start with one protected route, verify the log, then scale.
Create one Protected Page, run it in redirect mode, watch the first decisions land in the Traffic Log, then expand only after the route behaves predictably.