Creator Academy · AdSense guide

How to apply for Google AdSense

A plain-English walkthrough for small site owners who want their first AdSense approval, or who received a “low-value content” message and want to fix it properly.

Who this is for: owners of blogs, tool sites and small business sites who are about to click “Apply” in AdSense, or who were told their site “needs attention”. You do not need to be technical. You will learn what to fix first, how many pages you really need, how to apply, and what changes after approval. This guide is not from Google, and no checklist can promise approval.

1. Before you open AdSense

Most rejections come from the site, not the form. Check these five things first:

  1. You control the domain. You can edit files at the site root and add a code to every page. Free subdomains and sites you cannot edit cause problems at verification.
  2. Every page loads on https. Redirect the http and www versions to one address, and fix pages that return errors.
  3. About, Contact and Privacy pages exist. Link them in the footer of every page. The About page should say who runs the site; the Privacy Policy should explain cookies and advertising in your own words.
  4. The text is original. Copied articles, spun text and pages built only from scraped data are the fastest way to a rejection.
  5. No empty ad slots. Remove boxes that say “Advertisement” or “Ad space” until real ads run. Reviewers read an empty slot as a page built for ads instead of readers.

2. What “low-value content” usually means

When AdSense says a site has low-value content, it rarely means one bad page. It usually means the reviewer found patterns like these:

  • Shared templates: dozens of pages with the same layout and text, where only a name, city or keyword changes.
  • Language copies: machine-translated versions of the same pages added only to multiply URLs.
  • Duplicate titles: several URLs with the same title competing for the same search.
  • A chip-cloud blog: a blog index that is only a wall of tags or template links, with no real articles behind it.
  • Public deploy notes: README, CHANGELOG or audit files left open on the site.
  • Thin pages: pages far under a sensible length for their type. The SocialKit review rules use home 500+ words, tool pages 800+, guides 900–1,600, About 400+, Contact 120+ and Privacy or Terms 500+. These are review rules, not a Google quota.

3. How many URLs is enough?

Google does not publish a minimum page count. A site can fail with 200 thin URLs and pass with 30 strong ones. Use your indexable URL count as a band, not a target:

Indexable URLsWhat it means
1–7Too small if it is only a home page and legal pages. Add depth to what exists first.
8–25A healthy range for a small tool site, if each content page meets its floor and titles differ.
26–60Fine while thin pages stay under about 20 percent.
61–120Risk zone. If many pages are thin or templated, stop adding and noindex or merge the copies.
120+High risk of looking like scaled content unless the pages are real articles.

Do not add pages to reach a number. Add a new page only when a real topic is missing and you can write it yourself.

A worked example

Take a small PDF-tools site with 112 URLs in its sitemap. A readiness check measures 40 of them and finds: home page 1,400 words, About 930, Contact 320, Privacy 680, and nine handwriting worksheet pages where only 28 to 44 percent of the text is unique. The URL band is 61–120 and the thin share is 45 percent, so the check says “Fix the listed rows, then apply” instead of adding pages.

The owner keeps the two strongest worksheet pages, adds noindex to the other seven, and removes them from the sitemap (112 → 105 URLs). He rewrites the short Contact, Terms and Cookie pages in his own words, then rescans. The template family disappears from the report, and the remaining work is a list of specific rows — not a vague “add more content”.

4. How to apply, step by step

  1. Run a pre-apply check. Use the AdSense Readiness Checker and fix every row marked Add content, Merge or Noindex. The method section explains how each number is counted.
  2. Add your site in AdSense. Sign in, open Sites, and add the root domain you control.
  3. Place only the code Google asks for. Add the verification snippet, ads.txt line or meta tag exactly as shown, on the page or file AdSense names. Do not add extra ad units yet.
  4. Request review once. The status will show Getting ready while Google checks the site.
  5. Wait. Do not send a second review while one is running, and do not remove the verification code.
  6. Never click your own ads — not to test them, and not by asking friends. Invalid clicks can close an account permanently.

Common mistakes

  • Publishing fifty new pages the week before applying, all written from one template.
  • Copying a privacy policy from another site without changing the name, email or cookie list.
  • Leaving “Advertisement” placeholders, test ad units or lorem ipsum on live pages.
  • Requesting a new review the same day as a rejection, without changing anything the message named.
  • Blocking Googlebot or the AdSense crawler in robots.txt, or hiding the site behind a login or challenge page.

If you see “Needs attention”

Open the Sites page and read the exact reason. For low-value content, go back to section 2 and fix the patterns, not just one page. For policy issues, read the linked policy and remove the problem content. Then wait for Google to recrawl — usually a few days — and request one new review.

5. After approval

Only now turn ads on. Start with Auto ads or a few manual units on your strongest pages, and publish the ads.txt line AdSense gives you. Set up the consent message for visitors from the EEA, UK and Switzerland under Privacy & messaging. Keep thin template copies out of the sitemap, and run the readiness check again before you add a new section of pages.

Read next

Website SEO audit checklist · How to get your pages indexed by Google · Open the AdSense Readiness Checker →

Sources: AdSense Program policies · Google Search Essentials. This guide summarises; it does not quote them.

Frequently asked questions

Google does not publish a minimum. What matters is that every indexed page is useful on its own. A small tool site with 15 to 25 strong pages is a normal starting point. If you already have dozens of thin pages, improve or noindex them before you add more. Never create pages just to reach a number.
No. The checker is a pre-apply review. It reads your public pages and lists problems that often lead to a low-value content message, such as thin pages, copied templates or missing policy pages. Only Google decides whether a site is approved, and no outside tool can promise or predict that decision.
If many pages share one template and less than 40 percent of their text is unique, noindex the copies and keep one strong page in the sitemap. Rewriting forty near-identical pages in a day rarely makes them genuinely different. Rewrite a copy only when you can give it its own purpose, examples and answers.
It varies. Many reviews finish within a few days, and some take two weeks or longer while the status shows Getting ready. Do not remove the verification code or request a second review while the first one is running. If nothing changes for a long time, check the Sites page in AdSense for messages.
Before approval this message is normal and does not block the review. After approval, AdSense shows the exact line to publish. Create a plain text file named ads.txt in your site root with that line, so it opens at yourdomain.com/ads.txt. The status can take a few days to update after you add it.
Yes, new sites are approved regularly, but a very new or very small site is more likely to see Needs attention. Give the site original pages that answer real questions, clear About, Contact and Privacy pages, and some time to be crawled. Fix what the review message names, then request one new review.