AdSense safety tool
Review suspicious traffic patterns before making ad or analytics changes. Enter GA4-style country, device, and source notes, compare RPM movement around a spike date, and produce a safe investigation summary without creating risky test activity.
Summarize the suspicious period using GA4-style dimensions, a manual RPM trend, and any server or CDN notes you have already collected.
Start with evidence you already have: GA4 traffic acquisition, geography, device category, engagement rate, pageviews, AdSense RPM trend, and the first date the spike appeared. The tool is designed for short summaries instead of raw exports so you can capture the signal: which countries changed, which sources look weak, and whether device mix or referrals stopped matching the site's normal audience.
Treat the output as a triage note, not a verdict. A high risk result means the pattern deserves evidence preservation and conservative mitigation. It does not mean you should click ads, generate visits, or experiment with detection systems. Those actions can create the exact behavior a publisher should avoid.
First, record the spike date and compare the same date range before and after the change. Second, segment by country, device, source, landing page, and engagement. Third, check server logs or CDN logs for repeated IP ranges, user agents, referrers, and request rates. Fourth, apply normal security controls for obvious abuse while keeping ads and analytics measurement clean.
Do not generate pageviews, click or test live ads, ask other people to click ads, simulate ad views, buy suspicious traffic, or attempt to evade Google detection. The right response is to collect evidence, remove abusive traffic sources where you control them, improve site quality, and follow AdSense policy guidance.
Use the Website RPM Simulator when the issue is revenue mix rather than traffic quality, or the AdSense Revenue Calculator for a direct PV x RPM planning estimate.
Invalid traffic is activity that may not represent genuine user interest, including automated visits, accidental or artificial ad interactions, referral spam, suspicious measurement activity, or traffic patterns that Google cannot confidently treat as valid.
No. This checklist is a publisher triage tool. It helps organize GA4, server log, RPM, source, country, device, and timing evidence before taking safe actions. It does not inspect an AdSense account or override Google's systems.
Preserve evidence, compare GA4 traffic dimensions, review server logs, block obvious abusive sources at the infrastructure layer when appropriate, and avoid touching ads or creating test activity. Do not try to generate pageviews, test clicks, or evade detection.
No. Do not click your own ads, ask others to click, simulate ad views, generate pageviews, or create traffic to test AdSense. Those actions can create policy risk and make diagnosis harder.