Complete AdSense Site Review Checklist Before Applying

The AdSense site review checklist is the final quality-control process you should complete before clicking Request review in Google AdSense. A successful review is not based on one magic number of posts or a premium WordPress theme. Instead, Google reviews the entire submitted site for ownership, original content, policy compliance, technical accessibility, and a usable visitor experience. Therefore, you should audit the whole website rather than fixing only the homepage.

This guide turns those broad requirements into a practical, repeatable review. You will check account details, content quality, navigation, trust pages, privacy disclosures, technical access, AdSense connection code, traffic quality, mobile usability, and common rejection risks. In addition, the final sections explain current site statuses, what to do when a site is not ready, and how to submit the review without creating unnecessary delays.

This article belongs to the Google AdSense guides hub, the AdSense approval learning path, and the approval requirements cluster. Use those pages when you need the wider sequence rather than only the final audit.

Quick Answer: What Should You Review Before Applying?

Before applying, confirm that you control the domain, the website is fully launched, the content is original and useful, the navigation works, required privacy disclosures are accurate, the whole site follows Google Publisher Policies, and Google can access the live pages. Then connect the site through an accepted verification method, complete the account tasks shown in AdSense, and request review only after the checks are finished.

Google states that it reviews the entire site. Its current help pages also identify common readiness problems such as missing or incomplete code, an unreachable website, insufficient unique content, weak user experience, and policy violations. Consequently, the strongest approach is to treat approval as a full-site audit instead of a single-page inspection.

AdSense Site Review Checklist at a Glance

The table is a summary, not a substitute for the detailed audit below. For a broader preparation sequence, also follow the step-by-step approval checklist for new blogs. This page focuses specifically on the last review before submission.

AdSense Site Review Checklist: Account, Domain, and Ownership

Use accurate account information

Start the AdSense site review checklist with the account, because inconsistent information can create verification or payment problems later. Use the real legal name of the responsible account holder, the correct country or territory, and a postal address that can receive official communication. Do not create an identity only to match a website brand.

The AdSense account holder must be at least 18 years old. When a publisher is younger, a parent or legal guardian may use the adult’s own Google Account and legal information. In that situation, Google makes payments to the approved adult account holder.

Submit the correct website URL

Enter the standard domain you actually control. Check the spelling, HTTPS version, redirect behavior, and preferred hostname before submitting it. A wrong domain, temporary staging address, broken redirect, or inaccessible subdomain can prevent verification and waste the review period.

Open the submitted domain in a private browser window and on a mobile connection. The preferred version should load without an administrator session, password prompt, maintenance screen, or repeated redirect. In addition, important posts should remain available through normal navigation.

Confirm that you can modify the site

Google needs evidence that you own the site or can modify its content. Current connection methods can include an AdSense code snippet, an ads.txt code snippet, a meta tag, or a supported platform workflow. Therefore, confirm that you can edit the site header, root ads.txt file, or relevant platform settings before starting.

For WordPress, decide which single method will manage the connection. You might use an appropriate plugin, theme integration, manual header placement, or another supported setup. Avoid adding the same AdSense code through several tools because duplication makes troubleshooting harder.

Phase 2: Audit Whether the Website Is Fully Built

Remove unfinished and placeholder content

A site under construction is not ready for review. Remove lorem ipsum, sample posts, demo products, default theme pages, empty author archives, test forms, and sections labelled “coming soon.” Likewise, delete or complete draft-like pages that are publicly accessible but offer little information.

Check the header, homepage, footer, category archives, author pages, search results, pagination, contact form, and 404 page. Although not every design detail must be perfect, the website should look like a complete publication rather than a template waiting for content.

Make the site purpose clear

A reviewer and a first-time visitor should quickly understand the audience, main topics, and reason the site exists. The homepage, category structure, About page, and recent articles should support the same editorial direction. If one section covers careers, another publishes unrelated celebrity news, and a third contains thin product pages, the site may appear unfocused.

