Monthly Technical-Health Check (SOP)

Purpose

Technical faults silently erode visibility and cap every other effort, so a fixed monthly cadence catches regressions early. This SOP keeps the foundation trustworthy before content and authority work is layered on top.

When & who

Trigger

Start of each calendar month, or immediately after a deployment, migration or CMS change.

Frequency

Monthly

Roles

SEO lead, Technical SEO specialist, Web developer

Procedure

1. 1
   Pull the coverage report

   Review Google Search Console Page Indexing for new 'Not indexed' reasons and compare the indexed count against last month's baseline.

2. 2
   Audit crawlability

   Run a full crawl to surface broken links, redirect chains, 5xx errors and orphaned pages, and check robots.txt has not changed unexpectedly.

3. 3
   Validate rendering and speed

   Spot-check key templates for render-blocking issues and confirm Core Web Vitals remain within the 'Good' threshold in the field data.

4. 4
   Check indexability signals

   Verify canonical tags, meta-robots directives and XML sitemap accuracy on priority templates to ensure nothing is inadvertently excluded.

5. 5
   Review structured data

   Confirm schema still validates and no new markup errors or warnings have appeared in the Rich Results report.

6. 6
   Log and triage findings

   Record every fault against the Priority Matrix, assign owners and due dates, and flag anything blocking indexation as urgent.

7. 7
   Verify last month's fixes

   Confirm previously raised issues have been resolved and have not regressed before closing the cycle.

Tools

• Google Search Console
• Screaming Frog
• SearchScore Tracker
• PageSpeed Insights