Monthly SEO Checklist

Use this for: The selected draft or published page being reviewed.

Open the previous review’s action list and visit the affected live pages. Check each item’s original completion condition instead of accepting a status label alone. Separate not started, blocked, published and retested work. Give unfinished items a concrete next step or deliberately cancel them when they no longer matter. Do not silently carry the same vague task forward every month.

1. Review the previous commitments.
2. Test the specific live change.
3. Close, reassign or explicitly defer unfinished work.

Use this for: The selected draft or published page being reviewed.

In Search Console’s Performance report, select a completed period and a suitable comparison. Keep search type, country, device and page scope consistent. Calendar months differ in length; use equal-length windows when daily comparability matters and review seasonal periods when relevant. Check whether the newest data is incomplete or a reporting anomaly affects the observation before diagnosing a decline.

1. Choose a completed reporting window.
2. Apply the same relevant filters to both periods.
3. Check data completeness and seasonal context.

Use this for: The selected draft or published page being reviewed.

Review clicks and impressions in Search Console, then compare the Pages and Queries tables. Filter the pages with material changes to see which searches changed. Use device or country breakdowns when they reveal a pattern. Average position and CTR are diagnostic measures, not universal grades; changing query mix can alter both without a single page edit causing it.

1. Find material gains and losses.
2. Open the affected page and query segments.
3. Write the specific pattern that needs explanation.

Use this for: The selected draft or published page being reviewed.

In GA4, open Reports → Engagement → Landing page, or find that report in your property’s navigation. Filter or compare by Session default channel group = Organic Search, then review the relevant pages and configured key events. Keep sessions and Search Console clicks separate. If outcomes suddenly disappear, test the expected action with the analytics owner before assuming SEO quality collapsed. Use a test environment or agreed test mode; stop before creating an unintended purchase, booking or lead submission.

1. Review relevant organic landing pages.
2. Compare useful configured outcomes.
3. Investigate form or measurement changes when the pattern suggests them.

Use this for: The selected draft or published page being reviewed.

For a sustained change, compare its timing with releases, content edits and known seasonal patterns. Inspect affected pages and Search Console findings before assigning a cause. Use Google Trends for relative topic interest when it has usable data, and review official search-status or reporting notices when relevant. A coincident update is context, not proof that it caused the change.

1. Compare the timing with site changes and seasonality.
2. Inspect representative affected pages.
3. Choose investigate demand, content, tracking or technical cause.

Use this for: The selected draft or published page being reviewed.

Review the list of URLs published, moved or materially changed since the previous check. In Search Console’s Page indexing report, look for relevant new patterns, then use URL Inspection on representative affected pages. Distinguish an intended exclusion from a problem. Use the live test to verify current access and the indexed record for Google’s stored state; the two can differ.

1. List changed URLs and templates.
2. Review relevant indexing reasons and sample URLs.
3. Assign a confirmed shared cause to its technical owner.

Use this for: The selected draft or published page being reviewed.

Use the release list to choose affected templates and visitor actions. Open representative pages on desktop and a narrow screen. Test navigation, main content and the business action in an agreed test mode, stopping before any unintended purchase, booking or lead submission. Inspect rendering or performance when the release creates a relevant risk. Route a repeated failure to the component owner. A monthly review should target changed or problematic areas, not assume every page needs a full technical audit.

1. Identify changed templates and critical actions.
2. Test representative live paths.
3. Escalate reproducible shared failures with the affected scope.

Use this for: The selected draft or published page being reviewed.

Review priority pages against actual changes in products, services, policies and recurring audience questions. Correct obsolete instructions, examples and claims in the CMS. Use the existing URL when its purpose remains the same. A changed date is the result of a substantive update, not the update itself. Leave accurate pages alone when no useful change is needed.

1. Identify facts or needs that changed.
2. Update the affected passages and examples.
3. Have the responsible owner verify the revision.

Use this for: The selected draft or published page being reviewed.

Review the month’s new and changed URLs for durable incoming links and accurate destinations. Open their source pages and update links that still point to an old or removed answer. Check category or archive placement for new content. Use a broader internal-link audit only when recurring missing paths or template issues justify it.

1. Review new and changed URLs.
2. Find and correct affected source links.
3. Verify durable navigation to important new content.

Use this for: The selected draft or published page being reviewed.

Turn confirmed issues into specific actions and rank them by reader consequence, business relevance, confidence and available effort. Put blockers before dependent improvements. Assign an accountable owner and a completion test to each active item. A small completed batch is more useful than automatically commissioning new articles or links to meet a monthly quota.

1. Translate the strongest findings into bounded actions.
2. Order them by consequence and dependencies.
3. Assign owners and fit the batch to capacity.

Use this for: The selected draft or published page being reviewed.

When an action ships, repeat its original acceptance check on the live site. Verify a corrected link, form, instruction or indexing rule directly. Evaluate search or business impact later using the relevant comparison and enough data for a useful interpretation. Do not label an edit successful only because total clicks rose, or failed because the next day was quiet.

1. Repeat the specific live completion test.
2. Confirm the relevant owner accepts the fix.
3. Schedule a suitable later outcome review where useful.

Use this for: The selected draft or published page being reviewed.

Summarize what changed, what you think explains it, what was fixed and what remains uncertain. List only the decisions and active actions needed by the responsible people. Choose the next review timing based on site activity and risk. Escalate urgent failures immediately rather than waiting for the next monthly meeting. Notes in this checklist remain optional; use the team’s normal task system if it already works.

1. Summarize observations and decisions.
2. Share clear actions with their responsible owners through the normal workflow.
3. Choose the next appropriate review point.