Content
78%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.
The body is a lean, well-sequenced audit workflow with genuinely concrete specifics (title pattern, 300-word threshold, exact schema properties) and an appropriately split one-level reference verified to exist. The only notable weakness is mild duplication of the doorway-page rationale between the intro and Quick Reference.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is tight and imperative ('Create individual pages for each city/region served', 'at least 300 words of unique content'), but the doorway-page warning is stated twice — in the intro ('thin, templated location pages are penalised by Google as doorway pages') and again in a Quick Reference bullet ('Avoid creating identical pages per location... (doorway pages)'). This matches 'Efficient; minor instances of over-explanation that could be trimmed'; not 5 because of that duplication, not 3 because there is no substantive padding. | 4 / 5 |
Actionability | Concrete, specific guidance: 'unique title targeting `[Service] in [City]`', 'LocalBusiness schema with `areaServed`', 'Flag pages that appear to be thin templated clones'. Matches 'Mostly executable guidance... with minor gaps'; not 5 because copy-paste material (the JSON-LD markup example, URL structure) is deferred to the reference rather than inline, not 3 because there is no pseudocode or missing key detail. | 4 / 5 |
Workflow Clarity | A clear Check -> Fix -> Explain -> Code Review sequence with checkpoints ('Verify each page has unique content beyond just swapping city names', 'describe how to verify the final page output'). Matches 'Clear sequence with most checkpoints present; minor validation gaps'; not 5 because the explicit validation steps themselves live in references/rule.md, not in the body. | 4 / 5 |
Progressive Disclosure | The ~35-line body is a well-organized overview (Quick Reference, Check, Fix, Explain, Code Review) that defers detail through a clearly signaled, verified one-level-deep reference ('see `references/rule.md`' — a real file holding the code example, per-page checklist, URL structure, and verification steps). Matches 'Clear overview with well-signaled one-level-deep references; content appropriately split; easy navigation'. | 5 / 5 |
Total | 17 / 20 Passed |