Google’s instructions for a site that was not ready fit in 2 steps: fix what is wrong, then request another review. They set no waiting period between the 2, which leaves the question that matters unanswered: how long before the site is different enough for a second review to end differently? We use 3 weeks. That figure is our recommendation, not Google’s.
What Google says, and where the 3 weeks come from
The help page for a site that is not ready names 4 causes, each with a fix. The ad code is missing or incomplete: check that it sits in the head of the right site, or verify ownership through Search Console. The site cannot be reached: the URL must be correct and published, password protection removed, the SSL certificate valid with HTTP redirecting to HTTPS, and robots.txt must not block the AdSense crawler. There is not enough unique, useful content, or the experience is poor. Or the site breaks program policies, which you resolve in the policy center. After the fix you ask for a new review, and Google says a review usually takes a few days but can take 2 to 4 weeks.
The official text stops there. It does not say which page was at fault, and it does not say how long to wait before asking again. The 3 weeks are ours, and they rest on one measurement. On our own site, then 3 months old, Googlebot made 57 requests between 23 September and 7 October 2026, 37 of them for robots.txt, and read only 3 distinct pages. Your site may be crawled faster, but the lesson holds: you cannot assume a fix has been seen within a few days. Google does not say how a review relates to its crawling, so we wait until Search Console shows the changed pages as crawled before asking.
The plan at a glance
| Week | Goal | What you do | You are done when |
|---|---|---|---|
| 1 | Diagnose | Read the message, test code, access, robots.txt and indexing, then give every URL a verdict | You can name which of Google’s 4 causes applies, in one sentence, and every page has a verdict |
| 2 | Fix | Remove technical blockers first, then merge, enrich or delete pages, then write what is missing | Every verdict is applied and the checker shows nothing red that you can fix |
| 3 | Publish and verify | Publish the remaining pages at a steady pace, inspect the key URLs in Search Console, re-run the checks, read the site as a stranger | Key pages show as crawled and indexed, and the exit checklist below is all yes |
Day 21 is the earliest day we would ask for the review. If the checks are not all green by then, ask later.
Week 1: find the cause before you touch anything
Changing the site before you know why it was refused can bury the evidence and fix the wrong thing. Work through the rejection reasons in this order, which puts the cheap, binary checks first.
- Code. In your AdSense account, confirm that the ad code or the ownership verification is in place on the exact site you applied with.
- Access. Open the site in a private window with no login. It must load without a password, with a valid certificate, and plain http must redirect to https.
- Robots. Test your file with the robots.txt tester for both Googlebot and Mediapartners-Google, the AdSense crawler.
- Indexing. In Search Console, compare the number of indexed pages with the number you think exist, and look for a
noindexleft over from staging. - Content. Run the sitemap script from our guide to finding low value content and give each URL a verdict: keep, enrich, merge, noindex or delete.
Run the AdSense checker on your homepage at the same time. It covers the measurable part of steps 2 to 4 in one report, and its score is a baseline to beat in week 3. If you cannot finish the sentence “we were refused because…”, week 1 is not over.
Weeks 2 and 3: fix, publish, verify
In week 2, order the work by cost. Technical blockers come first because they are binary and quick: the code, the redirect, the robots rule, the stray noindex. Then apply the page verdicts, merging with 301 redirects where several pages cover one topic. Then write what is missing, starting with the pages that show a person stands behind the site, covered in important pages for AdSense approval. Leave the design alone: none of Google’s 4 causes is about colors or fonts.
Be honest about the count. Our recommendation in the requirements checklist is 20 to 30 indexed pages that each deserve to exist without ads. If your inventory shows 8, 3 weeks will not get you to 25 good ones, and padding is worse than waiting. Extend the plan. Publish at a pace you could sustain, a few substantial pages a week rather than 30 in a day; we publish this site in waves for the same reason.
In week 3, verify instead of hoping. Use URL Inspection in Search Console on the homepage and every page you changed: it shows whether the page is indexed, when Google last crawled it and which canonical Google chose. Resubmit your sitemap, knowing that it is only a hint. Re-run the checker and compare with week 1. Then read the site as a stranger on a phone: the homepage, 3 random articles and every footer page. When the checks pass, ask for the review. If Google has not recrawled your fixes yet, a few more days cost nothing, while a refusal costs you another wait of days or weeks. Once you have asked, keep publishing normally and see how long approval takes.
What not to do
Do not ask again the same day. Nothing a reviewer can read has changed, so we expect the same answer. You would be sending the same site to the same review.
Do not make cosmetic changes. A new theme, a new logo and a reworded About page address none of the 4 causes Google lists. They feel like progress and change nothing a reviewer weighs.
Do not delete everything. A reviewer needs something to read, and deleting indexed URLs without redirects creates a trail of 404s. Remove the pages that serve nobody and improve the rest.
Do not change domain by reflex. A new domain restarts discovery and indexing, and Google does not say how long that takes. If the cause was content, the same content moves with you. Change domains only for a reason tied to the domain itself.
Do not fill the site with generated filler to reach a page count. Google lists auto-generated content that nobody reviewed or curated among the problems, and says that generating content in bulk with automation to manipulate rankings violates its spam policies. A smaller site of pages someone read beats a larger one that nobody did.
Exit checklist
Ask for the review only when each line is true.
- The ad code or ownership verification is in place on the right site.
- The site loads in a private window, with a valid certificate and http redirecting to https.
robots.txtallows Googlebot and the AdSense crawler.- Every URL in the sitemap answers 200, and none carries a
noindexyou did not intend. - Every page in your inventory has had its verdict applied: kept, enriched, merged, noindexed or deleted.
- The privacy policy, contact, about and terms pages exist, are linked from the footer and can be indexed.
- No “coming soon” pages, placeholder text or empty archives remain.
- Search Console shows your key pages as crawled and indexed after your changes.
- You have read the homepage and 3 random articles on a phone, as a stranger would.
