AdSense "low value content" on tool and app sites
Plain Reckoner

Tool sites keep getting rejected for "low value content" — an observation, not a finding

858 words · about 4 min

Two site owners in one week reported being turned down by AdSense over and over for "low value content", while having real traffic and meeting every stated requirement. Both run software rather than write articles. One of them was accepted by a network that judges traffic instead of writing, on his first try, straight after six rejections from one that judges writing.

How it was measured
We read two public discussion threads and compared what each owner said against the sweep we had already made of Google's own AdSense help pages. This is a reading of two cases, not a count. It is graded C for exactly that reason, and the section at the bottom says what would turn it into a measurement.
Last checked
Listen to this Playing read from this page, nothing added
Watch it plot 35s · narrated · the same figures as above

Two threads, six days apart, with the same shape.

A site of browser games: 17 games the owner built himself, 50,220 visits and 191,660 pageviews in thirty days, visitors from 148 countries, legal pages, an about page with a real name on it, six languages, fourteen months old. Six rejections, all "low value content."

A site of small tools: about twenty pages in Google's index, fifteen of them real writing, headings laid out properly, around 80 clicks a day, mostly from the US. Rejected again and again since May, always "low value content."

Neither is a flimsy site by any ordinary reading. Both had done the formal things. Both were told the same generic sentence and given nothing they could act on.

What Google actually publishes

We went through Google's own AdSense help pages in their raw form, quoting rather than summarising. They state no minimum number of posts, no minimum number of words, no minimum site age and no minimum traffic. There is no number anywhere in them.

That matters for these two cases specifically, because both owners spent months adding pages to hit numbers — "twenty pages of eight hundred words" — that appear nowhere in anything Google has written. One of them said it plainly: he had tried adding different pages each time and was turned down each time.

Traffic is not a weak input here. It is not an input. 50,000 visits neither helped nor was overlooked.

The pattern we think we are seeing

On a site whose product is a tool or a game, the value is in the thing that runs. The text around it is thin compared with what people actually came for — not because the owner was lazy, but because that is what the product is.

Someone whose job is judging writing has very little writing to judge.

If that is right, it explains the part both owners found maddening: adding pages did nothing, because pages were never the problem. It also explains why the rejection is always the same generic sentence — if the mismatch is about what kind of site it is, there is no specific fix to name.

The strongest evidence, and it is not ours

The owner of the tools site, after six AdSense rejections, applied to Journey by Mediavine and was accepted on his first try.

That is a different test — one that looks at traffic and how people behave on the site rather than at the prose — passing him immediately after a writing test had failed him six times. It is the cleanest signal in either thread, and neither thread picked it up.

The one requirement that is real

Whatever else is going on, there is exactly one page Google genuinely insists on, and it is the one most often subtly wrong.

From the Publisher Policies, word for word: publishers must "have and abide by a privacy policy that clearly discloses any data collection, sharing, and usage that takes place as a consequence of your use of Google products and services". It must also say "that third parties may be placing and reading cookies on your users' browsers".

Policies produced by a generator, and ones translated through several languages, routinely cover data protection in general and never say that one thing. It is a hard requirement, not a judgement call.

We were missing it on this site ourselves until we ran our own published checklist against our own pages. That is not a hypothetical.

Why this is graded C

This is two threads. It is an observation, not a measurement, and publishing it as anything else would be the error this site exists to avoid.

Two cases that agree can agree by coincidence. Both came from the same subreddit, and a subreddit picks out people who were rejected and were annoyed enough to post — the ones who got in, and the ones who quietly gave up, never appear there at all. We have written a separate note about exactly this way of choosing who you look at manufacturing exactly this kind of result.

What would make it a measurement

Count rejection threads over a fixed window, sort each site into software or writing using a rule written down before looking at any of them, and compare the rejection rate for one against the other.

That needs access to Reddit's data feed, which is no longer something you can simply take. Reddit closed off self-service access under its Responsible Builder Policy: every new key has to be approved through a request form. We assumed at first that our rejection was about the standing of our account, and it was not — the door is shut to everyone by default, and we have asked for it to be opened.

Until then this stays at C, and anyone planning around it should treat it as a hypothesis worth testing rather than a number worth using.

If you have been rejected with a tool or app site, or accepted with one, that is the data point we are missing. It is worth more than another thread of guesses.

Tracked as TOOLSITE-LOWVALUE. If a number here looks wrong, tell us and we will check it against the source.

One email per finding

Get these as they land

One email per finding — the number, the method, and the date it was true. No schedule, because measurements do not arrive on one.

Data controller: Plain Reckoner. Contact contact@plainreckoner.com.