A clear purpose does not require an extremely narrow niche. However, related content should be organized into understandable categories and clusters. This structure also helps visitors discover useful next steps instead of leaving after one page.

Check every public template

Review more than individual posts. WordPress can generate tag archives, category pages, date archives, attachment pages, author archives, search results, and pagination. Some templates may contain duplicate headings, blank descriptions, broken layouts, or almost no content.

Decide which archives genuinely help users. Improve valuable archives and consider appropriate indexing controls for low-value duplicates, but do not make broad technical changes without understanding their effect. The immediate review goal is to prevent public sections from looking abandoned, deceptive, or broken.

AdSense Site Review Checklist for Original Content Quality

Check whether each important page adds real value

Google’s eligibility guidance emphasizes unique and interesting content. Therefore, each main article should answer a clear question, explain the important details, and provide a reason to choose your page over a copied or generic summary. Value can come from original examples, local context, tested steps, screenshots, calculations, comparisons, templates, or careful synthesis from reliable sources.

Do not judge quality only by word count. A 1,000-word article can be complete, while a 4,000-word article can repeat the same point. During the audit, remove filler, improve vague sections, define technical terms, and add missing practical guidance. The goal is usefulness, not artificial length.

Remove copied, scraped, and lightly rewritten material

Copied content creates copyright, trust, and approval risks. Search several distinctive sentences from your articles and check whether they match another source too closely. Also review imported product descriptions, press releases, job listings, quotations, and translated pages.

A translation or paraphrase does not automatically become original simply because the wording changed. Add independent value, verify the facts, credit sources when appropriate, and avoid presenting another publisher’s work as your own. When content cannot be improved responsibly, remove or consolidate it.

Apply editorial review to AI-assisted content

AI tools can support planning, drafting, grammar, or data organization, but the publisher remains responsible for the final page. Check names, dates, formulas, policy claims, statistics, links, and examples. Remove invented details, unsupported certainty, repetitive wording, and generic advice that does not help the intended reader.

Add human judgement where it matters. For example, explain why a recommendation fits a specific audience, identify limitations, distinguish official requirements from practical suggestions, and update claims that may change. This editorial layer makes the content more reliable and more useful.

Review high-impact claims carefully

Money, tax, legal, health, safety, and employment topics can affect important decisions. Use strong sources, qualify estimates, explain uncertainty, and avoid guarantees. If you publish AdSense earnings examples, label them as hypothetical or historical rather than promising that every reader will receive the same CPC, RPM, or income.

Correct outdated claims before applying. A site that repeatedly presents old thresholds, discontinued product features, or unsupported “new rules” can lose reader trust even when the writing appears polished.

AdSense Site Review Checklist for Navigation and User Experience

Create a predictable primary menu

The main menu should lead to the website’s important sections without overwhelming visitors. Use descriptive labels rather than vague items such as “More” or “Stuff.” On mobile, verify that the menu opens, closes, scrolls, and returns users to the page correctly.

A visitor should be able to reach the homepage, main categories, About page, Contact page, and essential policy pages through normal links. Important information should not exist only in a sitemap or a hidden footer widget.

Fix broken and misleading links

Click representative internal links from the homepage, menus, category pages, articles, and footer. Fix 404 errors, redirect loops, mixed HTTP links, malformed URLs, and links that point to staging domains. Also update anchor text that promises one destination but opens another.

Internal links should help readers continue their journey. For example, this final review naturally connects to the guide on website requirements before applying and the explanation of important trust and policy pages. Contextual links are more useful than placing dozens of unrelated URLs in one block.

Check readability on real devices

Use short paragraphs, meaningful headings, readable font sizes, sufficient spacing, and tables that reflow or scroll on small screens. Avoid forcing users to zoom. In addition, make sure sticky elements do not cover headings, buttons, consent controls, or the article text.

Review color contrast, keyboard focus, form labels, link visibility, and image alternative text. Accessibility improvements help a wider audience and often reveal design problems that also frustrate other visitors.

