Monthly SEO maintenance checklist.

Use the same date length and note seasonality, campaigns, outages, and reporting delays before calling a movement meaningful.

Look for lost or gained impressions and clicks on queries tied to real services, products, or qualified demand.

Separate one-page movement from a sitewide pattern, then check whether the page or its internal links changed.

Compare the displayed result and query intent before changing a title or description; low CTR is a clue, not a diagnosis.

Verify leads, calls, purchases, or other business outcomes in the analytics and systems your team actually trusts.

Record releases, migrations, content edits, promotions, outages, and measurement changes without claiming timing proves causation.

Investigate new security, manual-action, indexing, enhancement, or ownership notices before routine optimization work.

Look for new reasons important URLs are excluded. Use URL Inspection for representative pages instead of expecting every excluded URL to be a problem.

Sample the homepage and important templates or revenue pages, especially after a release or when an indexing pattern changes.

Confirm the sitemap is readable and contains preferred canonical URLs, then investigate sampled redirects, errors, noindex pages, or canonical conflicts.

Check the production host for an unexpected sitewide block and confirm declared sitemap locations still resolve.

Prioritize failures reached by users, internal links, backlinks, sitemaps, or search results rather than treating every historic URL equally.

Confirm each important URL reaches the intended destination without an avoidable chain, loop, error, or unrelated final page.

Look for new noindex or conflicting crawler directives in both the HTML and response headers.

Verify one valid preferred URL per page and investigate missing, duplicate, off-domain, staging, HTTP, or mismatched targets.

Catch missing, duplicated, placeholder, or materially rewritten fields. Judge wording by page purpose rather than a universal character count.

Validate parseable schema against visible content and confirm important Open Graph or Twitter-card fields still point to the intended values.

Repair confirmed internal failures and distinguish missing alt attributes from intentionally empty alt text on decorative images.

Identify what shipped, which pages or templates it could affect, and whether the public response matches the intended release.

Check whether the page still satisfies its query, remains factually current, has useful internal links, and supports the intended conversion.

Use field data where available and investigate persistent template-level LCP, INP, or CLS problems instead of chasing one lab run.

Submit the form, place the test call, or complete the safe checkout path and confirm the destination, notification, and measurement event.

Record the affected URL or template, before and after state, approver, release date, validation, rollback plan, and expected measurement window.

Give every material finding an owner, priority, due date, and evidence required to close it. Leave low-value noise out of the plan.