Content
57%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 well-structured, brief overview with excellent progressive disclosure to a real one-level reference file. Its weaknesses are the lack of executable verification steps and the malformed escaped-HTML snippet in the Fix section, plus mild padding that re-explains known SEO concepts.
Suggestions
Replace the escaped entities in the Fix section with the actual tag so the snippet is usable: Remove `<meta name="robots" content="noindex">` from pages that should be indexed.
Add concrete verification commands to the Check or Code Review section, e.g. `curl -sI <url> | grep -i x-robots-tag` for header directives and inspecting the rendered DOM for `<meta name="robots">`.
Cut the intro sentence explaining what noindex does and merge the 'Check' section with the Quick Reference bullets to remove duplication, and surface the reference file's Verification steps explicitly.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly lean at ~30 lines, but the intro ('An incorrect `noindex` tag can completely remove important pages from search results...') explains SEO concepts Claude already knows, and the 'Check' section largely restates the Quick Reference bullets. Not 4 because of this duplicated/padded content; not 2 because most sections are tight. | 3 / 5 |
Actionability | Names concrete artifacts ('the `noindex` directive in meta tags or headers', 'rendered HTML', 'response headers', 'routes or templates') and a concrete fix, but no executable commands are given, and the Fix line shows escaped entities ('Remove the <meta name="robots" content="noindex">') instead of the actual tag. Not 4 because the guidance is incomplete and the one snippet is malformed; not 2 because specific directives and their locations are named. | 3 / 5 |
Workflow Clarity | Check -> Fix -> Explain -> Code Review provides a rough sequence, but the steps are descriptions rather than ordered instructions, and there are no verification checkpoints in the body — the verification guidance lives in references/rule.md and is not surfaced. Not 4 because checkpoints are missing or implicit. | 3 / 5 |
Progressive Disclosure | A lean overview body with a clearly signaled, one-level-deep reference ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md' — the file exists in the bundle), with bulk detail appropriately split into that reference. Body is under 50 lines with well-organized sections, matching the top anchor. | 5 / 5 |
Total | 14 / 20 Passed |