Content
75%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A well-structured, actionable audit procedure that sequences discovery, structural validation, URL reality cross-check, and reporting into clear phases with concrete acceptance criteria. The main gaps are minor: a touch of motivational padding and no explicit fetch-failure/error-recovery feedback loop.
Suggestions
Trim the two-sentence motivation paragraph after the role framing — the value is already implicit in the phased checks and it adds tokens without new guidance.
Add a brief fetch-failure handling note in Phase 3 (e.g., retry/timeouts, how to treat unreachable URLs in the bucketed table) to turn the batch URL cross-check into an explicit feedback loop.
Specify the 'representative sample if large' rule with a concrete sampling heuristic (e.g., sample N per sitemap or per URL-pattern bucket) so the action is repeatable rather than left to judgment.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Lean and assumes Claude's SEO competence — no padding about what a sitemap is — but the two-sentence motivation paragraph ('A sitemap full of redirects... Both are common; both are fixable.') and the attribution line are minor tokens that could be trimmed; sits above the 'mostly efficient' anchor at 3. | 4 / 5 |
Actionability | Concrete, specific guidance throughout — 'Fetch robots.txt and read every Sitemap: directive', '≤ 50,000 URLs and ≤ 50 MB', per-bucket actions like 'list the canonical instead' — with only minor gaps (no exact fetch commands, sampling strategy left as 'a representative sample if large'). | 4 / 5 |
Workflow Clarity | Clear phased sequence (Step 0 → Phase 0-4) with structural validation built into Phase 2 and a bucketed cross-check in Phase 3; the destructive/batch cap does not apply since this is a read-only audit, but it lacks an explicit error-recovery feedback loop that would reach 5. | 4 / 5 |
Progressive Disclosure | Well-organized into clearly delineated phases with a single one-level-deep, clearly signaled external reference ('Read and follow ../shared/preamble.md'); no bundle files exist, and the self-contained guidance is appropriately structured rather than monolithic. | 4 / 5 |
Total | 16 / 20 Passed |