Control pop-ups and intrusive elements

Newsletter forms, cookie notices, app banners, social prompts, and promotional overlays can combine into an unusable first visit. Test the page in a fresh browser where every message appears. Users should be able to read the content and close optional overlays without hunting for hidden controls.

An ad-ready site should prioritize content before monetization pressure. Therefore, remove deceptive buttons, fake notifications, forced redirects, and download controls that resemble advertisements.

Phase 5: Check Important Pages, Privacy, and Transparency

Publish an accurate Privacy Policy

Your Privacy Policy should describe the data and technologies actually used on the site. Depending on the setup, that may include analytics, advertising cookies, identifiers, comments, forms, embedded content, newsletters, and third-party services. Avoid copying a template without adapting it to the real website.

Google’s publisher policies require relevant privacy disclosures for data collection, sharing, and ad-serving technologies. Regional consent duties can also apply based on the visitor, not only the publisher’s location. Therefore, review the current requirements and obtain qualified advice when necessary.

Make ownership and contact information understandable

An About page should explain who operates the publication, what it covers, and how the content is created. A Contact page should provide a working method for legitimate questions, corrections, or business communication. Test the contact form from another email address and check the spam folder for the result.

Terms, disclaimers, affiliate disclosures, earnings disclaimers, editorial policies, correction policies, and author pages may also improve transparency when they match the website. However, do not describe every optional trust page as a universal Google approval requirement. Accuracy is stronger than an exaggerated checklist.

Link trust pages visibly

Place key pages in a clear footer or another consistent location. Do not hide them behind JavaScript that fails to load or inside a menu available only to logged-in users. Review each link in desktop and mobile views.

Phase 6: Complete a Publisher Policy Audit

Review the whole domain, not only new posts

Google reviews the entire site, so old content can affect the result. Audit posts, pages, media, comments, downloads, embedded videos, external links, user profiles, and public uploads. A policy issue does not become harmless because it appears in an old article with little traffic.

Use Google’s current Publisher Policies and restrictions as the controlling source. Policies can change, so do not depend only on a checklist written years ago. Where a topic is uncertain, remove the risky implementation or seek authoritative guidance before applying.

Moderate user-generated content

Comments, forums, classified listings, and public profiles can introduce spam, prohibited material, scams, copied text, or unsafe links. Set moderation rules, remove problematic submissions, and close abandoned features that you cannot supervise.

The publisher remains responsible for monetized pages even when another user created the material. Consequently, a large community feature needs stronger moderation than a small blog with comments disabled.

Avoid deceptive monetization patterns

Do not ask visitors to click ads, describe ad clicks as support for the site, or create layouts that cause accidental interaction. Navigation, download buttons, image controls, and calls to action should remain clearly distinguishable from advertising.

During this pre-approval review, remove fake play buttons, misleading system alerts, forced click paths, and pages whose primary purpose is sending users through ads or redirects. A sustainable site serves readers first.

AdSense Site Review Checklist for Technical Access

Confirm the site is live and reachable

Open the website from different networks and devices. Check that the server responds consistently, HTTPS works, the certificate is valid, and the site does not show maintenance, firewall, or rate-limit errors. If a security service challenges every new visitor, Google may also struggle to reach the pages.

Google’s connection guidance specifically warns about unreachable sites and login protection. Therefore, the public site should be accessible without a password during the review. Private member pages can follow separate crawler-login procedures after activation when appropriate.

Review robots.txt and security rules

Make sure robots.txt, firewall rules, CDN settings, security plugins, and server configurations do not block the AdSense crawler or verification resources. A blanket bot block may protect against abuse but also prevent legitimate review access.

Check the live robots.txt file rather than only the WordPress editor. Also review recent security logs for blocked Google requests, repeated 403 responses, or country restrictions that might interfere with the review.

Check response codes and redirects

Important pages should normally return a successful response. Fix server errors, soft 404 pages, redirect chains, loops, and inconsistent canonical destinations. Although a perfect technical SEO audit is not a stated approval formula, severe access problems can stop Google and users from evaluating the content.

