What 'Requires Review' Means in AdSense Sites

Requires review on the AdSense Sites list means Google has not started the site check yet—not that your account was rejected, not that ads are broken today, and not the same as Getting ready after checks begin. Beginners stare at the label and either panic-apply again or delete the site to “reset” a clock that never started.

Status neighbors: AdSense Getting ready vs under review (full label map), AdSense review time (wait clock after review starts), Add a new site after approval (add → verify → review steps), and Connected sites vs account status (account approved while one URL still waits). This page is not the approval checklist and not rejected: what to fix.

Requires review = site not checked yet. Finish homepage tasks, verify ownership, click Request review once, then expect Getting ready while Google runs checks.

Official: Check the status of your AdSense sites · Connect your site to AdSense · Add a new site

Disclosure: Educational AdSense status guide only. No earnings, RPM, or approval guarantees. Confirm labels in live Help—UI changes.

Table of contents

1. Where Requires review sits in the lifecycle
2. Official meaning from Google Help
3. Requires review vs Getting ready vs Ready
4. Requires review vs Needs attention
5. Account layer vs site layer
6. What to finish before Request review
7. What happens after you click Request review
8. Adding a second site while another is Ready
9. Actions that delay review
10. FAQ
11. Request once, then read the next label

Where Requires review sits in the lifecycle

Think of site approval as a short sequence of labels on the Sites page—not a single “AdSense approved” light for every URL you will ever publish.

Before checks: Requires review — you have added the site (or Google listed it during apply), but the formal site review has not run yet.

During checks: Getting ready — you requested review; Google is evaluating ownership, content, and policy fit for that hostname.

After success: Ready — that site may show ads when code, ads.txt, and policies are in order.

Repair state: Needs attention — Google flagged fixable issues before ads can serve; not a pure wait.

Requires review is the front door of that sequence for a site row. Nothing is “stuck” in a mysterious pending timer if you never finished homepage tasks or never clicked Request review.

If I were helping someone read their Sites list for the first time, I would have them write the exact string next to the URL before opening any checklist post—half of forum panic is colloquial “pending” language that does not match the live label.

Official meaning from Google Help

Google’s Check the status of your AdSense sites article defines Requires review roughly as: the site has not been checked yet; finish the tasks on your AdSense homepage, then click Request review.

Connect-site Help adds context: if you request review without completing required setup, the site may stay in Getting ready while Google waits for you to finish tasks—another reason to complete homepage items before you poke review.

Help also warns not to remove your site and resubmit because that can delay review. Requires review is not an invitation to delete the row and re-add the URL tomorrow.

This article paraphrases Help only. When your live UI shows a string Help does not list, trust Google’s in-product explanation and refreshed Help—not a blog synonym.

Requires review vs Getting ready vs Ready

Requires review is pre-flight. Getting ready is in-flight. Treating them as the same word causes duplicate Request review clicks or remove-and-add cycles that Help explicitly discourages.

Colloquial “under review” emails often map to Getting ready, not Requires review. Translate email language to the Sites string using Getting ready vs under review.

Requires review vs Needs attention

Both labels can frighten new publishers, but the job differs.

Requires review assumes setup is incomplete or review was never requested—normal on a freshly added hostname.

Needs attention means Google wants fixes before the site can show ads—policy, connectivity, or readiness problems named in Help’s “site not ready” paths.

If Needs attention appears, do not apply the Requires review playbook (“just wait”). Open the repair guidance linked from that status. Requires review pages like this one are the wrong tool once Needs attention is showing.

Account layer vs site layer

Your publisher account can be approved while a connected site still shows Requires review—common when you add domain two after domain one is Ready.

Account questions: payments profile, program-level policy, identity tasks on the homepage.

Site questions: is this hostname verified, reviewed, and Ready on the Sites list?

Deep map: Connected sites vs account status. Requires review almost always belongs to the site column, not “my AdSense account is broken.”

What to finish before Request review

Google points you to homepage tasks before review—not a blog-invented post count.

Typical prep (confirm live UI the day you act):

1. Payments and account tasks shown on the AdSense homepage.
2. Site ownership verification on Sites—code snippet, ads.txt line, meta tag, or platform connect path documented in Help.
3. Live, crawlable content on the URL you added—not a placeholder domain.
4. Policy-safe basics your site actually needs (about/contact/privacy where appropriate for your model)—without copying a checklist post line-for-line here.

First-time apply depth stays on the approval checklist owner. This page assumes you are reading a Requires review row, not starting from zero applicants.

For site-two clicks: Add a new site after approval owns add → verify → review sequencing.

What happens after you click Request review

After a proper request, Help describes checks that usually take a few days and can take 2–4 weeks in some cases. The Sites label typically moves from Requires review to Getting ready while those checks run.

During Getting ready:

• Do not remove the site to restart.
• Confirm verification stays live (snippet not stripped by a theme update).
• Read duration guidance on review time / pending instead of refreshing hourly.

When the label becomes Ready, placement and blank-ad troubleshooting move to serving guides—not back to Requires review.

If Google sends a clear account or site rejection, switch to the rejected owner. Requires review is not a soft rejection label.

Adding a second site while another is Ready

Scenario: blogA.com is Ready and earning. You add blogB.com; it shows Requires review.

That is normal site-layer behavior. Account approval does not auto-Ready every future domain. Walk site B through verify → Request review → Getting ready → Ready while site A keeps serving—provided policies and placement stay healthy on both.

Do not copy site A’s ad code onto site B and assume Ready propagates. Each hostname has its own Sites row and approval column.

Actions that delay review

Google’s Help repeatedly warns against remove and resubmit games. Other self-inflicted delays:

• Requesting review before homepage tasks are done—may prolong Getting ready.
• Verification that disappears after a theme push—crawlers cannot confirm ownership.
• Adding the same URL repeatedly under slightly different hostnames (www vs bare) without a plan.
• Treating Requires review as rejection and rewriting the entire site daily instead of finishing setup once.

Patience belongs to Getting ready, not Requires review. On Requires review, the productive action is finish tasks and request once.

FAQ

See frontmatter for schema. Label comparisons stay unique vs Getting ready and rejected owners—no duplicated “Is this the checklist?” blocks across cluster posts.

Request once, then read the next label

Requires review means the site check has not started yet. Finish AdSense homepage tasks, keep ownership verification live, click Request review once, and watch for Getting ready while Google runs site checks. Account approval, rejection repair, and ad blank traces live on their own owners—this URL only decodes the Requires review row so you act on the right layer at the right time.