How to Set Up BotRefund on a Custom-Coded Website

Setting up BotRefund on a custom-coded website is a direct code integration. You paste a single script tag into your HTML templates, deploy the updated files, and confirm the script loads in a browser. There is no CMS plugin and no marketplace install; you work straight in your source files.

For most custom sites the fastest path is: copy your BotRefund snippet from your dashboard, place it before the closing </body> tag in every template that receives traffic, push the change to production, then run BotRefund's free bot audit to confirm detection is active. Total setup time is about one minute for a typical static or server-rendered site.

How BotRefund works after you add the script

BotRefund runs client-side on your pages. It collects signals from each visitor's browser, network, device, and behavior. The system uses 106 independent checks to evaluate a visit. A single anomaly is not a verdict; privacy tools, travel, corporate networks, and unusual devices can make genuine people look odd. BotRefund cross-checks each signal against the others and feeds the complete pattern into its prediction AI. Only then does it classify a visit as bot or human.

Once a bot click is confirmed, BotRefund captures video proof for each one, proves the bot click, negotiates with Google and Meta, and gets your money back. Refund claims can reach back to 2017 for Google Ads spend.

What you need before you start

• A BotRefund account. Sign-up takes about a minute and no credit card is required.
• Access to your site's HTML. You need the source files or template engine, not just a built preview.
• A way to deploy to production. Your edited templates must go live for the script to load.
• A browser with developer tools. You will use the network tab to confirm the script file is fetched.

Step-by-step setup for a custom-coded site

1. Create your BotRefund account. Go to BotRefund.com and sign up. You will land in a dashboard that gives you your site's unique snippet. No credit card is required.
2. Copy the snippet. The snippet is a small JavaScript file reference or inline loader. Keep it as-is; do not modify the URL or query parameters.
3. Choose the insertion point. Best practice is before the closing </body> tag. This keeps the script from blocking initial page rendering.
4. Add the snippet to every template. For a static HTML site, paste it into each page. For a server-rendered app like Django, Rails, or Laravel, add it once to the base layout so inherited pages include it automatically. For a static site generator, edit the default layout file.
5. Handle single-page apps. If you use React, Vue, or another SPA framework, the code lives in your index.html. The script loads once on initial page load, which is what BotRefund expects. It keeps collecting behavior data across client-side navigation.
6. Deploy the change. Push your updated templates or build output to your host. Hard-refresh your browser after deploy.
7. Verify the script loads. Open developer tools, go to the Network tab, and look for the BotRefund script file. On the BotRefund dashboard, start a free bot audit.

How to verify the script is live and detecting

After deployment, verification takes two steps.

Browser check. Open your live site in an incognito window. Open developer tools (F12 or Ctrl+Shift+I), click the Network tab, and reload the page. You should see a request to BotRefund's script domain. If the request is missing, the snippet was not added to the page you are viewing, or the deployment did not go live.

Dashboard check. From your BotRefund account, run the free bot audit. It will start collecting signals from your site's visitors. Because BotRefund weighs the complete pattern across browser, network, device, and behavior evidence, it can identify a visit as bot or human with 99% accuracy, according to the company's claim. Your audit report gives you a view of the bot signals present in your current traffic.

Common mistakes that break BotRefund setup

• Adding the script only to the homepage. Bot detection only works on pages where the script is present. If you only tag the homepage, bot clicks on product and landing pages go undetected.
• Placing the script inside a conditional block. Some developers wrap scripts in if statements or cookie-consent branches. BotRefund needs to run consistently; conditional inclusion can hide bot sessions.
• Deploying a build that removed the script. Minifiers and bundlers sometimes strip unknown tags. Check the compiled output after build.
• Testing only on localhost. Localhost confirms code, not live traffic. The script loads from BotRefund's domain, so it works on any deployed URL, but you must verify on a production or staging environment.
• Editing the snippet. Do not reorder parameters, change the script URL, or inline the file manually. It must load as provided.

Key facts about BotRefund

Limitations and when this guide does not apply

This guide covers custom-coded websites where you control the HTML output. It does not cover:

• Websites behind a CMS you cannot edit directly. If you use Wix, Squarespace, or a hosted SaaS builder that blocks raw HTML, use that platform's code-injection feature instead.
• Server-side-only integration. BotRefund's detection is client-side. If your site serves no HTML to the browser, there is no page to tag.
• Compliance or consent gates. If your privacy policy blocks third-party scripts before user consent, work out the consent flow before adding BotRefund.

Also note: detection is probabilistic, not absolute. A single anomaly is not a bot verdict. Privacy tools, travel, corporate networks, and unusual devices can produce unexpected behavior for genuine people. BotRefund cross-checks each signal against independent browser, network, device, and behavior data before making a call.

Frequently asked questions

1. Do I need a CMS to use BotRefund? No. The script is plain HTML and works on any site where you can edit templates.
2. Where exactly should the script go? Before the closing </body> tag is the safest spot. It keeps the script from blocking initial page rendering.
3. Does BotRefund work on single-page apps? Yes. Put the script in your index.html. It loads once and keeps collecting behavior data across client-side navigation.
4. How much does setup cost? Creating an account and adding BotRefund is free; no credit card is required. The free bot audit is part of the onboarding flow.
5. How does BotRefund decide a visit is a bot? It uses 106 independent checks covering browser, network, device, and behavior evidence. The prediction AI weighs the complete pattern rather than trusting a raw rule.
6. What evidence does BotRefund use for refund claims? BotRefund detects bot clicks and captures video proof for each one, then negotiates with Google and Meta to get your money back.