Keep the preferred domain consistent

Choose one HTTPS hostname and redirect alternatives consistently. Internal links, canonical tags, sitemaps, and navigation should point to the preferred version. This reduces confusion when AdSense verifies the submitted domain.

Phase 8: Connect the Website to AdSense Correctly

Choose one supported verification method

Current AdSense instructions can offer an AdSense code snippet, ads.txt code snippet, meta tag, or a platform-specific connection method. Follow the options shown inside your own account because the available workflow can vary.

When using the AdSense code snippet, Google instructs publishers to place it between the <head> and </head> tags. Publish the change and verify it in the live page source rather than assuming a caching plugin applied it.

Place code on a real content page

Google notes that long activation delays often occur when the code is not on a page receiving regular views. Do not use an empty test page that exists only for the code. The connection should appear on the live site that Google is being asked to review.

Avoid duplicate code installations

WordPress publishers sometimes add code through a theme, a header plugin, Site Kit, another advertising plugin, and a tag manager at the same time. Inspect the live source and keep a single intentional implementation. Duplicate code can create confusing diagnostics and maintenance problems.

Complete every account task before submission

The Sites page may show the website as Requires review until you complete the required tasks and request a review. AdSense can also require payments information or other account setup steps before the site review begins. Follow the task list displayed in your account rather than relying on a screenshot from another publisher.

Phase 9: Audit Traffic Quality Before Monetization

Identify every major traffic source

Review analytics, server logs, referral reports, and recent campaigns. You should be able to explain where visitors come from and why they visit. Organic search, direct visits, genuine referrals, newsletters, and responsible social promotion can all be legitimate when the traffic reflects real interest.

Stop suspicious and incentivized traffic

Remove click exchanges, paid-to-click schemes, bot packages, forced redirects, pop-under networks, misleading push campaigns, and offers that reward people for viewing or clicking ads. A spike in low-quality sessions is not evidence that the website is ready.

Also examine unexpected countries, extremely short sessions, repeated identical behavior, and referrals from unknown domains. Not every unusual pattern is invalid, but investigate before connecting advertising.

Do not test ads by clicking them

After approval, never click your own live ads or ask friends, staff, readers, or contractors to click. Use approved preview and diagnostic tools. Build this rule into your operating process before the first advertisement appears.

Phase 10: Test Mobile Usability and Performance

Run a real-phone review

Open the homepage, several long articles, tables, forms, category pages, and the footer on a real phone. Test portrait and landscape views. Check font size, spacing, menu behavior, table overflow, image width, sticky bars, cookie notices, and form fields.

Mobile problems often hide inside one template rather than the whole theme. For example, a comparison table may overflow, an author box may push text off-screen, or a floating share button may cover the consent controls. Fix the specific pattern before applying.

Reduce avoidable performance problems

Compress oversized images, remove abandoned plugins, control third-party scripts, and prevent unnecessary layout shifts. A fast score is not a published AdSense approval threshold, but slow and unstable pages create a poor user experience and may become worse after ads are added.

Keep enough space for media and embedded elements so the layout does not jump during loading. In addition, test the site while logged out because administrator sessions may bypass caching or hide scripts.

The Complete 35-Point AdSense Site Review Checklist

Use the following AdSense site review checklist as the final pass. Mark an item complete only after checking the live website.

