A quarterly review can catch changes that accumulate between applications or account checks. Start with the AdSense account: read site status, Policy Center notices, and ads.txt status. Then verify the public site: open the homepage, representative article types, contact and privacy pages, and any high-traffic landing pages. Test menus, forms, redirects, and mobile layouts. Review the current Google policy pages rather than relying on an old printed checklist.
Update content that contains changed prices, policies, screenshots, or recommendations. Check image and video permissions. Review new user comments and outbound links. If you changed plugins, themes, hosting, or domain routing, verify that the public version still loads and that important functions work.
Google’s site status article explains account-side status checks; the page-readiness guidance covers useful content and navigation; and the ads.txt guide explains seller-file checks. Use these sources for the specific steps relevant to your site.
Run SiteReadyScore at the start of the review to collect public signals and again after substantial repairs. Keep dated reports and track which findings were confirmed or dismissed. A scan complements the account and human review; it does not replace them.
Quarterly log: Date; account notices; pages sampled; source updates; verified defects; changes; retest results; remaining questions.