AdSense Site Not Ready: Low Value Content Fix Order

If AdSense told you your site is not ready to show ads, or that your content is low value or insufficient, fix things in this order: read the exact message, work out which of the three kinds of rejection you have, cut or merge the pages that give a reader nothing, repair navigation and ownership signals, add depth only where a reader question is still unanswered, and then request a new review. Adding new posts first is the most common wasted effort, because it leaves the pages that triggered the message untouched.

This guide is for owners of blogs, hobby sites and early-stage publications who have been turned down and want a sequence they can follow. It covers how to read the message, how to see your site the way a reviewer's crawler does, what to do about thin and templated pages, which navigation and ownership signals to check, what to cut, merge or expand, and how to approach a new review. For the general method of finding weak pages, the article on thin content and how to fix it is a good companion.

There is no approval guarantee here, and no magic post count. Google's help pages do not state a minimum number of articles or words, so this guide does not invent one.

Reading the exact rejection message

Two different AdSense help pages describe two different situations, and the fix depends on which one you are in. Many publishers lump them together as "I was rejected." Separating them first saves weeks.

Situation one: the site is not ready to show ads

Google's page on a site that is not ready to show ads lists four causes. The ad code may be missing or incomplete, the site may be unreachable, the site may lack enough unique content or offer a weak user experience, or there may be policy violations. The page says a site should provide enough valuable content to users before it is monetized, and it advises improving content depth and originality and making navigation clear. It also gives the review steps: sign in to AdSense, open Sites, pick the site, confirm the code is on it, and click Request review. Reviews usually take a few days but can take two to four weeks. All of this is on the Google help page (Opens in a new tab).

Notice how much of that list is technical. If the code is outside the head tags, if the crawler is blocked by robots.txt, or if HTTPS has an invalid certificate, writing more articles changes nothing.

Situation two: the account was not approved

The help page on an account that was not approved separates a duplicate account from problems with the site itself. AdSense allows one account per publisher. On the site side it names insufficient content, content quality, policy violations, navigation problems, problematic traffic sources and an unsupported language. It also says publishers whose accounts were terminated for invalid traffic or policy violations cannot open new accounts. Read the full list on the account not approved page (Opens in a new tab).

Situation three: a policy problem in your account

A policy-based rejection is about what your pages are, not how many exist. Under its behavioral rules, Google's publisher policies bar Google-served ads on screens that have no publisher content or only low-value content, and on screens that are under construction or exist for alerts, navigation or similar behavioral purposes. The policy page (Opens in a new tab) is the authority on exact wording.

Keep a log from day one

Save the message with its date and write each stated reason on its own line. Next to each reason, record what you checked and what you changed, with dates. A log keeps you from fixing imagined problems and gives you something to compare when the next message arrives. If the message shows only one reason, do not invent others; work on that one first.

Thin and templated pages Google can see

A reviewer and a crawler see every address your site exposes, not only the posts you are proud of. The gap between the pages you think you have and the pages that exist is where rejections often hide.

Count addresses, not articles

List every crawlable address: the sitemap, category pages, tag pages, author archives, paginated archives, attachment pages for images, internal search result pages and any leftover test pages. A site with forty good articles can still expose hundreds of addresses that carry no text of their own. If the ad code or the review reaches those pages, they weigh on the verdict.

On its page about unapproved accounts, Google tells publishers to make sure pages have enough text and that the site is finished rather than "under construction." It adds that ad code should not sit on an empty test page, that auto-generated pages or pages with little original content should be avoided, and that affiliate content should be only a minor part of the site unless it adds value.

A triage table

Questions for each page

Open the page cold and ask three questions. Would a stranger who landed here get an answer? Does another page on the site already say the same thing? Is there anything here that exists only because a template generated it? A yes to the last question, or a no to the first, marks the page for action.

Working with a spreadsheet

Use one row per address with columns for page type, title, rough length, stand-alone value, overlap with another page, decision, action taken and date. Sort by length to find the shortest pages quickly, but treat length as a sorting aid and not a verdict. A short page that fully answers a narrow question can stay. Fill the sheet in three passes: list, review, decide. Deciding in the same pass as listing makes people rush.

• Every address listed from the sitemap, archives and internal search.
• Every blank, draft and placeholder page removed.
• Near-duplicate posts merged with a redirect from the old address.
• Tag and archive pages reviewed.
• Menu, footer and related-post links updated after removals.
• Sitemap refreshed.

