The client-proof workflow → Monthly monitoring

The Monthly Index Health Check for Retainer Clients

Deindexation is rarely loud. Pages leave the index quietly, traffic erodes over a quarter, and by the time the client asks, the story has no clean start date. The monthly health check exists to own that start date — and it fits in an hour per client.

The one-hour routine

1. Run the standing samples (15 min). The per-template URL sets defined in the sampling methodology go through a batch index check. Same URLs every month; the output is a delta, not a discovery.
2. Cross-check Search Console (15 min). The Page Indexing report's bucket sizes get logged next to the sample results — the report's documentation is clear that data lags and examples are capped, so it corroborates trends rather than replacing per-URL checks.
3. Check the fresh batch (10 min). Whatever shipped last month — new pages, new links — gets its day-28 verification. Clean misses go back through resubmission; stubborn ones through manual reindexing.
4. Log three numbers (5 min). Percent indexed per money-template, count of URLs that left the index, count recovered. Straight into the client report.
5. Escalate or close (15 min). Anything beyond thresholds becomes an incident with an owner; everything else closes until next month.

Escalation thresholds that work in practice

• Any money-template sample dropping sharply in one cycle — treat as an incident, run a full check of that template the same day.
• Two consecutive small declines in the same template — not noise anymore; inspect the template's recent deploys and content changes.
• Fresh-content indexation stalling while old pages hold — a discovery and crawl-priority problem, different fix path from a quality problem.

Why this beats reactive audits

A reactive audit starts from "traffic fell" and works backward through a quarter of possible causes. The monthly log starts from "pagination sample dropped on March's check" and works forward from a known date, a known template, and a shortlist of deploys. Same tools — a fraction of the diagnostic surface. Retainers keep clients when incidents come with start dates.