Seatext library / BotRefund evidence

Where to Add BotRefund Protection in Your Website's Settings

BotRefund protection is not added through your website's own settings panel. You connect your website to the BotRefund dashboard, then configure protection there. The whole setup takes about one minute with no credit card...

Built for advertisers who need clear, refund-ready traffic evidence.

Where BotRefund protection really lives

BotRefund protection does not live inside your website's admin area. It is not a toggle in WordPress, Shopify, or your hosting control panel. Instead, protection is managed from the BotRefund dashboard. You add your website to BotRefund, and the dashboard becomes the control center for detection, evidence, and refund requests.

Think of it like Google Analytics. You add a small script to your site, and the service starts collecting data. All configuration, reports, and actions happen on the BotRefund side. You do not need to touch your website's settings again unless you want to remove the script.

This design makes sense because bot detection requires constant updates and a central view of traffic. If the logic lived on your server, it would be harder to update and less consistent across all clients. The dashboard also lets BotRefund show you evidence and manage refunds from one place.

How to add your website to BotRefund

Adding your website is a short process. Based on the source pack, the typical setup time is about one minute, and no credit card is required to start.

  1. Go to BotRefund.com and click Create account.
  2. Enter your website URL and work email.
  3. Confirm your email if prompted.
  4. Add the BotRefund script or pixel to your site. You can do this manually or through the integration guide provided in the dashboard.
  5. Once the script is live, the free bot audit starts automatically.

The script is a small JavaScript snippet. It loads in the background and begins collecting behavioral data. You do not need to change DNS records or reconfigure your hosting. The script is the only connection point.

If you use a content management system, the integration guide in your dashboard shows platform-specific steps. For example, WordPress users may insert the script in the theme header. Shopify users may edit the theme's layout file. The guide gives exact instructions for each common platform.

You can also add the script using a tag manager like Google Tag Manager if you prefer. The guide explains how to do that as well. Regardless of the method, the result is the same: the script runs on every page and starts collecting data.

After you add the script, verify that it loads correctly. You can open your browser's developer tools and check the network tab for a request to BotRefund. Or you can view the page source and see the script tag. If it is present, the audit will start.

What happens after you add the site

Once the script is in place, BotRefund runs a live audit of your site traffic. The dashboard shows you flagged sessions and the evidence behind each one. You do not need to wait for a report. Data appears as visitors come to your site.

The dashboard is organized into several views. The main report shows suspicious sessions, the reason each was flagged, and a confidence score. You can filter by date, device, campaign, or other dimensions. This helps you spot patterns, such as a spike in bots from a specific placement.

Each flagged session has an evidence file. BotRefund captures video proof of the session, along with the specific signals that triggered the flag. You can review the video to see the bot's behavior in action. This evidence is what you submit to Google or Meta when requesting a refund.

The dashboard also includes suppression tools. You can suppress conversion events for sessions you determine are invalid. This keeps fraudulent sessions from distorting your conversion data. When you suppress a conversion, the ad platform learns not to count that action as a real lead.

You can also export a full report at any time. The report contains all flagged sessions, evidence, and recommended actions. You can send this report to your ad platform or to BotRefund's negotiation team if you enroll in that service.

Understanding the detection signals

BotRefund does not rely on a single browser tell. It collects signals from hardware, behavior, and network patterns. The source pack mentions 106 independent checks. Each check adds one objective fact about the visit. The system cross-checks these facts before making a prediction.

For example, the CPU Concurrency Lie check looks for a mismatch between reported device details and actual behavior. A bot might claim it is a powerful desktop but run like a low-end VM. The Impossible Tab Speed check catches interactions faster than a person could realistically perform. A script can switch tabs or click faster than any human. The window.open Tamper check looks for bots that interfere with browser windows in unnatural ways.

