Ad code installation and site approval are separate steps. The code may be present while Google still reviews the site, or the site may need another account task. Follow the exact instructions shown in AdSense and make sure the code appears on the intended production domain. If using a plugin or theme integration, confirm it is active on public pages and has not been removed by a cache, staging migration, or theme change.
Google’s site connection page describes the connection process and notes that the entire site is reviewed for compliance. Its not-ready guide includes missing or incomplete ad code among possible setup problems. Seeing code in the page source is not the same as seeing “Ready” status in the account.
Example: A WordPress plugin inserts the code on posts but not on a custom landing page, while AdSense is reviewing the custom page as part of the site. Confirm the integration’s scope and account instructions. Do not paste duplicate scripts into multiple theme files without knowing the effect.
Use SiteReadyScore for public technical checks and a page inventory, then verify AdSense setup directly in the account. The scan cannot validate your publisher account or request the review. If code is updated, inspect the public source and follow Google’s own status page.