AdSense site readiness: what you can verify before review

AdSense approval is Google's decision and no checklist can guarantee it. What a publisher can control is whether the website is technically reachable, clearly structured and correctly connected to the intended publisher account.

Make the site reliably reachable

Before review, verify that the primary domain loads over HTTPS without certificate warnings, DNS errors or authentication. The live site should be the same site you submitted.

Confirm the publisher code

The AdSense loader should contain the publisher ID from the account being used. Avoid leaving stale publisher code from another account unless the configuration is intentional.

Check ads.txt independently

If Google provides an ads.txt line, publish it at the root—for example https://example.com/ads.txt—and open the public URL yourself.

Do not submit an empty shell

A functioning website needs more than verification code. Navigation, real content or functionality, clear purpose and trust information should all be present.

Keep the conclusion accurate

A technical audit can find missing code, inaccessible files or accidental indexing problems. It cannot predict Google's final approval decision.

Review the site as a visitor, not only as the owner

Open the site in a private browser window and navigate from the homepage without using bookmarks or admin shortcuts. A visitor should be able to understand the site's purpose, find the main content or tool, reach supporting pages and move back to the homepage without encountering unfinished sections.

This manual pass catches a class of problems that code checks cannot: unclear navigation, placeholder copy, empty categories, misleading buttons, broken forms and pages that technically return HTTP 200 but are not useful.

Keep account verification separate from site quality

Ownership verification answers a narrow question: can the publisher prove control of the site? A working AdSense script, meta tag or other supported verification method does not by itself establish that the site is ready for advertising. Treat verification and site review as separate gates.

Check consistency across the domain

Confirm that the canonical hostname, HTTPS version, navigation links and ads.txt location all refer to the same production site. Fresh domains sometimes work on one hostname while another still points elsewhere. That creates confusing signals for visitors and automated review systems.

After requesting review

Keep the production site stable. Fix genuine bugs, security issues and broken pages, but avoid repeatedly deleting the site, changing domains or replacing the entire information architecture without a reason. A stable, reachable site is easier to evaluate than a moving target.

A practical pre-review sequence

1. Verify the production domain and HTTPS.
2. Check the intended AdSense publisher ID in page source.
3. Open ads.txt directly and compare it with the line provided by the account.
4. Test navigation, contact information and important content in a private browser.
5. Confirm robots.txt, sitemap and indexability are intentional.
6. Submit the site only after those checks are stable.