In addition to these technical checks, BotRefund tracks behavioral patterns. The source pack lists eight categories:

  • Ghost click detection: catches clicks that happen without a natural sequence of human intent.
  • Honeypot trap interactions: watches for bots that respond to hidden or deceptive page elements.
  • Robotic linear mouse movements: flags unnaturally straight pointer paths.
  • Absence of humanlike mouse tremor: looks for missing tiny imperfections and jitter.
  • Superhuman input speed: identifies interactions under 1 millisecond.
  • Grid-aligned movement patterns: detects movement that snaps to precise lines.
  • Absence of clicks or scrolling: highlights sessions that stay too static.
  • Unnatural session durations: catches visit lengths that are too short, too long, or too uniform.

Each signal is treated as evidence, not a verdict. A single anomaly does not make a visit a bot. For example, a real user might use privacy tools that mask certain data. A corporate network might produce unusual traffic. Travelers might have different device behavior. BotRefund keeps these signals as evidence and cross-checks them against independent browser, network, device, and behavior data.

The AI model weighs the complete pattern. It does not trust a single raw rule. This corroboration is why BotRefund claims 99% accuracy. The source pack states that accuracy comes from corroboration, not one browser tell.

Key facts about BotRefund protection

FactDetail
Setup timeAbout one minute
Credit card requiredNo
Detection checks106 independent signals
Example signalsGhost clicks, honeypot traps, robotic mouse movement, superhuman input speed
Ad budget lost to botsUp to 20% of Google and Meta ad spend
Video proofCaptured for each flagged session
Refund recoveryRecovery from Google and Meta billing disputes, dating back to 2017
Case studyFinTrust recovered $140,000 and saw a 14% bot click rate and 18% conversion rate increase

These facts come directly from the BotRefund site and case studies. They are useful for planning, but actual results vary by ad spend and platform.

Limitations and what BotRefund does not do

BotRefund does not block every bot instantly. Its strength is evidence collection and refund recovery. You still need to work with Google or Meta to approve refunds. BotRefund can negotiate on your behalf if you enroll in that service, but approval is not guaranteed.

Also, the system can flag unusual behavior from real users, such as privacy tools, corporate networks, or travel. That is why it cross-checks signals before making a verdict. If you see a flag that looks like a false positive, you can review the video evidence and suppress it if needed.

If you only need basic spam blocking on your forms, a different tool might be simpler. BotRefund is built for advertisers who want to recover money from invalid clicks and keep conversion data clean. Small spenders might not see a return on investment.

BotRefund does not alter your website's performance. The script is lightweight, but it does add a little load. If you have many visitors, this could be a consideration, though the impact is usually minimal.

Frequently asked questions

Does BotRefund protect my website automatically once I add the script?

Yes. After you add the script, the free audit starts immediately. The dashboard begins flagging suspicious sessions right away.

Do I need to change my website's DNS settings?

No. You only add a script or pixel to your site. There is no DNS or server configuration involved.

Can I use BotRefund with any website platform?

BotRefund works with any site where you can add a JavaScript snippet. That includes WordPress, Shopify, Wix, and custom-built sites. The integration guide in your dashboard shows specific steps for common platforms.

How does BotRefund get refunds from Google and Meta?

BotRefund provides you with documented evidence of invalid clicks. You then submit that evidence to the ad platform as part of a billing dispute. BotRefund negotiates on your behalf if you enroll in that service.

What does the free bot audit include?

The free audit identifies suspicious paid visits and explains why each session was flagged. It gives you a baseline for what bot traffic looks like on your site.

Is there a limit on how far back I can claim refunds?

BotRefund can help recover refunds for Google Ads spend dating back to 2017, according to the source pack.

Next steps to add protection

Adding BotRefund to your website takes about a minute. Start with a free audit and see what invalid traffic is costing you.

You will manage everything from the dashboard, so bookmark it after you sign up. That is where you will find the audit report, suppression tools, video evidence, and refund case files.

If you have a large ad budget, consider talking to Enterprise Sales. The source pack mentions that BotRefund maps out a recovery, protection, and escalation plan based on your spend. This is useful for companies spending more than $10,000 per month.

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.

Learn more