Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →thedaviddias/trailing-slash
Use when applies to all static and dynamic websites. Use when auditing a site for duplicate content, setting up a new site, or after migrating platforms that changed URL conventions.
Passed 21 of 22 test cases with the skill, and 21 of 22 without it.
1 fixed20 passed either way0 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A test case the skill fixed. Same model, same prompt, with and without the skill.
A client claims: 'We don't need 301 redirects between /docs and /docs/ because putting <link rel="canonical"> on both pages is sufficient for search engines.' Evaluate this claim.
| Checked | Without skill | With skill |
|---|---|---|
| Disagrees with the claim that canonical tags alone are sufficient | Passed | Passed |
| States that 301 redirects are required to prevent dual 200 responses and consolidate crawl budget | Missed | Passed |
The instructions your model reads when the skill loads.
Inconsistent trailing slashes create duplicate content — Google sees /page and /page/ as two separate URLs competing for the same ranking, splitting PageRank between them.
/page/ and /page must not return HTTP 200; one must redirect to the otherrel="canonical" to the preferred version on all pagesFor a sample of URLs, test both the trailing-slash and non-trailing-slash versions. Both should NOT return HTTP 200 — one must 301-redirect to the other. Check that internal links, sitemap <loc> values, and canonical tags all use the same convention consistently.
Choose a canonical URL convention. Add server or framework redirect rules so the non-preferred variant permanently redirects (301) to the preferred one. Update all internal links, canonical tags, and sitemap entries to use the preferred format.
Explain why /page and /page/ are treated as distinct URLs by default, how this creates duplicate content, and how 301 redirects and canonical tags resolve the ambiguity.
Review metadata generation, rendered HTML, structured data, and response headers related to Use trailing slashes consistently. Flag exact routes or templates where search-facing output violates the rule, and describe how to verify the final page output.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/seo/trailing-slash
test cases passed, vs 21 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.