Google Analytics Spam and Bot Traffic Audit
Spot suspicious traffic that distorts reports.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Audit suspicious traffic in Google Analytics. Traffic by source, country, device, landing page, session duration and engagement for a period, and spikes: [TRAFFIC_DATA]. Make a checklist of signs and mark which each suspicious segment shows: a sudden spike from one source, engagement under one second, a single page, identical session durations, an implausible location, unusual hostnames or language settings, and fake referrals. Quantify the share of sessions affected: 1,800 suspicious sessions of 12,000 is 15 percent, and show the effect on conversion rate with and without them. Exclude the traffic from reports first with a saved comparison or filter that can be switched off, and keep a note of the date, the rule and the effect on key figures before any permanent change [VERIFY]. Recommend server-level or tool-level defences only through the person who manages the site, and never block ranges that might include real customers without checking. Return a table and a plan, testing before applying filters.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.
See an example result (fictional data)
Invented data. Total sessions 12,000. One source gives 1,200 sessions with 0.5 percent engagement and average duration 1 second. One country gives 600 sessions, all to the home page, all within one hour. Suspicious sessions = 1,200 + 600 = 1,800 = 15 percent of 12,000. After excluding in a report view, the conversion rate moves from 2.4 percent (288 / 12,000) to 2.8 percent (288 / 10,200). Documentation entry: 'From 1 March, report view B excludes sessions from source X and country Y (1,800 sessions, 15 percent). Reason: engagement under 1 second and one page only. Reviewed monthly by the site owner.'
Illustrative only, made-up data. Your results will differ and must be reviewed.