Technical readiness begins with access. Open the site from a logged-out browser, test the canonical domain and HTTPS, and make sure important pages are not blocked by a maintenance screen, password gate, or redirect loop. Check that your site ownership or verification method is complete and that the AdSense code or other required connection step is in place as your account instructs. The precise workflow may vary, so use the Sites page in AdSense as the source of truth.
Google’s “site not ready to show ads” guide describes common setup problems including an unreachable site, missing or incomplete ad code, policy issues, and insufficient unique content or user experience. Google’s site status guide explains where to check review and ads.txt status. A visible website alone does not prove that account setup is complete.
Keep a dated preflight log: submitted domain; preferred HTTPS version; page loads; redirect behavior; robots or access issues; verification status; ad-code status; and account status. If the site recently moved hosts or changed domains, verify that the version submitted in AdSense resolves to the version visitors use. Avoid repeated submissions while a listed prerequisite remains unresolved.
Example: http://example.com redirects to https://www.example.com, but AdSense lists the non-www version and ownership verification was added only to the www property. Confirm the exact submitted site and follow the verification steps that the account shows rather than assuming the redirect automatically completes every setup requirement.
SiteReadyScore can check a range of public signals and help you spot URLs worth testing. Use it as one part of preflight; it cannot complete account verification, inspect private setup tasks, or decide that Google is ready to serve ads.