Navigation, policy pages and ownership signals

Reviewers also behave like visitors. They look at the homepage, click through the menu, open an article and try to understand who runs the site and why. This section is the visitor's checklist.

Navigation problems named by Google

The unapproved-account page lists navigation issues explicitly: redirects, broken links, pages behind logins, excessive pop-ups and unfinished pages. Test each as a visitor would. Can you reach every main section from the homepage in a couple of clicks? Does every menu link work? Does the mobile menu open and close? Does a pop-up cover the article before the reader can start?

A frequent trap on new sites is a menu item for a section that is not built yet. It is both a navigation problem and a blank page. Take it out of the menu until it has real content.

Access checks

The not-ready page tells publishers to make sure AdSense can open the site without a login, that robots.txt is not blocking the AdSense crawler, and that HTTPS uses a valid certificate from a recognized authority with HTTP redirecting to HTTPS. If you would rather not edit your code, you can verify ownership through Search Console instead. Run these checks once and note the result.

About, contact and privacy pages

Google's help pages do not list an about page, a contact page or a privacy policy as a separate reason for rejection, and the help text contains no such requirement. They are still reasonable signals that a real person or organization runs the site, and the publisher policies do cover privacy matters such as personalized advertising, privacy disclosures and cookies. If your site uses ads and cookies, read that part of the policies rather than assume your current page is enough.

An author page helps readers judge who is speaking. The guide on building an author page for E-E-A-T shows what to include.

• The about page says what the site covers, for whom, and who is behind it.
• The contact page offers a working route, such as a form or an address that is read.
• The privacy page matches how the site actually handles data and ads.
• Each article shows its author and links to an author page.
• Publication dates, and update dates where relevant, are visible.

Ads near navigation

The policies also say Google-served ads may not overlay or sit next to navigational or other action items where they could lead to unintended clicks, and may not appear on dead-end screens a user cannot leave without clicking the ad. When you place ad code, test the page on a phone with your thumb, not only in a desktop browser.

What to cut, merge or expand

This is the step where most people overreact. The goal is not a smaller site or a bigger site. It is a site where each address earns its place.

A decision rule for each page

Ask whether this address, on its own, answers a reader's question. If not, and another page covers the same topic, merge. If not, and the topic is outside what the site is about, remove it. If partly, and the topic is central to the site, expand. If yes, leave it. Expanding every weak page just produces longer weak pages.

What depth means

Google's help pages give no word count, so depth cannot be measured by length. In a 2017 post on AdSense insufficient content, Google's Ad Traffic Quality Team wrote that reviewers and the crawler need enough text to understand what a page is about, that sites with little text, or mostly images, video or Flash, can be rejected, and that template-only sites with little original material are at risk. The post, dated March 1, 2017, urges publishers to think about what makes their pages distinct and to create original and relevant content that keeps users engaged. It is an older source and does not replace the current help pages, but its logic still helps. You can read it on the Google blog (Opens in a new tab).

A useful page usually has a clear reader question, something only you can add (a method you used, a measurement you took, a mistake you made), a next step for the reader, dates and sources where claims need them, and no filler. The helpful content guidelines and quality scoring table gives you a scoring grid to apply across your archive.

Do not make these moves

• Padding posts by repeating the same point.
• Copying text from other sites or generating pages in bulk.
• Adding the same generic paragraph to every post.
• Publishing hundreds of short posts in a day.
• Filling posts with affiliate links and little information.

Redirects and cleanups

After a merge, redirect the old address to the merged post, update internal links to the new address and refresh the sitemap. When you delete a page that has no close equivalent, send its address to the nearest relevant page instead of leaving a broken link, since broken links count as navigation problems on Google's list.

Topic focus

A site that touches fifty topics with a short post each often looks weaker than one that goes deep on three. Choose your core topics, check which reader questions each one still leaves open, and write for those gaps. Posts outside the core are candidates to rewrite for the core or to remove.

How a reviewer might walk your site

Picture the review as a short visit. The reviewer opens the homepage and sees whether the site looks finished. They open two or three articles to see whether the text is original and complete. They follow the menu to check that sections exist and links work. They look for signs of who runs the site. They may also open pages you rarely visit yourself, such as an old tag page. The unapproved-account page says reviewers may check all pages, not just the sign-up page, so assume any public address can be seen.