1. Confirm that the responsible account holder is at least 18 years old.
2. Use the correct legal name, country, and postal address.
3. Submit the exact standard domain that you control.
4. Confirm that HTTPS and the preferred hostname load correctly.
5. Open the site without an administrator login or password.
6. Remove maintenance mode, staging banners, and unfinished sections.
7. Delete lorem ipsum, demo posts, sample products, and template pages.
8. Make the website purpose and audience clear.
9. Review all public categories, tags, archives, and author pages.
10. Publish original, useful, audience-focused content.
11. Remove copied, scraped, spun, or minimally rewritten pages.
12. Fact-check AI-assisted drafts and time-sensitive claims.
13. Label examples, estimates, and earnings scenarios accurately.
14. Fix broken internal and external links.
15. Test the main menu and footer on desktop and mobile.
16. Make important content reachable through normal navigation.
17. Publish an accurate Privacy Policy.
18. Provide understandable About and Contact information.
19. Add relevant terms, disclaimers, disclosures, or editorial pages.
20. Test forms and verify that messages are received.
21. Review the entire domain against current Publisher Policies.
22. Moderate or remove risky user-generated content.
23. Remove deceptive buttons, forced redirects, and accidental-click layouts.
24. Investigate suspicious traffic and stop incentivized campaigns.
25. Confirm that the server responds reliably from different networks.
26. Check that robots.txt and security tools do not block Google.
27. Fix important 404s, server errors, redirect loops, and access failures.
28. Review mobile text, spacing, tables, overlays, and sticky elements.
29. Reduce unnecessary scripts, oversized images, and layout shifts.
30. Choose one supported AdSense verification method.
31. Publish the code, meta tag, ads.txt entry, or platform setting correctly.
32. Verify the connection in the live page source or account workflow.
33. Complete required payments and account setup tasks shown by AdSense.
34. Run the broader new-blog approval audit.
35. Request review once, then avoid removing and resubmitting the site unnecessarily.

WordPress AdSense Site Review Checklist

Check Site Health and plugin conflicts

Review WordPress Site Health for critical errors, HTTPS problems, failed scheduled events, and outdated software. Update carefully, create a backup, and confirm the site still works after changes. Do not perform a major theme migration immediately before requesting review unless the current site is unusable.

Inspect the live page source

Open the public homepage, view its source, and search for your AdSense publisher ID or the chosen verification meta tag. Confirm that the code appears in the correct site and is not inserted repeatedly. Clear page caches, CDN caches, and optimization caches when necessary.

Review visibility settings

Check that WordPress is not discouraging search engines through a forgotten staging setting. Also review maintenance plugins, coming-soon plugins, password protection, firewall challenges, and noindex rules. The site must be accessible for review.

Test themes, menus, widgets, and forms while logged out

Administrators often see a different version because of caching, editing bars, or role-based content. Use a private browser window to test menus, widgets, author boxes, cookie controls, forms, links, and footer pages exactly as a visitor sees them.

Understanding Current AdSense Site Statuses

Google currently says the review usually takes a few days, although some cases can take two to four weeks. Do not treat that range as a guaranteed deadline. Connection problems, incomplete account tasks, access failures, or required fixes can extend the process.

Google also advises publishers not to remove and resubmit a site merely because the review is taking time, since that can delay the process. Instead, keep the connection active, confirm the site remains accessible, and watch the Sites page and account notifications.

What to Do When the Site Is Not Ready

Read the stated issue before changing everything

A “not ready” result should lead to diagnosis, not random redesign. Open the site details and identify whether the problem relates to code, reachability, content, user experience, or policy. Save the message and review the affected areas across the whole domain.

Make meaningful fixes

If the issue is unique content, adding one short post is unlikely to solve a site-wide quality problem. Improve or remove weak pages, strengthen the editorial focus, fix navigation, and finish incomplete sections. Likewise, a reachability problem requires technical verification rather than more articles.

Request another review only after validation

Test the live site again after changes. Check page source, response codes, robots rules, mobile behavior, menus, and the exact issue Google reported. Then request another review through the Sites page when the website is genuinely ready.

For wider recovery guidance, read the relevant rejection or account-status article in the approval cluster. The goal is to fix the underlying cause rather than repeat the same submission.

Common AdSense Site Review Mistakes

