Invalid traffic risk: what small publishers should document before appealing

Small publishers should document traffic sources, unusual spikes, ad placement changes, and prevention steps before treating an invalid traffic issue as a mystery.

Invalid traffic can include artificial clicks or impressions, but the practical problem for a publisher is evidence. If a site suddenly receives unusual traffic from one referral, a paid campaign, a social post, or a bot-heavy region, the publisher needs a record of what changed. If friends, team members, or hired helpers interacted with ads, that risk should be acknowledged and stopped. If a layout change put ads too close to navigation, the placement should be corrected.

Before appealing or asking for help, collect a timeline: traffic spike dates, top sources, affected pages, countries, devices, recent campaigns, ad placement changes, analytics filters, blocked referrers, and steps taken to prevent repeats. The goal is not to prove innocence with one screenshot. The goal is to show that the publisher understands the pattern and has reduced future risk.

Avoid public advice that encourages clicking, testing ads manually, buying low-quality traffic, or asking visitors to support the site through ads. Those behaviors can create more risk.

The practical rule is: document what changed, remove controllable risks, and explain prevention steps before escalating.

Invalid traffic risk: what small publishers should document before appealing

// COMMENTS

ON THIS PAGE