You can spend a month writing articles and still get rejected from AdSense in under a minute because your About page still has Lorem ipsum, or your Privacy Policy never says the word “cookies.” The review process does not start with your best post. It starts with the boring trust pages most people skip. This is the pre-flight checklist that fixes those surfaces before you click “Apply.”
TL;DR
Before you submit, do exactly this: publish a real About page (200-400 words, a real name or fixed pseudonym, a working contact link), a Contact page with a visible non-bouncing email, and a Privacy Policy that names cookies, third-party ad serving, and Google AdSense and links Google’s “How Google uses information” page. Then click every nav and footer link to kill dead ones, confirm the Google account you apply with owns the site’s verified Search Console property, serve everything over HTTPS, and have your W-9/W-8BEN and a USD-capable payout method ready for after approval. Budget 30 focused minutes. Most “low value content” rejections in 2026 trace back to one of these surfaces being broken — not to thin articles.
Why reviewers reject “good” sites
AdSense’s review looks at a predictable set of surfaces in roughly this order: trust pages (About / Contact / Privacy), site navigation, a sample of articles, and then identity and account ownership. Google’s own eligibility page requires you to be at least 18, to own or have admin access to the site’s HTML, and to run original content that complies with the AdSense Program policies. Notice what is not on that list: a traffic minimum or an official article count. Google publishes neither.
That is why the rejection message is so misleading. “Low value content” is the catch-all label, but in practice it fires when a trust page is missing or placeholder, when navigation has dead links, or when the articles read as machine-generated and interchangeable. A 2026 pattern reviewers and the SEO community keep flagging: posts with zero first-person voice — no “I tested this,” no “here is what broke” — get read as generic and penalized. The fix below is mostly about the trust pages, because that is where 30 minutes buys the most approval odds.
You should already clear the content bar before running this checklist. Practitioner consensus in 2026 lands around 15-20 substantial posts (aim for 800+ words each, with genuine first-hand specifics) and a domain at least a couple of months old; sites under three months old see noticeably higher rejection rates. If you are not there yet, fix that first — see when to apply for AdSense.
The 30-minute checklist
| Surface | What reviewers check | Pass condition |
|---|---|---|
| About page | Is there a real human and a real reason the site exists? | 200-400 words, real name or fixed pseudonym, photo or avatar, contact link |
| Contact page | Can a reviewer actually reach you? | Visible, monitored email that does not bounce (a form alone is allowed) |
| Privacy Policy | Cookies + ad serving + AdSense named | Mentions cookies, third-party ad cookies, Google AdSense by name, and an opt-out path |
| Navigation | Any dead or “coming soon” links? | Every menu and footer link resolves to a live page |
| Account ownership | Does the applying Google account own the property? | Same Google account verified in Search Console |
| Transport | HTTPS everywhere? | Valid SSL, no mixed-content or plain-HTTP pages |
| Payout (post-approval) | Tax + payment ready | W-9 (US) or W-8BEN (non-US individual); USD-capable payout method |
Work top to bottom:
- About page. Write 200-400 words. Use a real name or a pseudonym you will keep, add a photo or avatar, explain in one honest paragraph why the site exists, and link your contact. Too short reads as fake; padding it past 400 words reads as filler. One concrete sentence about your actual experience with the topic does more for E-E-A-T than three paragraphs of mission statement.
- Contact page. Put a working email in plain text. A form is allowed, but a visible address that you actually monitor is stronger, because reviewers do sometimes email to confirm site ownership and a bounce blocks approval. Avoid a
no-reply@address. - Privacy Policy. It must explicitly name: cookies, third-party advertising cookies, Google AdSense, and how a user can opt out (link Google’s How Google uses information page). Free generators such as Termly or privacypolicies.com are fine for an indie site — just change the site name, domain, and dates so it does not look copy-pasted.
- Audit navigation. Click every menu item and footer link. Fix broken ones, 301-redirect moved ones, and delete every “coming soon.” A single dead link nudges a borderline review toward rejection.
- Account ownership. The Google account you apply with must own the site’s verified property in Search Console. Mismatched ownership is a common, fully avoidable rejection cause. Verify in Search Console first, then apply with that same account.
- HTTPS. SSL is a hard requirement. Vercel, Netlify, Cloudflare Pages, and Firebase Hosting all issue certificates free. If anything still loads over plain HTTP in 2026, fix it before applying.
- Payout prep. You do not submit this at application time, but line it up now: a payment method that can receive USD, plus your tax form (W-9 for US persons, W-8BEN for non-US individuals). The standard USD payment threshold is $100 before your first payout, and Google mails a 6-digit PIN to verify your address once earnings cross the verification threshold — you then have 4 months to enter it.
Verification code: the one technical step
After you apply, AdSense gives you a snippet to paste into the <head> of every page. The single most common technical mistake is pasting it into <body> instead. In an Astro, Next.js, or Hugo theme this is easy to get wrong because the layout file may not make <head> obvious. Paste it once in your shared layout’s head, deploy, then open the live page and use “View source” to confirm the script tag sits inside <head> before you tell Google to check. The newer site-level connection in AdSense can also use an ads.txt file or a meta tag; whichever method the dashboard shows you, verify it is live with View source rather than trusting the editor preview.
Common pitfalls
- Copy-pasted Privacy Policy with another site’s name or stale dates. Reviewers spot it instantly; change the site name, domain, and effective date.
- A bouncing or unread contact email. If a reviewer emails to confirm ownership and it bounces, approval stalls.
- A “Disclosure” or “Affiliate” page but no Privacy Policy. The Privacy Policy is the one genuinely required document; the others are optional.
- Verification snippet in
<body>. Confirm via View source that it is inside<head>. - Applying with a previously banned Google account. AdSense enforcement is per-person and per-account. Use a clean account if yours was banned — but do not try to circumvent a ban; that gets you re-banned faster.
- Gutting the site mid-review. Restructuring navigation or deleting sections during review can reset or fail it. Keep publishing, but leave the structure alone.
FAQ
- How long does the review take after I submit?: As of June 2026, anywhere from about 48 hours to roughly 2 weeks, with most decisions landing in 1-2 weeks. A longer wait usually means a human reviewer is involved, which is fine — be patient and avoid dramatic site changes during the review. If your account was already approved but a newly added site stays “Getting ready” for weeks, that is a separate per-site review — see account approved but this site is still pending.
- Is there an official minimum number of articles or traffic?: No. Google’s eligibility page sets no article count and no traffic minimum. The 15-20 posts and 800+ words figures are community practice, not policy — they exist because thin, generic content is what actually triggers the “low value content” rejection.
- Can I keep publishing during review?: Yes, and it helps — an active site reads as legitimate. Just do not restructure navigation or remove large sections mid-review.
- Do I need an SSL certificate?: Yes. HTTPS is required. Vercel, Netlify, Cloudflare Pages, and Firebase Hosting all provide SSL for free, so there is no reason to apply on plain HTTP.
- What if my country is not on the AdSense supported list?: Some countries cannot host AdSense publishers due to sanctions or platform restrictions. Check the supported-countries list before investing effort. Using another country’s payout method to work around it violates AdSense terms and risks a permanent ban.
- When do I get paid, and how much do I need first?: Earnings pay out once they cross the standard $100 USD threshold. Before that, Google mails a PIN to verify your address once you hit the lower verification threshold; you have 4 months to enter it.
Related
- When to apply for AdSense
- What is AdSense in 2026
- “Low value content” rejection — how to recover
- AdSense on bilingual sites
- AI AdSense Readiness Review Tutorial
- How to Use AI to Detect Thin Content (Before Google Does)
Tags: #Indie dev #AdSense #Monetization #Privacy policy #Getting started