The client-proof workflow → Client reports

Turning Index Checks Into Client-Proof Reports

The moment a client questions a retainer, the argument is won or lost on evidence quality. "We monitor indexing" loses. A dated file with 2,400 rows, each carrying a verdict, wins — because nobody argues with line items.

What the report contains, in order

1. One headline number. Percent of scope indexed, next to last month's figure. This is the sentence the client repeats internally, so put it first and make it exact.
2. The three piles. Blocked (with the fix owner named), clean-but-skipped (with the resubmission date), written off (with the reason and, for links, the vendor). Counts, not adjectives.
3. The movement section. What left the "not indexed" pile since the last report and why. This is the part that justifies the invoice.
4. The appendix. The raw per-URL file from the bulk index checker — indexed and not-indexed lists, dated. Ten clients in a row won't open it. The eleventh will, and that's the meeting the appendix exists for.

Why per-URL beats screenshots

A screenshot documents one query at one moment. Search Console's URL Inspection tool is the deepest single-URL evidence there is — and even it covers one URL per click, on properties the agency may not have access to during onboarding. A batch verdict file scales the same evidence to the whole scope and needs no property access at all, which also makes it the only clean way to report on backlink placements sitting on domains nobody controls.

The two report mistakes that create disputes

• Reporting "delivered" instead of "verified". For link building, the number that belongs in the report is placements verified in the index — resubmissions in progress get their own line, via drip-feed indexing when batches need pacing.
• Reporting one month in isolation. A single percent invites "is that good?". A three-point trend answers it before it's asked.