Invalid traffic and AdSense: what the policy covers and how to stay clear of it

Invalid traffic is Google's term for any click or impression on an ad that does not represent genuine interest from a genuine person. The policy is broad by design, because the ways of generating fake engagement are numerous and keep changing. A few categories account for most enforcement action.

• Clicks or impressions a publisher generates on their own ads, whether by clicking directly, refreshing a page repeatedly, or viewing their own site excessively to inflate impression counts.
• Clicks solicited from friends, family or colleagues, even if the request is informal and even if no money changes hands.
• Automated traffic: bots, scripts, crawlers and traffic-generation tools that load pages or trigger ad requests without a human behind them.
• Incentivised clicking, including reward apps, click-for-click arrangements, and any scheme where a click is exchanged for payment, credit or a favour.
• Traffic bought from paid-traffic services, traffic exchanges or click farms, regardless of how the traffic is described by the seller.
• Accidental clicks caused by deceptive ad placement, such as ads positioned to be mistaken for navigation, or placed immediately next to buttons a visitor is likely to tap.

The common thread is not intent but effect. A click that does not reflect a person's genuine interest in the ad counts as invalid traffic whether or not the publisher meant any harm.

Search results and marketplaces are full of services offering to send visitors to a site, and some explicitly market themselves as "AdSense safe traffic" or "AdSense compliant traffic". There is no such thing. Any paid-traffic service, traffic exchange, or bot network sending visitors to a page carrying AdSense is generating exactly the invalid traffic the policy prohibits, and the fact that a seller labels it safe does not change what it is.

This applies regardless of whether the publisher clicks anything themselves. Sending non-genuine visitors to a monetised page inflates impressions and skews click patterns even if not a single ad is clicked, and that alone is enough to breach the policy. Paying for traffic to an AdSense site is one of the fastest routes to a permanently disabled account, and it is treated as a serious violation rather than an accident.

If a traffic service is being sold specifically to publishers running ads, treat that as a signal to avoid it entirely, not evidence that it has been made safe.

Google does not publish the mechanics of its detection systems, and no article, including this one, can tell you precisely how it works. What is publicly acknowledged is that Google analyses patterns across clicks, impressions, traffic sources and visitor behaviour, comparing them against what is typical for genuine human activity at that scale and in that context.

In practical terms this means unusual click-through rates, traffic arriving in sudden bursts from a narrow set of sources, sessions that behave nothing like normal browsing, and impressions concentrated in patterns that suggest automation rather than organic visits are all the kind of signal that gets scrutinised. A single unusual day rarely triggers anything; sustained or repeated patterns are what tend to matter.

It helps to separate three distinct outcomes that often get conflated.

• Silent filtering: Google routinely identifies and removes invalid clicks and impressions from earnings before they are ever paid out. This happens continuously in the background and does not necessarily mean anything is wrong with the account; some background level of invalid traffic is normal for almost every site.
• An invalid traffic warning: this is a formal notice that unusual activity has been detected on the account and needs attention. It is a chance to review traffic sources and behaviour and is not itself a suspension.
• Account disabling: this is the serious outcome, applied when Google concludes the invalid traffic is significant, deliberate, or left unaddressed. A disabled account generally cannot be reinstated for the same site, which is why a warning should always be treated as urgent.

A publisher who never sees a warning has not necessarily avoided invalid traffic entirely; they have simply stayed inside the range Google filters quietly without escalation.

Most invalid traffic issues are not caused by anyone trying to cheat the system. The common innocent causes are worth knowing precisely because they are avoidable.

• Testing how ads look by clicking them live rather than using a preview tool.
• A post going unexpectedly viral through a referrer, forum or link aggregator with a large proportion of automated or low-quality visits.
• A traffic-boosting or auto-refresh plugin that reloads pages or ad units far more aggressively than a real visitor would.
• A short-lived bot storm from scraping tools or scanners hitting the site in volume, unrelated to anything the publisher did.

None of these are usually catastrophic on their own, but they are the kind of thing that shows up in an invalid traffic review, so it is worth knowing they exist and addressing the ones within your control.

• Never click your own live ads, for any reason, including curiosity about placement or payout.
• Use the Google Publisher Toolbar or the ad preview and diagnosis tool to check what is showing, rather than viewing and clicking the live page.
• Exclude your own IP address, and those of anyone regularly working on the site, from analytics and from repeated live visits.
• Keep ad placements clearly separated from buttons, navigation and other interactive elements so visitors cannot click an ad by mistake.
• Audit referrer traffic periodically, particularly sudden spikes from unfamiliar domains, and investigate anything that looks automated rather than assuming it is good news.
• Turn off or reconfigure any plugin that auto-refreshes pages, auto-plays content, or reloads ad units on a timer.

None of this requires special tools or technical skill. It is mostly discipline: treat your own site the way you would want a stranger to behave on it.

If you receive an invalid traffic warning, treat it as urgent even though the account is still active. Review recent traffic sources, check for any plugin or embed capable of generating repeated ad loads, remove any referral or promotion arrangement that could look like solicited clicks, and stop any paid promotion aimed at the site while you investigate.

If the account is disabled, Google provides an appeal process, but it is worth understanding its limits honestly. An appeal is generally reviewed once, so it needs to be right the first time. Google does not disclose the detailed evidence behind the decision, so the appeal cannot be a request for more information; it needs to stand on its own as a specific, honest account of what happened and what has been changed as a result.

1. Identify the most plausible cause honestly, even if it reflects badly on a decision you made, such as testing ads live or using a traffic tool you did not fully vet.
2. Fix the underlying cause completely before appealing, not partially.
3. Write the appeal as a specific, factual account of the cause and the fix, avoiding vague denials or general statements of good intent.
4. Submit once, and treat the outcome as final; repeated appeals without new substance rarely succeed and can look evasive.

A generic appeal claiming no wrongdoing, without a specific explanation, is the most common reason reinstatement requests fail even when the original cause was genuinely accidental.