Is HTTP to HTTPS redirect required even if site is only on HTTPS?

Is HTTP to HTTPS redirect required even if site is only on HTTPS? - 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 Is HTTP to HTTPS redirect required even if site is only on HTTPS? error on your web browser. Problem :

I have a new website and from day one, it was on HTTPS. For example:

https://www.example.com/

Do I still need to redirect HTTP to HTTPS to avoid content duplication? For example, should I still set a redirect from http://www.example.com/ to https://www.example.com/?

Solution :

If search engines never crawled HTTP URLs under this domain, and if there are no HTTP links anywhere, you don’t need to redirect from HTTP to HTTPS for SEO purposes.

But you should still redirect for usability reasons:

• If users manually enter URLs to your site, they often omit the https:// (e.g., starting with www.). Unless they visited your HTTPS site before, their browsers will likely request the HTTP variant.




• If users enter the full URL, they might not notice the s in https:// and enter http://.

If your site sends HSTS Preload headers and is listed in chrome's HSTS Preload list and all your users are using a browser that uses that list, then you can probably get away without using a redirect (assuming your domain doesn't respond on port 80 at all).

However if there's a chance that users might just type your domain in manually then you should really ensure that you redirect to HTTPS with a 301 permanent redirect.

Best practices dictate that we should redirect non-secure traffic to https. One example: if you want to add a login script in the future, it must be secure. At that point, your visitors using http will be getting all sorts of error messages and warnings (mixed content, unsecured web form ...).

To avoid this kind of mess, just do the redirect.

If it is from day one on HTTPS only, for me it means it should not even listen on port 80 for HTTP (trying to connect with pure HTTP should trigger a timeout error).

We hope that this article has helped you resolve the seo, redirects, https error in your web browsers. Enjoy browsing the internet uninterrupted!