Use trailing slashes consistently
SkillWeb & browsingtrailing-slash is a skill that gives an AI agent a checklist for handling trailing slashes consistently across website URLs. It applies to static and dynamic websites, and is useful when auditing a site for duplicate content, setting up a new site, or after migrating platforms that changed URL conventions.
Available today. Use it from your connected AI after setup.
No other account needed.
Have an AI agent that can load skills.
Then ask your AI: use the Use trailing slashes consistently skill
What your AI can do with it
- Provides a checklist for consistent trailing-slash handling across URLs
- Supports auditing a site for duplicate content caused by slash variants
- Guides URL conventions when setting up a new site
- Helps reconcile URL conventions after a platform migration
- Applies to both static and dynamic websites
Getting started
- Have an AI agent that can load skills.
- Add the trailing-slash skill to the agent's available skills.
- Ask the agent to apply it when auditing URLs, setting up a site, or after a migration.
What this skill tells your AI
The instructions your AI receives, as published by thedaviddias/front-end-checklist in skills/trailing-slash/SKILL.md and read by ahel’s review.
Inconsistent trailing slashes create duplicate content — Google sees /page and /page/ as two separate URLs competing for the same ranking, splitting PageRank between them.
Quick Reference
- Pick one convention — trailing slash or no trailing slash — and enforce it site-wide with 301 redirects
- Both
/page/and/pagemust not return HTTP 200; one must redirect to the other - Set
rel="canonical"to the preferred version on all pages - Ensure all internal links, sitemaps, and canonical tags use the same convention
Check
For 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.
Fix
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
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.
Code Review
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/en/rules/seo/trailing-slash
Signals
- GitHub stars
- 74k
- Forks
- 7k
- Last commit
- Aug 2026
Questions
- When should this skill be used?
- Use it when auditing a site for duplicate content, setting up a new site, or after migrating platforms that changed URL conventions. It applies to all static and dynamic websites.
- Does it work for both static and dynamic sites?
- Yes, the skill applies to all static and dynamic websites.
- What does the skill actually give the agent?
- A checklist for handling trailing slashes consistently across website URLs.
Advanced
- Item type
- skill
- Key
trailing-slash- Source
- github.com/thedaviddias/front-end-checklist