• Applying during development: the public site still contains demo content, blank sections, or broken templates.
• Optimizing only the homepage: old posts, archives, comments, and downloads still contain problems.
• Counting posts instead of reviewing quality: the site reaches an arbitrary number but offers thin or duplicated content.
• Using generic trust-page templates: the Privacy or About page does not describe the real website.
• Blocking the crawler: security tools, robots rules, or login protection prevent access.
• Installing code several times: multiple plugins and theme settings create duplicate connection scripts.
• Buying traffic before approval: low-quality sessions create risk without improving the site.
• Submitting repeatedly: the publisher requests another review without fixing the stated problem.
• Making major changes during review: URLs, themes, or code are removed while Google is checking the site.
• Treating approval as permanent: the publisher stops monitoring policy, content, traffic, and user experience after acceptance.

A Seven-Day Pre-Application Review Plan

The seven-day schedule is an organizational example, not a Google requirement. A small site may finish sooner, while a large or neglected site may need several weeks. Quality and validation matter more than the calendar.

AdSense Site Review Checklist: Frequently Asked Questions

What does Google check during an AdSense site review?

Google reviews the entire submitted site for compliance with AdSense Program policies. Its current readiness guidance highlights site connection, reachability, unique content, user experience, and policy issues. Publishers should also complete the required account tasks shown in AdSense.

How many posts should I publish before requesting review?

Google does not publish one guaranteed post count for every standard website. Publish enough original, complete content to make the site’s purpose clear and provide a useful experience. Ten strong articles are not an automatic approval formula, and fifty thin articles do not guarantee acceptance.

Does my site need traffic before the AdSense review?

There is no universal published traffic threshold for a standard website application. However, genuine visitors can expose broken navigation, weak pages, and mobile problems. Do not buy bots or incentivized traffic to make the site appear active.

Should I add AdSense code before approval?

Follow the connection instructions shown in your AdSense account. Google currently asks publishers to connect and verify the site before requesting review, using an available method such as the AdSense code snippet, ads.txt code, meta tag, or supported platform setup.

Where should the AdSense code snippet go?

Google’s current connection instructions say to place the AdSense code snippet in the page HTML between the opening and closing head tags. WordPress users should use one reliable implementation and confirm the published code in the live source.

How long does the site review take?

Google currently says reviews usually take a few days, but some can take two to four weeks. The duration is not guaranteed. Incomplete tasks, missing code, crawler blocks, or other access problems can delay the process.

Should I remove and resubmit a site when the review is slow?

Google advises against removing and resubmitting simply because the review is taking time, since that can create more delay. Keep the site connected, accessible, and compliant while monitoring the account.

Are About, Contact, and Terms pages mandatory for every site?

An accurate Privacy Policy has direct importance for advertising and data-use disclosures. About, Contact, Terms, Disclaimer, Editorial Policy, and similar pages generally support transparency and trust, but publishers should not claim that every optional page independently guarantees approval.

What should I do after passing the review?

Set up ads carefully, keep content readable, monitor traffic quality, review the Policy center, and continue updating the website. Approval confirms that the site passed the review at that time; it does not remove the publisher’s ongoing responsibility.

Final Review and Next Step

A strong AdSense site review checklist protects you from avoidable delays. Confirm ownership, finish the website, improve original content, make navigation clear, publish accurate privacy and trust information, audit the entire domain for policy risks, verify crawler access, connect the site correctly, and investigate traffic before requesting review.

After every item is validated on the live website, continue with the practical guide on how to apply for Google AdSense. That article should cover the account and submission workflow, while this page remains the final site-readiness audit.

Official Google Sources

• Google AdSense Help: Eligibility requirements for AdSense
• Google AdSense Help: Connect your site to AdSense
• Google AdSense Help: What to do when your site is not ready to show ads
• Google AdSense Help: Check the status of your AdSense sites
• Google AdSense Help: AdSense site management
• Google AdSense Help: Your AdSense account was not approved

Important: This checklist explains current Google guidance and practical publishing checks. AdSense approval is not guaranteed, and Google may update policies, interfaces, connection methods, or review procedures. Always verify the tasks and messages shown inside your own AdSense account before submitting.