Once on https should Moz still be picking up errors on http
-
Hello,
Should Moz be picking up http errors still if the sites on https? Or has the https not been done properly? I'm getting duplicate errors amoung other things.
Cheers,
Ruth
-
Wow - sorry this question slipped past, Ruth.
As long as the proper HTTP redirect has been written to HTTPS, there's nothing that needs to be done with canonical tags.
The beauty of 301-redirects is that they are server directives - once in place, its no longer even possible to reach the non-HTTPS URLs. The HTTPS URLs should of course still keep their own self-referential canonical tags, but that's handled automatically in most CMSs (Content Management Systems like WordPress.)
Hope that covers what you were asking?
Paul
-
Hi Ruth,
I am more than happy to help. Please have a look at these resources if you believe the migration has not been done correctly.
Please have a look at these resources I think they will be immensely helpful. Please remember the Google doc referenced in number one is available in line 3 as well as In the instructions anchor text on line 2.
- https://www.aleydasolis.com/en/search-engine-optimization/http-https-migration-checklist-google-docs/
- To easily make a copy, add to your own Drive, download or print, go to the Google Docs, then choose “File” and select your preferred option: (Or use link below)
- https://docs.google.com/spreadsheets/d/1XB26X_wFoBBlQEqecj7HB79hQ7DTLIPo97SS5irwsK8/edit?usp=sharing
Please let me know if I can be of any help,
Thomas
-
Thanks, Thomas will have a look at those.
-
Hi Ruth,
Paul brought up a very good point.
If using Apache and it sounds like you are you can force the HTTP to HTTPS redirect using
<ifmodule mod_rewrite.c="">RewriteEngine On
RewriteCond %{SERVER_PORT} !^443$
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]</ifmodule>See this for more https://www.aleydasolis.com/htaccess-redirects-generator/https-vs-http/
301 Redirects are in place verify that by using a tool like this one. you can drop all the URLs you want to check in here. https://httpstatus.io/
Then make sure any HTTP is a 301 and any HTTPS is a 200
Then run a search and replace
http://mydomain.com
tohttps://mydomain.com
http://www.mydomain.com
tohttps://www.mydomain.com
If you are running a WordPress website this is a very effective plug-in ( and free if you type the name into wordpress.org's plugin repo)
https://bettersearchreplace.com/ or https://interconnectit.com/products/search-and-replace-for-wordpress-databases/
Your canonical tags (unless very good reason like third-party content) should be self-referencing meaning add canonical's to the https:// urls not the http:// URLs like below. A good example is what you see below
Moz will tell you as will https://www.screamingfrog.co.uk/redirect-checker/ & https://deepcrawl.com will easily find any of the problems. some references below for rel-canonical tags
https://moz.com/blog/rel-canonical
https://yoast.com/rel-canonical/
Last but not least here is a wonderful tutorial that goes over migrating from http to https
https://www.keycdn.com/blog/http-to-https/
I hope this was of help,
Tom
-
Hi Paul,
Yes thank you, that's brilliant and confirms what I've been thinking - that the https hasn't been done properly as they're not redirecting when going to the http version. I thought the client had at the htaccess so will look into that.
If the redirects are done properly do I need to add canonical tags or are the redirects enough? Just want to make sure I'm covering all bases.
Thanks so much for your advice.
Cheers,
Ruth
-
You need to ensure that the HTTP version of the site's URLs are no longer reachable, Ruth. That means adding a 301-redirect to force all URLs to their HTTPS versions. This is the most likely cause of your issue
To test, simply go to a page URL in the browser address bar and remove the s from the HTTPS and hit enter. Watch what happens. If the address bar shows the automatic change back to the HTTPS version of the URL, you're good. If it doesn't, you'll need to add the redirect.
You should also ensure that all the internal links within the site have been rewritten to use the HTTPS version of the URLs - like menus, sidebars, widgets, and in-content links to other pages.
Hope that helps?
Paul
-
Thanks, Thomas. The https urls are in place but I was concerned that if the http urls are showing up still that the move to https hasn't been done properly.
-
Do a search & replace on your site then recheck it.
search for HTTP url's & replace with https URL's
Got a burning SEO question?
Subscribe to Moz Pro to gain full access to Q&A, answer questions, and ask your own.
Browse Questions
Explore more categories
-
Moz Tools
Chat with the community about the Moz tools.
-
SEO Tactics
Discuss the SEO process with fellow marketers
-
Community
Discuss industry events, jobs, and news!
-
Digital Marketing
Chat about tactics outside of SEO
-
Research & Trends
Dive into research and trends in the search industry.
-
Support
Connect on product support and feature requests.
Related Questions
-
Blocking pages from Moz and Alexa robots
Hello, We want to block all pages in this directory from Moz and Alexa robots - /slabinventory/search/ Here is an example page - https://www.msisurfaces.com/slabinventory/search/granite/giallo-fiesta/los-angeles-slabs/msi/ Let me know if this is a valid disallow for what I'm trying to. User-agent: ia_archiver
Technical SEO | | Pushm
Disallow: /slabinventory/search/* User-agent: rogerbot
Disallow: /slabinventory/search/* Thanks.0 -
Website crawl error
Hi all, When I try to crawl a website, I got next error message: "java.lang.IllegalArgumentException: Illegal cookie name" For the moment, I found next explanation: The errors indicate that one of the web servers within the same cookie domain as the server is setting a cookie for your domain with the name "path", as well as another cookie with the name "domain" Does anyone has experience with this problem, knows what it means and knows how to solve it? Thanks in advance! Jens
Technical SEO | | WeAreDigital_BE0 -
Http urls on a new https website
Hi, If a site is quite new and setup as https from the beginning why would http variations exist? There are 301 redirects in place from the http to the https variation and also canonical tags pointing back to the http variation? This seems contradictory to me. I'm not sure why the http variations exist at all but they have gone to the trouble of redirecting these to the https variation indicating that it is the variation of choice but at the same time using a canonical tag that indicates the http variation is the original/main url? Thanks
Technical SEO | | MVIreland0 -
Error after scanning with browseo.net
Good day! I have done a scan on my site with browseo.net ( and a few other similar scanners ) and got the mess seen in the screenshot. I've tried deleting all the files in the website folder, replace it with a single image file, but it still shows the same error. What could this mean and should i be worried? P.S Found my answer after contacting the helpful support of browseo.net : It took me some time to figure out what was going on, but it seems as if you are mixing content types. Browsers are quite smart when it comes to interpreting the contents, so they are much more forgiving than we are. Browseo crawls your website and detects that you are setting utf-8 as part of the meta information. By doing so, it converts the content in a different character encoding then what they are supposed to be. In a quick test, I tried to fetch the content type based on the response object, but without any success. So I am suspecting that in reality your content is not utf-8 encoded when you parse it into joomla. The wrong character type is then carried over for the body (which explains why we can still read the header information). All of this explains the error. In order for it to work in browseo, you’d have to set the content type correctly, or convert your own content into utf-8 before parsing. It may be that you are either storing this incorrectly in the database (check your db settings for a different content type other than utf-8) or that other settings are a bit messed up. The good news is, that google is probably interpreting your websites correctly, so you won’t be punished for this, but perhaps something to look into… From Paul Piper VKNNnAL.png?1
Technical SEO | | AlexElks0 -
429 Errors?
I have over 500,000 429 errors in webmaster tools. Do I need to be concerned about these errors?
Technical SEO | | TheKrazyCouponLady0 -
Https enabled site with seo issues
Hello, Is there a problem with seo bots etc to crawl and rank my wesbite well if the entire site is https enabled? We have a sign in button which results on the next page being https along with the main homepage and all other pages are https enabled. Any major setbacks to the seo strategies? How do I overcome these issues?
Technical SEO | | shanky10 -
404 error
Both SEOmoz and Google webmaster tools are returning over 4000 error 404.The majority or returned error URLs are for images, and all URLs end up with %20target=as shown belowimages/products/detail/AD9058RoundGlassTableChairs.jpg%20target=images/products/detail/BM921ModernRoundDiningTable.jpg%20target=images/products/detail/CR701506CappuccinoCoffeeTableSet.jpg%20target=any suggestions?RegardsTony
Technical SEO | | OCFurniture0 -
I have a site that has both http:// and https:// versions indexed, e.g. https://www.homepage.com/ and http://www.homepage.com/. How do I de-index the https// versions without losing the link juice that is going to the https://homepage.com/ pages?
I can't 301 https// to http:// since there are some form pages that need to be https:// The site has 20,000 + pages so individually 301ing each page would be a nightmare. Any suggestions would be greatly appreciated.
Technical SEO | | fthead90