14
Support Automatic 301 Redirects to URL's with trailing slashes
complete
Patrick Sullivan
Gatsby Cloud does not support automatic 301 redirects to URLs with trailing slashes.
…/blog/guide-to-fast-websites to …/blog/guide-to-fast-websites/
Again, another very important feature that has us blocked on a current project. Google is penalizing us for duplicate content because of this.
Activity Feed
Sort by
Patrick Sullivan
complete
This feature is currently in production and generally available. You can read about enabling this option in our documentation https://www.gatsbyjs.com/docs/reference/config-files/gatsby-config/#trailingslash
As with any hosting changes, we recommend that you test your changes using a pull request before applying to your production site.
Please use our standard bug reporting processing to submit any issues you may encounter: https://github.com/gatsbyjs/gatsby/issues/new?assignees=&labels=type%3A+bug&template=BUG_REPORT.yml
Thank you, and we hope you enjoy the simplicity of this new Gatsby Cloud-integrated feature in the framework!
Patrick Sullivan
This original request was to support automatic 301 redirects to URL's with trailing slashes, which we do support today in Gatsby Cloud.
We're about to bring a framework-integrated feature into Beta that allows you to force the addition / removal of trailing slashes to URLs without any plugins or manual work done within gatsby-node.
I'll notify back to this discussion when the framework-integrated version is in Beta ( ETA late this week, early next week ), and I'd love to hear what you all think!
Link to the feature under development: https://github.com/gatsbyjs/gatsby/discussions/34205
Thanks!
Patrick Sullivan
The corresponding public RFC for this feature can be found here: https://github.com/gatsbyjs/gatsby/discussions/34205
W
Weston Hancock
Excited for this feature as it is impacting our current site negatively as well.
J
Joel Smith
in progress