Should I do a redirect when trailing slash and http is changed?

Should I do a redirect when trailing slash and http is changed? - If a page has internal and external outgoing links to redirecting URLs, it’s returning 3xx (301, 302, etc.) HTTP status codes standing for redirection. This issue means that the page does not exist on a permanent or temporary basis. It appears on most of the popular web browsers, usually caused by a misconfigured website. However, there are some steps you can take to ensure the issue isn’t on your side. You can find more details about redirecting URLs by reading the Google Search Central overview. In this article, we’ll go over how you can fix the Should I do a redirect when trailing slash and http is changed? error on your web browser. Problem :

I have noticed that all my internal links (and I have a lot of them) were being linked like so:

https://websitenamehere[dot]com/post-title

Yet, my posts have actually a trailing slash after the title, like so: https://websitenamehere[dot]com/post-title

When I check Google Search Console, I can see like 26.5k links being excluded, because they don't have this trailing slash ("Page with redirect: The URL is a redirect, and therefore was not added to the index."). But when I check out the URL of the one with the trailing slash, they are all indexed and seem fine.

My question: does it still make sense to redirect them or shouldn't I care, as the proper/canonical ones are already indexed?

And would this have an effect on SEO in the first place?

PS: I recently went from http to https, but I can see that almost all https are properly indexed. Should I care to redirect still?

Solution :

Google is just telling you that it doesn't add redirects to its index. This is fine and normal. Continue to redirect to the trailing slash version, which is the version that Google will index.

We hope that this article has helped you resolve the seo, google, google-search-console error in your web browsers. Enjoy browsing the internet uninterrupted!