Switching from HTTP to HTTPS: 301 redirect or keep both & rel canonical?
-
Hey Mozzers,
I'll be moving several sites from HTTP to HTTPS in the coming weeks (same brand, multiple ccTLDs). We'll start on a low traffic site and test it for 2-4 weeks to see the impact before rolling out across all 8 sites.
Ideally, I'd like to simply 301 redirect the HTTP version page to the HTTPS version of the page (to get that potential SEO rankings boost). However, I'm concerned about the potential drop in rankings, links and traffic.
I'm thinking of alternative ways and so instead of the 301 redirect approach, I would keep both sites live and accessible, and then add rel canonical on the HTTPS pages to point towards HTTP so that Google keeps the current pages/ links/ indexed as they are today (in this case, HTTPS is more UX than for SEO).
Has anyone tried the rel canonical approach, and if so, what were the results? Do you recommend it?
Also, for those who have implemented HTTPS, how long did it take for Google to index those pages over the older HTTP pages?
-
Thanks Eric, I appreciate the response.
-
Regarding the GCLIDs, you'll want to update your Google AdWords campaigns and anywhere else you can updated the URLs to the new HTTPs version of your site.
Whenever you use a 301 Permanent Redirect you typically lose the referrer data, so that's why you're going to see issues with the referrers.
-
I would definitely use the 301 permanent redirects and NOT use the canonical tag for this. Also, don't forget to verify the HTTPs version of your site in Google Search Console, as well. We recommend getting a few new links to the HTTPs version of the site, as that will help with indexing and crawling.
-
The best way to mitigate this problem would be to update the destination URLs in your Adwords Campaigns. You can do this in bulk relatively quickly using the Adwords Editor desktop application.
-
Hi Logan,
I have a question related to this topic. We have something similar in place, but we are struggling as the 301 redirect from http to https sometime kills the gclid parameter that AdWords uses to track clicks coming search or display campaigns.
Have you heard about this before? Do you any practical solution to this?
Cheers,
Kilgray Translation Technologies
-
No problem!
-
Thanks Logan!
-
Hi Steven,
You'll definitely want to apply 301 redirects to any site that you move to HTTPS. For most sites, this can typically be done with a single redirect rules that essentially replaces http with https, so you won't have to comb through each URL and apply one-to-one redirects.
No need to worry about losing link juice, Google views these types of 301s differently than a typical 301, and all authority will pass through them.
Canonical should also be applied, this will help search engines learn your new URL structure and ensure they index the new HTTPS URLs.
Cryus Shepard wrote a great post with all the necessary steps for a secure migration, check it out here: https://moz.com/blog/seo-tips-https-ssl
Good luck!
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
-
Should I put rel next and rel prev and canonical on tags pages
Hi I have a tag pages on a news website each tag page is divided to several pages, but Google does't crawled those pages because the links are in javaScript, I want to do the following things: Change the links to html href Add rel=pref rel=next Add a canonical in each page with the url of the main tag page Do you agree with my solution? Thanks Roy
Intermediate & Advanced SEO | | kadut1 -
Rel=canonical on pre-migration website
I have an e-commerce client that is migrating platforms. The current structure of their existing website has led to what I would believe to be mass duplicate content. They have something north of 150,000 indexed URLs. However, 143,000+ of these have query strings and the content is identical to pages without any query string. Even so, the site does pretty well from an organic stand point compared to many of its direct competitors. Here is my question: (1) I am assuming that I should go into WMT (Google/Bing) and tell both search engines to ignore query strings. (2) In a review of back links, it does appear that there is a mish mash of good incoming links both to the clean and the dirty URLs. Should I add a rel=canonical via a script to all the pages with query strings before we make our migration and allow the search engines some time to process? (3) I'm assuming I can continue to watch the indexation of the URLs, but should I also tell search engines to remove the URLs of the dirty URLs? (4) Should I do Fetch in WMT? And if so, what sequence should I do for 1-4. How long should I wait between doing the above and undertaking the migration?
Intermediate & Advanced SEO | | ExploreConsulting0 -
From HTTP to HTTPS
Hi We have implemented HTTPS to the our website. Do we need to now redirect the whole site to HTTPS in the HTTACCESS file? Because when you enter the site via a google search or enter the domain directly the site is set to HTTP once we click on a URL on the page it sets it to HTTPS so do we require to redirect from the start? thanks
Intermediate & Advanced SEO | | Direct_Ram
E0 -
301 Redirects?
We have an e-commerce website with about 4500 products for sale. About 1200 of these items were not showing up in the Google PLA ads because they were $0 dollar items, so we made those products invisible. Then Set 301 Redirects for each of the 1200 items. My question is this; we want to turn back on the 1200 items, should we delete the 301 redirects that are in place for them.? Will it hurt SEO performance by having them?
Intermediate & Advanced SEO | | Goriilla0 -
Set up a rel canonical
I have a question. I was wondering, if it was possible to set up a rel canonical. When I can't access the non canonical pages? For example, my site as at www.site.com , but the non cannocail is at site.com is their any way to set thet up without actually edting it at site.com ? Thanks for your help
Intermediate & Advanced SEO | | PeterRota0 -
How does Google treat chained 301 redirects?
I did the following two chained 301 redirects (A->B->C) Plural to Singular to New Domain A. http://domain1.com/filenames B. http://domain1.com/filename C. http://domain2.com/filename To new domain without www and then back to origining domain A. http://www.domain1.com/filename B. http://domain2.com/filename C. http://domain1.com/fifilename How much link juicy will be rediectetoto URL C in above two scenarios?
Intermediate & Advanced SEO | | Bull1350 -
How To Remve Rel Canonical Error from site
Hello friends, I have a site there I install all in one SEO plugin when I add my site at seomoz.org after the crawling results it so there are a penalty of Rel Conanical tag error but when I see my editor code there I see that all in one seo automatically giving rel conanical tag. Now I don’t understand that why seomoz giving these errors. Please help me to resolve this problem.
Intermediate & Advanced SEO | | KLLC0 -
301 redirect help
Hey guys, I normally work in WordPress and just use a 301 redirect plugin. I bought a site and rather than maintain two similar ones have decided to redirect one to the other. I am having trouble with the .htaccess file. Here is an example. These are two redirects: redirect 301 /category/models/next/2
Intermediate & Advanced SEO | | DanDeceuster
redirect 301 /category/models I want both of these URLs to redirect to the same URL of the new site. However, the /category/models is the only one working. It redirects to the new page just fine. The /category/models/next/2 is redirecting to nearly the same URL on the new site, only it is adding /next/2 to the end and that is bringing up a 404. Why is it adding /next/2 to the new URL? How can I fix this? There are several doing this. Help appreciated!0