How to Interpret the Bot Score in Your Free Audit Report

The bot score in your free BotRefund audit is a single number that summarizes how much of your paid traffic looks automated. It is derived from 106 independent browser, network, device, and behavior checks — things like empty font canvas, suspicious ports, ghost clicks, robotic mouse paths, and superhuman input speed — each weighted by an AI model that cross-references every signal before labeling a session as bot or human. A score of 19% means roughly one in five paid clicks came from a source that failed multiple independent checks; a score of 2% means the traffic is mostly clean.

What the bot score actually measures

The score is not a raw count of blocked IPs. It is the percentage of paid sessions that the model classifies as invalid after evaluating the full evidence stack. Each session gets a probability; sessions above the decision threshold roll into the bot bucket. The report also shows the volume of flagged sessions, the ad platforms they came from (Google, Meta, or both), and the estimated dollar value of those clicks based on your reported spend.

How BotRefund calculates the score

BotRefund runs 106 independent checks on every visit. Signals include hardware and GPU fingerprinting, empty font canvas detection, suspicious port analysis, ghost click detection, honeypot trap interactions, robotic linear mouse movements, absence of humanlike mouse tremor, superhuman input speed under 1ms, grid-aligned movement patterns, absence of clicks or scrolling, and unnatural session durations. No single check decides the verdict. The AI prediction engine weighs the complete pattern across browser, network, device, and behavior evidence to reach 99% accuracy through corroboration, not one browser tell.

Score thresholds and what they mean for your budget

• 0–5%: Low invalid traffic. Your targeting and platform filters are working. Routine monitoring is enough.
• 5–15%: Moderate exposure. Some campaigns or placements (often Meta Audience Network or display partners) are leaking budget. Review the placement breakdown in the report and consider exclusions.
• 15–30%: High exposure. A significant chunk of spend is wasted. The report will usually show specific campaigns, devices, or geos driving the score. This is the range where refund claims become worthwhile.
• Above 30%: Critical. Bot traffic is dominating paid visits. Immediate action: pause affected campaigns, submit refund evidence to Google and Meta, and deploy BotRefund's pixel protection to stop conversion pixel poisoning.

Reading your audit report breakdown

The free audit report splits the score by channel, campaign, device type, geography, and detection signal. Look for:

• Channel split: Google Search vs. Display vs. Meta Feed vs. Audience Network. Audience Network often shows 98%+ bounce rates and sub-0.1-second sessions because mobile app publishers run background click scripts.
• Signal contribution: Which of the 106 checks fired most often. If "empty font canvas" and "suspicious ports" dominate, you're seeing headless browsers or VPN/proxy farms. If "ghost clicks" and "superhuman speed" lead, it's click-fraud scripts.
• Dollar impact: The report estimates wasted spend using your average CPC and the flagged session count. This is the number you take to the ad platform for a billing dispute.

Common misinterpretations

• "A 10% score means 10% of all visitors are bots." It means 10% of paid clicks are flagged. Organic, direct, and referral traffic are not scored.
• "One weird signal = bot." Privacy tools, corporate networks, and unusual devices can trigger a single anomaly. BotRefund keeps each signal as evidence, not a verdict, and only flags a session when multiple independent signals agree.
• "The score is final." The free audit is a snapshot. Scores shift when you change targeting, add exclusions, or when fraudsters rotate infrastructure. Re-run the audit after any major campaign change.

What to do with your score — a decision framework

1. Under 5%: Keep monitoring. Re-audit monthly or after budget increases.
2. 5–15%: Open the placement breakdown. Exclude the worst placements (often Audience Network, display partners, or specific apps). Re-audit in two weeks.
3. 15–30%: Export the refund evidence dossier. The report organizes flagged sessions with timestamps, IPs, signal details, and video proof. Submit to Google Ads and Meta billing support. Simultaneously enable BotRefund pixel protection so future bot sessions don't fire your conversion pixels.
4. Above 30%: Pause the affected campaigns immediately. File refund claims for the last 90 days (BotRefund can recover spend dating back to 2017). Deploy full protection and schedule a live audit call with the enterprise team to map a recovery and escalation plan.

Limitations of the bot score