That is why a final spot check matters. Before you request a review, pick five addresses at random from different parts of the site, including an archive and an old post, and ask the same questions of each: does it open, does it carry enough original text, does the menu work, is the author shown, is anything blank? Random selection protects you from only checking the pages you know are good.

Reapply timeline and what not to do

Once the work is done, the request itself is simple. What matters is not asking too early.

The checklist

1. The rejection message is saved with its date and every reason is logged.
2. There is no duplicate account.
3. The ad code is on the right site, inside the head tags, and the site opens without a login.
4. robots.txt does not block the AdSense crawler and HTTPS works with a valid certificate.
5. The address inventory is done and blank, stub and duplicate pages are handled.
6. Tag and archive pages are reviewed.
7. Every menu link works and unfinished sections are gone.
8. About, contact, privacy and author information are in place.
9. There is no open violation in the Policy center.
10. Traffic comes from natural sources, not paid-to-click programs or unwanted email.
11. The site language is supported.
12. You request the review from Sites in your account.

A six-week order of work

This is a sequence, not a promise. Week one: save the message, check access and list addresses. Weeks two and three: remove, merge and redirect, then fix the menu. Week four: complete ownership and policy pages. Week five: expand or rewrite the few posts that sit at the center of your topic. Week six: run the checklist end to end and only then request the review.

Timing and restraint

Reviews usually take a few days and sometimes two to four weeks. During that window avoid large structural changes, because it becomes hard to know what the reviewer saw. Do not open a second account as the same publisher, since the unapproved-account page treats a duplicate as a reason for rejection. Do not paste your ad code into sites unrelated to your application.

Example scenario: two sites, one message

A hypothetical example:

Site A is a travel notes blog. Its posts are strong, but it exposes a tag page for every place name, each a bare list. It also has two menu entries for sections that are still empty. The fix order is: remove the empty menu entries, noindex or introduce the tag pages, then recheck access. Writing more posts would not touch either problem.

Site B is a coupon aggregator. Most pages are short lists with only the store name changed. This site has a content problem, not a navigation one. The fix is to decide which handful of topics it can cover with original information, and to cut the templated pages that add nothing. Reapplying quickly would likely repeat the result.

Both sites got the same type of message, and the correct first move was different. That is why the log and the triage table come before any writing.

Conclusion

Fix an AdSense low value content or not-ready rejection in sequence: identify which kind of message you have, verify technical access, inventory every address and triage thin, duplicate and blank pages, repair navigation and ownership signals, expand only what answers a real reader question, then run the checklist and request a review. There is no published post count and no guarantee, but doing the steps in order stops you from spending a review request on a site that still carries the original problem.

If you need to build or rewrite core posts to the standard above, you can look at our content writing service.

Frequently Asked Questions

What should I do first after an AdSense low value content rejection?

Save the message with its date and decide which type it is: site not ready, account not approved or a policy issue. Then verify technical access, inventory every crawlable address and deal with thin, duplicate and blank pages. New posts come after those steps.

How many posts do I need to get approved?

Google's help pages do not state a minimum number of posts or words. What they stress is enough original text on each page, a finished site and working navigation. Judge your pages by whether each answers a reader question.

Do tag and archive pages count against me?

Google tells publishers to avoid auto-generated pages and pages with little original content. Tag and archive pages that are only link lists can look that way. Adding a real introduction or keeping them out of the index are reasonable choices.

How long should I wait before I reapply?

The help pages give no minimum waiting period. Reviews usually take a few days and can take two to four weeks. The better test is whether you have fixed the stated reason and completed the checklist.

Are an about page and a privacy policy enough to pass?

No. They are useful ownership signals, but the help pages do not list them as a separate reason for rejection. Content, navigation and policy compliance carry the decision.

Should I write new posts or fix old ones first?

Fix old ones first. Blank, duplicate and stub pages keep weighing on the site until you remove, merge or expand them. After that, add posts that answer reader questions in your core topics.

Is Google's 2017 post on insufficient content still valid?

It is dated March 1, 2017 and does not replace the current help pages. Its core idea, that a site needs enough original text and a distinct purpose, still guides the work, but check current rules on the help pages and publisher policies.