We are redirecting http and non www versions of our website. Should all versions http (non www version and www version) and https (non www version) should just have 1 redirect to the https www version?
-
We are redirecting http and non www versions of our website. Should all versions http (non www version and www version) and https (non www version) should just have 1 redirect to the https www version?
Thant way all forms of the website are pointing to one version?
-
Ideally, yes.
However, it's not likely to have a massive impact if you do have a redirect chain first to www and then to https.
-
if you talking about the domain
you should 301 redirect each of the 3 of 4 different URLs to the one you want to be the primary domain that is using https
This is a great guide
https://ahrefs.com/blog/301-redirects/
You can always use CloudFlare as free & easy fix.
If you want to use HSTS preload or just HSTS
Test your 301 setup using
https://hstspreload.org/?domain=example.com
If you are using https://www. as the primary
See you must force http to https and the HTTP://www
Must redirect to the https:// bare domain so that means two redirects.
Error: No redirect from HTTP
http://example.comdoes not redirect tohttps://example.com.Hope this helps,
Tom
-
Thank you for the advice it is very useful.
In GWT we are also showing redirects on all pages from the non / page to the / page
ie cardiff.co.uk redirects to cardiff.co.uk/
is this OK?
-
It is fine to 301 redirect to** "/"** you need to pick forward slash "/" or no forward slash.
- SEE:
- https://webmasters.googleblog.com/2010/04/to-slash-or-not-to-slash.html
- https://www.seroundtable.com/google-trailing-slashes-url-24943.html
You should force HTTPS
- http://cardiff.co.uk 301's to http://www.cardiff.co.uk/
- See: https://i.imgur.com/fg34sXR.png
- You should add https
- https://dash.cloudflare.com/sign-up
- or
- https://www.rapidtables.com/web/tools/redirect-generator.html
Add a SSL cert I would just add cloudflare.com (if you want fast & easy also Free)
- https://support.cloudflare.com/hc/en-us/articles/204144518
- https://support.cloudflare.com/hc/en-us/articles/200172286-Configuring-URL-forwarding-or-redirects-with-Cloudflare-Page-Rules
When configuring Page Rules, the Always use HTTPS action is the simplest method to redirect HTTP requests to HTTPS. You can also use the Forwarding URL action with a 301 redirect if you need to redirect to another subdomain in addition to forcing HTTPS. For example, a Page Rule match for
**_http://_cardiff.co.uk_/*_**with a _Forwarding URL _of
**_https://www.cardiff.co.uk/$1_**or ASP.NET
<%@ Language="VBScript" %>
<%
' ASP permanent URL redirect - generated by www.rapidtables.com
Response.Status="301 Moved Permanently"
Response.AddHeader "Location", "https://www.cardiff.co.uk/"
Response.End
%>Redirect entire domain from HTTP to HTTPS
RewriteEngine On RewriteCond %{HTTPS} off RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]Redirect entire domain from non-www to www and HTTP to HTTPS
RewriteEngine On RewriteCond %{HTTP_HOST} !^www\. [NC] RewriteRule ^ https://www.%{HTTP_HOST}%{REQUEST_URI} [L,R=301] RewriteCond %{HTTP:X-Forwarded-Proto} !https RewriteCond %{HTTPS} off RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]Hope this helps,
Tom
-
PS I will run a crawl to check
-
This post is deleted! -
I am happy I could be of help please let me know if there's anything else I can be of assistance with?