A site may load for its owner but fail from another location, browser, or domain version. Test http and https, with and without www, and any domain you recently moved. Record the final URL, response behavior, and whether the route reaches the intended public page. Look for loops, expired certificates, temporary maintenance screens, and redirects to a different site.
Google’s site-not-ready guide includes unreachable sites among common setup problems. Google’s site connection instructions explain the account’s connection and review process. Use the exact site shown in AdSense as your reference; do not assume that a redirect makes every verification or ownership step equivalent.
Example: The user submits example.com, but the site redirects to www.example.com; a CDN rule then redirects the www address back to the apex domain only for some paths. Test the homepage and article URLs from a logged-out session, correct the conflicting rule, and retest across the same variants.
After a domain migration, update internal links, canonical settings, sitemaps, and Search Console properties as appropriate. Keep old-domain redirects only when they take visitors to the equivalent destination. A redirect to the homepage for every removed URL can be confusing and may hide the missing page rather than solve it.
Use SiteReadyScore to surface public reachability signals and URLs to verify. Confirm redirects independently in a browser and use the AdSense account for its private site status. A scan from one location cannot prove universal access from all networks.