I would love the option to add 301 redirects for trailing slashes. Specifically a global rule to configure either:
- All non-trailing slash URLs redirect to the trailing slash version (e.g. mydomain.com/page → mydomain.com/page/)
- All trailing slash URLs redirect to the non-trailing slash version (e.g mydomain.com/page/ → mydomain.com/page)
I’m aware there are many different support threads already with discussions on this issue as well as a request for documentation clarity, which I’m not trying to repeat. Ultimately it is not currently supported and only workarounds are offered.
The advice seems to either boil down to
- change your site directory structure to match your preferred trailing slash convention (e.g.
/page.htmlfor no trailing slash and/page/index.htmlfor a trailing slash) and make sure pretty URLs are enabled. - use canonical URLs.
For Pretty URLs, I feel like the convention of trailing-slash-for-directory and no-trailing-slash-for-file convention is a bit outdated and I would prefer to configure this without changing my app build settings. As for canonical URLs - I already use them, but I have never encountered an SEO team who don’t demand both canonical URLs and 301 redirects for dealing with duplicate content.
I’d love to hear if there are any plans to implement a feature like this, given the traction it gets in the support forum? I really enjoy using Netlify 
for my side projects but this is one of those little feature gaps that holds me back from using it for bigger projects.