• The score only covers traffic that reaches your site with the BotRefund script installed. It cannot see clicks that bounce before the script loads.
• It reflects the detection model at the time of the audit. New bot techniques may not be caught until the model updates.
• Refund approval depends on the ad platform's review. BotRefund provides the evidence; Google and Meta decide the credit. Historical approval rate across clients is 83%.
• The free audit samples a time window. A one-day spike or lull can skew the percentage. Run audits across multiple weeks for a stable baseline.

Key facts

Metric	Value	Source
Independent detection checks	106	S1
Model accuracy claim	99% via corroborated signals	S1
Estimated bot click share of ad budget	Up to 20%	S2, S3, S7, S8
Customer refund success rate	83%	S2
Setup time for free audit	About 1 minute, no credit card	S2, S3, S7, S8
Refund lookback window	Google Ads spend back to 2017	S2, S3, S7, S8
Core behavior signals	Ghost clicks, honeypot traps, robotic mouse, no tremor, superhuman speed, grid-aligned paths, no engagement, unnatural durations	S2, S3, S7, S8

Terminology quick reference

• Bot score: Percentage of paid sessions classified as invalid after multi-signal AI evaluation.
• Empty font canvas: A fingerprint mismatch where the browser reports no system fonts — common in headless or spoofed environments.
• Suspicious ports: Network-level anomalies where connection ports don't match the claimed device or ISP profile.
• Ghost click: A click event that lacks the preceding human intent signals (hover, movement, focus).
• Honeypot trap: A hidden page element that only bots interact with.
• Pixel protection: Suppressing conversion pixels for flagged sessions so bidding algorithms don't optimize for fraud.
• Refund evidence dossier: Organized export of flagged sessions with timestamps, IPs, signal logs, and video replay for platform disputes.

FAQ

How often should I re-run the free audit?

Monthly for stable campaigns. Weekly after launching new creatives, changing targeting, or adding placement exclusions. The script stays on your site; each audit pulls the latest data.

Can I see which specific IPs or sessions were flagged?

Yes. The audit report includes a session-level table with timestamp, IP, user agent, triggering signals, and a video replay link for each flagged visit.

Does the bot score affect my Quality Score or ad rank?

Not directly. But if bot clicks inflate your CTR or conversion rate artificially, smart bidding will optimize for more of that traffic. Pixel protection stops the feedback loop.

What if Google or Meta rejects my refund claim?

BotRefund's evidence is built to platform dispute standards. If a claim is denied, you can escalate with the same dossier. The 83% approval rate reflects claims submitted with BotRefund evidence.

Is the free audit really free — no card, no trial expiry?

Yes. Add the script, let it collect data for a few days, then generate the report. No credit card, no auto-enrollment. You only pay if you upgrade to continuous protection or enterprise recovery services.

How does BotRefund differ from Google's or Meta's built-in invalid traffic filters?

Platform filters look at account-level patterns (IP reputation, click frequency). BotRefund analyzes client-side behavior on your landing page — mouse tremor, font rendering, hardware fingerprint, interaction timing — catching bots that pass platform checks because they originate from real user accounts or residential proxies.

Can I use the audit report to negotiate lower CPCs with my agency?

Absolutely. The report quantifies wasted spend by campaign and placement. Share it with your agency to justify placement exclusions, bid adjustments, or a shift to higher-quality inventory.

Further reading and comparison sources

These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.

• Am I a Bot? Free Bot vs Human Test - Check Your Human Score
• Free AI Website Audit — Get Your AIReady™ Score | FreeAIWe...
• Chatbot Accuracy Audits: What They Cover and What You Will Learn ...

How BotRefund can help

BotRefund installs in about a minute and starts scoring every paid session against 106 browser, network, device, and behavior signals. The free audit gives you a baseline bot score, a dollar estimate of wasted spend, and a refund-ready evidence dossier you can send to Google or Meta. If the score is above 15%, the platform also suppresses conversion pixels for flagged sessions so your bidding algorithms stop optimizing for fraud. The limitation: BotRefund only sees traffic that loads its script, so clicks that bounce before the script fires are not scored. Refund approval still depends on the ad platform's review, though 83% of client claims succeed with BotRefund evidence.