After you add a website to AdSense, the most useful information is the status shown inside your own account. It tells you whether Google is still preparing or reviewing the site, whether action is needed, or whether the site is ready for the next stage.
Status labels and account screens can change, so this guide explains the practical meaning behind the workflow rather than pretending that every account will display identical wording.
Where to check your site status
Sign in to AdSense and open the Sites section associated with your publisher account. Select the website you submitted and read the current status and any accompanying message.
If Google has identified a specific problem, the message in the account should take priority over generic advice from blogs or videos.
What the common statuses mean
| Status or message | Practical interpretation |
|---|---|
| Getting ready / preparing | Google is processing the site and preparing it for review or the next step. |
| Ready | The site has reached the relevant AdSense readiness state shown by Google; follow the account's next instructions. |
| Needs attention | Something in the account or site requires action before the process can continue. |
| Not ready | The site has not met the requirements for the current review stage; read the reason shown in the account. |
Do not diagnose from the status label alone
A label such as “Not ready” is a starting point, not a complete diagnosis. Open the associated details. Google may identify a site-quality, policy, technical or setup issue.
For example, a site can have excellent content and still have a technical connection problem. Conversely, a technically perfect site can still have content or policy issues.
If your site is still being reviewed
Keep the production site stable. Continue fixing genuine problems you discover, but do not repeatedly make unrelated changes simply because the status has not changed yet.
Avoid changing domains, restructuring the whole website or adding a large amount of low-value content solely because you are waiting for a status update.
If your site needs attention
Read the message and make a targeted checklist. If Google identifies a missing setup step, complete that step. If the issue concerns the site itself, investigate the affected pages.
After making a change, verify the public page while logged out. This catches a common development mistake where the administrator sees a working page but visitors—or Google's systems—receive something different.
If your site is not ready
Do not treat “not ready” as a signal to publish random articles. Inspect the fundamentals:
- Does the site provide useful original content?
- Are the important pages complete?
- Can visitors navigate between related resources?
- Do the tools and forms work?
- Can Google access the pages it needs to review?
- Does the site comply with current Publisher Policies?
- Are the relevant privacy and consent requirements addressed?
Keep evidence of what you changed
For a larger site, maintain a small review log. Record the date, the status, the message, affected URLs and the fix you made. This prevents repeated work and makes it easier to determine whether a later change actually addressed the problem.
Do status changes happen immediately?
Not necessarily. Crawling, processing and account updates can take time. If Google tells you that an update or review is still in progress, give the process time rather than repeatedly submitting the same information.
Status checklist
- □ Check the status inside your AdSense account.
- □ Read the full message, not only the label.
- □ Identify whether the issue is technical, content, policy or account-related.
- □ Fix the underlying issue.
- □ Test the public site while logged out.
- □ Recheck the account after Google's systems have had time to process the change.
Quick answer
Check the Sites section of your AdSense account to see your current site status and read the detailed message attached to it. Treat the status as a diagnostic signal, not a complete explanation. If the site is not ready or needs attention, identify whether the underlying issue is content, policy, technical accessibility or account setup and fix that specific problem.