Seatext library / BotRefund evidence
Add Free Bot Protection to Your Website in One Simple Step
You can protect your site from bots at no cost by installing BotRefund’s free client‑side script, which runs a suite of behavioral checks and AI analysis to flag non‑human traffic.
✓ Built for advertisers who need clear, refund-ready traffic evidence.
To add free bot protection, simply embed BotRefund’s free JavaScript snippet on your pages. The script runs dozens of independent behavioral checks—including the Impossible Tab Speed check—and sends the results to BotRefund’s AI model, which decides if a visit is likely a bot.
Installation takes about a minute and requires no credit card. After the script is live, BotRefund continuously monitors traffic and flags suspicious activity without charging you.
| Signal | What it checks | Why it matters |
|---|---|---|
| Impossible Tab Speed | Detects timing mismatches that real users cannot produce | Bots struggle to mimic natural pauses and hesitation |
| Biometric & Behavioral Interactions | Analyzes mouse tremor, movement curves, and click patterns | Human motion is imperfect; bots are overly linear |
| Cross‑checked Context | Correlates browser, network, and device data | Single anomalies are not verdicts; multiple signals improve accuracy |
What is free bot protection?
Free bot protection refers to tools that you can use without paying a subscription fee. Most rely on client‑side scripts that collect behavioral data (mouse movement, typing speed, tab focus) and compare it to known human patterns. The data is then evaluated by a model that decides whether the visitor is a bot.
Why you need it now
Even legitimate sites lose money when bots click ads, scrape content, or submit fake forms. Invalid traffic inflates analytics, poisons conversion pixels, and can lead to higher ad costs. Blocking bots early keeps your data clean and your budget intact.
How bot traffic harms SEO, ad spend, and user experience
Search engines treat sudden spikes in bounce rate or low dwell time as quality signals. When bots generate thousands of rapid page loads, they raise bounce rates and lower average session duration. This can cause rankings to slip.
Ad platforms charge per click. Bots that click but never convert waste spend and can trigger higher cost‑per‑click (CPC) rates because the algorithm thinks the audience is less valuable.
For real users, bot‑filled forms create spam, slow down server response, and may expose security vulnerabilities. A clean traffic stream improves page load speed and overall experience.
Understanding each behavioral signal
Impossible Tab Speed looks for timing mismatches that a real browser cannot produce. For example, a script may fire a click event 5 ms after a page load—faster than any human could react. This signal is part of the 106 independent checks described in source S1.
Biometric & Behavioral Interactions capture mouse tremor, movement curves, and click pressure. Humans exhibit tiny jitter; bots often move in perfectly straight lines. When the script records a perfectly linear path across a form field, the AI flags it as suspicious.
Cross‑checked Context aggregates browser fingerprint, network latency, and device orientation. If the tab speed is odd but the device reports a high‑resolution touchscreen and normal latency, the AI weighs all evidence before deciding. This multi‑signal corroboration is why BotRefund claims 99 % accuracy, as noted in source S1.
Each signal alone is not a verdict. BotRefund’s AI prediction layer (source S1) combines them, applies weighting, and outputs a confidence score. The free tier still runs the full suite of checks, but it does not automatically generate refund evidence packages.
Core free methods you can combine
- CAPTCHA alternatives – simple JavaScript challenges that ask for a mouse movement or a short delay.
- Rate limiting – limit the number of requests per IP per minute using server config.
- Honeypot fields – hidden form inputs that bots fill but humans ignore.
- BotRefund free script – a comprehensive behavioral suite that works without a paid plan.
Step‑by‑step: Add BotRefund in one minute
- Visit the BotRefund homepage and click “Add BotRefund to your website in about one minute. No credit card required.”
- Copy the JavaScript snippet shown on the signup page.
- Paste the snippet just before the closing
</head>tag of every HTML page you want to protect. - Publish the changes and clear any CDN cache.
- Open your site in a private browser window and verify that the script loads (check the network tab for
botrefund.js).
Prerequisites and common pitfalls
Make sure your site can serve external JavaScript and that no Content‑Security‑Policy (CSP) blocks the BotRefund domain. A common mistake is placing the snippet after other scripts that already manipulate the DOM; always load BotRefund first to capture raw user interactions.
If you use a strict CSP, add script-src https://botrefund.com to the policy. Otherwise the script will be blocked and no signals will be collected.
Verify that protection works
After installation, open BotRefund’s free audit page (linked from the homepage) and run a live audit on your URL. The audit will show which signals fired and whether any visits were flagged as bots. Look for a green “human” verdict on your own test session.
The audit also displays the raw timing data for the Impossible Tab Speed check, letting you see how close a real user’s click latency is to the bot threshold.
Free client‑side vs paid or server‑side solutions
Free client‑side protection runs entirely in the visitor’s browser. It is easy to deploy, requires no backend changes, and works for any site that can add a script tag. Accuracy depends on the quality of the behavioral signals, which BotRefund supplies at 99 % accuracy (source S1).
Paid plans add server‑side verification, automated refund filing, and dedicated support. Server‑side checks can validate IP reputation and request headers before the page renders, catching bots that block JavaScript. However, they add latency and require server resources.
Privacy considerations also differ. Client‑side scripts send anonymized interaction data to BotRefund’s AI; this is covered by their privacy policy. Server‑side solutions may store IP addresses and device fingerprints, which can raise GDPR concerns.
Choose the free tier if you need quick protection, have limited technical resources, and are comfortable with client‑side data collection. Upgrade to a paid or server‑side plan when you need bulk evidence for ad‑platform disputes, higher traffic volumes, or stricter compliance requirements.
Limitations and when to consider a paid plan
The free tier provides all behavioral checks but does not include automated refund filing or dedicated support. If you need bulk evidence packages for ad platform disputes, you’ll have to upgrade. Also, extremely privacy‑focused users (e.g., using strict VPNs) may occasionally be flagged; you can whitelist IP ranges in the dashboard.
Common Follow‑Up Questions
- Can I combine BotRefund with other tools? Yes. The script runs independently, so you can keep rate limiting, honeypots, or third‑party CAPTCHAs alongside it.
- How does privacy regulation affect data collection? BotRefund only sends aggregated interaction metrics, not personal identifiers. The free tier complies with GDPR and CCPA, but you should review the privacy notice on the BotRefund site (source S2).
- What if my CSP blocks the script? Add
script-src https://botrefund.comto your CSP header or use a nonce/hashed script approach. The script will then load correctly. - Will the script work on single‑page applications (SPA)? Yes. BotRefund listens for navigation events and re‑evaluates signals on each virtual page view.
- Can I adjust the sensitivity? The dashboard lets you set a confidence threshold. Lowering it catches more bots but may increase false positives; raising it does the opposite.
FAQ
- Is the script really free? Yes, the JavaScript snippet and real‑time detection are free forever. Paid features are optional.
- Will it slow my site? The script runs asynchronously and adds less than 50 ms of overhead on average.
- Do I need a server‑side component? No, BotRefund works entirely client‑side for the free tier.
- Can I test it without affecting users? Use the “Get free bot audit” link to run a sandbox test on a staging URL.
- What if legitimate users are blocked? Review the audit report; you can adjust sensitivity or add exceptions in the dashboard.
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Learn more
Visit the website for more information.