# Gatsby trailing slash redirection

**URL:** <https://answers.netlify.com/t/gatsby-trailing-slash-redirection/41595>\
**Category:** Support\
**Tags:** redirects, gatsby\
**Created:** [July 28, 2021, 5:19am UTC](https://answers.netlify.com/t/gatsby-trailing-slash-redirection/41595 "2021-07-28T05:19:34Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![smit0086](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/smit0086/32/27941_2.png) [@smit0086](https://answers.netlify.com/u/smit0086)\
**Post date:** [July 28, 2021, 5:19am UTC](https://answers.netlify.com/t/gatsby-trailing-slash-redirection/41595/1 "2021-07-28T05:19:34Z")

</div>

Hello,  
I am using gatsby generated static site for my website. I wanted to prevent redirection from non-trailing to trailing slash. One solution we implemented was to use a gatsby plugin to force non-trailing slash and disabled pretty URLs. but this causes both with and without slashed pages to return 200. I want to have my static site redirect 301 from trailing to non-trailing slash page.

---

<div class="post-metadata">

**Author:** ![hillary](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/hillary/32/21132_2.png) [@hillary](https://answers.netlify.com/u/hillary)\
**Post date:** [July 29, 2021, 3:39pm UTC](https://answers.netlify.com/t/gatsby-trailing-slash-redirection/41595/2 "2021-07-29T15:39:17Z")

</div>

Hey there, @smit0086 👋

Welcome to the Netlify Forums!

A good first stop would be the debugging redirects support guide, which I have [linked here](https://answers.netlify.com/t/support-guide-making-redirects-work-for-you-troubleshooting-and-debugging/13433).

We also have this post on [asset optimization and trailing slashes](https://answers.netlify.com/t/problem-with-assets-optimization-relative-links-and-integrity-check/13732/9) and [our Docs](https://docs.netlify.com/routing/redirects/) outline redirects and rewrites as well.

If you are still having issues after using those resources, please respond with your site name and the additional debugging steps you tried, as well as any additional screenshots or images that would be useful!