“Site not ready” can refer to different kinds of blockers. Google’s site-not-ready guide groups common causes that include a site that cannot be reached, missing or incomplete ad code, policy issues, and insufficient unique content or user experience. Start by reading the exact status in AdSense, then classify the issue before changing anything.
If it is an access problem, open the submitted domain while logged out and check redirects, password protection, and server errors. If it is code or setup, follow the instructions shown for the site in your AdSense account and verify the code is on the intended version. If it is policy, open Policy Center and review the specific notice. If it concerns content or experience, inspect representative pages for unique usefulness, completeness, and navigation. These categories can overlap, so keep a repair log instead of assuming one fix resolves everything.
Example: A publisher can open the site, but Google’s account still reports that the site is not ready. The owner should check whether the correct domain was submitted, whether the required connection step is completed, and whether the account gives a more specific issue. “I can see it in my browser” proves public access from that browser; it does not prove every account step is complete.
Run SiteReadyScore to organize public checks such as loading, links, and page signals. Use the finding to identify what to inspect, then return to AdSense for private setup or policy status. The scan cannot submit a review or see the private account.