NGinx rule for redirecting trailing '/'

[AbsoluteDesign]

We have successfully implemented run-of-the-mill 301s from old URLs to new (there were about 3,000 products). As normal. Like we do on every other site etc.

However, recently search console has started to report a number of 404s with the page names with a trailing forward slash at the end of the .html suffix.

So, /old-url.html is redirecting (301) to /new-url.html

However, now for some reason /old-url.html/ has 'popped up' in the Search Console crawl report as a 404.

Is there a 'blobal' rule you can write in nGinx to say redirect *.html/ to */html (without the forward slash) rather than manually doing them all?

[DmitriiK]

Hi there.

Yes, the global rule should work. However, there is a reason this is happening, and it look like there is an extra rule, which adds that trailing slash. Go through those new rules you've added, make sure that you don't have anything extra. Example might be "Redirect everything from old blog to new blog with adding trailing slash" or something. It's quite common error, so you should be able to figure it out.

Also see when these 404s were discovered, if it was right after you did redirects, it means for sure, that some of the new redirect rules are messed up at some point.

Cheers!