Changing Domains - 301 old https to new https
-
Brief History:
Our company made change to a new domain. Both domains had an SSL configured on it in which the old domain SSL was controlled and created by Shopify which gave us limited control. Because we couldn't redirect the old https:// to the new https:// So basically we duplicated our new HTML website and put canonical ref on all duplicate pages to the final domain to help get search to navigate to the newer domain.
Question:
In the near future I would like to take down the old domain and do a 301 domain forwarding. What is the correct course of action to complete this? Our old domain was indexed and SERP results were tied to it's https:// url's.
-
Hi
Cloudflare does not need to be added two times (or to each domain) to work or it would only be used on the old domain for an Automattic 301 redirect to the new site/ domain so I would only use it once to make sure I get the set of 301s for the old domain.
Does that make sense?
(The "yournewdomain.com" does not need to run on Cloudflare only the "yourolddomain.com" domain)
You will then want to see how this is used in the following pattern:
https://yourolddomain.com/*
Select “Forwarding URL” and “301 – Permanent Redirect” for the settings, and input the following rule:
https://newyourdomain.com/$1
The /$1 enables the wildcard part to function. Then click on “Save and Deploy.”
cite: https://woorkup.com/free-url-forwarding/
Let me know if I can be of any help,
Thomas Zickell
-
Thank you for the response Tom - This does make sense and I will implement and let you know how it works out. I have very limited experience with the free Cloudflare account so I do have one question. Does the domain I am forwarding everything need to be controlled by Cloudflare as well? Didn't know if that was needed for everything to play nice.
-
Thomas is right you IF YOU STILL HAVE THE DOMAIN you can use Cloudflare to do 100% Free URL Forwarding With HTTP & https 301 wildcard redirects with no server.
"Because we couldn't redirect the old https:// to the new https:// So basically we duplicated our new HTML website and put canonical ref on all duplicate pages to the final domain to help get search to navigate to the newer domain."
So the canonical ref on all duplicate pages to the new domain will help get Google to navigate to the newer domain but not like a 301 redirect will. So on Shopify, you are pointing the old URLs to the new domains URL's I hope if not please 301 use Cloudflare for 301 domain forwarding
- If so Follow the tutorial below on how setup free URL forwarding with Cloudflare, along with 301 wildcard redirects.
- https://woorkup.com/free-url-forwarding/
if you do change the URL's after the forward slash "/" or don't want Cloudflare to run your old domain so you can take down the old domain and do a 301 domain forwarding you should read the guides below.
- https://builtvisible.com/domain-migration/
- https://moz.com/blog/achieving-an-seo-friendly-domain-migration-the-infographic
- https://searchengineland.com/changing-domain-names-2016-10-easily-overlooked-steps-can-save-seo-248484
this setup, you don't want to duplicate your web site HTTP to HTTPS if needed.
If I where you I would just do what is in this guide the only cost is the cost of your old domain & it will auto line up urls (if you did not change them aside from the domain name.
- Read & use this https://woorkup.com/free-url-forwarding/
Hope this helps,
Tom
-
If I'm correct, you're no longer using the old domain and just redirecting to the new site?
If that's correct, why keep it with Shopify at all, you could instead point it to a different server (or to Cloudflare which'll be able to handle to redirects through page rules without you having to do any code).
The best course of action is to 301 redirect the site to the new site, then on the new site (after checking for issues) submit sitemaps/fetch as google. To speed up this process slightly you can also submit a sitemap for the old site, Google will see the redirect when they try to crawl any page.
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
-
Resolving 301 Redirect Chains from Different URL Versions (http, https, www, non-www)
Hi all, Our website has undergone both a redesign (with new URLs) and a migration to HTTPS in recent years. I'm having difficulties ensuring all URLs redirect to the correct version all the while preventing redirect chains. Right now everything is redirecting to the correct version but it usually takes up to two redirects to make this happen. See below for an example. How do I go about addressing this, or is this not even something I should concern myself with? Redirects (2) <colgroup><col width="123"><col width="302"></colgroup>
Technical SEO | | theyoungfirm
| Redirect Type | URL |
| | http://www.theyoungfirm.com/blog/2009/index.html 301 | https://theyoungfirm.com/blog/2009/index.html 301 | https://theyoungfirm.com/blog/ | This code below was what we added to our htaccess file. Prior to adding this, the various subdomain versions (www, non-www, http, etc.) were not redirecting properly. But ever since we added it, it's now created these additional URLs (see bolded URL above) as a middle step before resolving to the correct URL. RewriteEngine on RewriteCond %{HTTP_HOST} ^www.(.*)$ [NC] RewriteRule ^(.*)$ https://%1/$1 [R=301,L] RewriteCond %{HTTPS} !on RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L] Your feedback is much appreciated. Thanks in advance for your help. Sincerely, Bethany0 -
Domain change recommendations
We recently migrated one of our websites to a new domain. Obviously we were expecting a decrease in traffic initially, but it has actually gone down by 70% week-over-week since we made the switch. We set up a 301 redirect from the old domain to the new domain, changed all internal links to the new domain and changed all inbound links that we owned to the new domain. Our research suggested the best way to approach a domain change was by keeping it simple and not making too many changes at once. So my questions are: 1. Are these the kinds of results we should expect initially after a domain change? And if not, 2. What are the steps we should take from here? Thanks!
Technical SEO | | gouldtr0 -
What is cross domain?
what is cross domain? can any one explain in simple language ?
Technical SEO | | constructionhelpline0 -
Changing Domain Registrars have an affect on rankings?
So, I just wanted to move my domain from GoDaddy to NameCheap. I am still thinking about the move as I am not sure what affect it will have on my rankings. Has anyone here done it before? Did you see any drop in rankings? Also, while I was at it - I was thinking maybe I can add WhoisGuard too. I am not too paranoid about people getting my info from WhoIs, but does having a private Whois have an affect on ranking?
Technical SEO | | uzair0 -
Google , 301 redirects, and multiple domains pointing to the same content.
Google, 301 redirects, and multiple domains pointing to the same content. This is my first post here. I would like to begin by thanking anyone in advance for their help. It is much appreciated. Secondly, I'm posting in the wrong place or something please forgive me simply point me in the right direction I'm a quick learner. I think I'm battling a redirect problem but I want to be sure before I make changes. In order to accurately assess the situation a little background is necessary. I have had a site called tx-laws.com for about 15 years. It was a site that was used primarily by private resource and as such was never SEO'd. The site itself was in fact quite Seo unfriendly. despite a complete lack of marketing or SEO efforts, over time, SEO aside, this domain eventually made it to page one of Google Yahoo and Bing under the keywords Texas laws. About six months ago I decided to revamp the site and create a new resource aimed at a public market. A good deal of effort was made to re-work the SEO. The new site was developed at a different domain name: easylawlook up.com. Within a few months this domain name surpassed tx-laws in Google and was holding its place in position number eight out of 190 million results. Note that at this point no marketing has been done, that is to say there has been no social networking, no e-mail campaigns, no blogs, -- nothing but content. All was well until a few weeks ago I decided to upgrade our network and our servers. During this period there was some downtime unfortunately. When the upgrade was complete everything seemed fine until a week or so later when our primary domain easy law look up vanished off Google. At first I thought it was downtime but now I'm not so sure. The current configuration reroutes traffic from tx-laws to easylawlookup in IIS by pointing both domains to the same root directory. Everything else was handled through scripting. As far as I know this is how it was always set up. At present there is no 301 Redirect in place for tx-laws (as I'm sure there probably should be). Interestingly enough the back links to easylaw also went away. Even more telling however is that now when I visit link: easylawlookup.com there is only one link, and that link is to a domain which references tx-laws not easy law. So it would appear that I have confused Google with regards to my actual intentions. My question is this. Right now my rankings for tx-laws remain unchanged. The last thing I want to have happen is to see those disappear as well. If easy law has somehow been penalized and I redirect tx-laws to easy through a 301 will I screw up my rankings for this domain as well? Any comments or input on the situation are welcome. I just want to think it through before I start making more changes which might make things worse instead of better. Ultimately though, there is no reason that the old domain can't be redirected to the new domain at this point unless it would mean that I run the risk of losing my listings for tx-laws, ending up with nothing instead of transferring any link juice and traffic to easy law. With regards to the down time, it was substantial over a couple of weeks with many hours off-line. However this downtime would have affected both domains the only difference being that the one domain had been in existence for 15 years as opposed to six months for the other. So is my problem downtime, lack of proper 301 redirect, or something else? and if I implement a 301 at this point do I risk damaging the remaining domain which is operational? Thanks again for any help.
Technical SEO | | Steviebone0 -
301 lots of old pages to home page
Will it hurt me if i redirect a few hundred old pages to my home page? I currently have a mess on my hands with many 404's showing up after moving my site to a new ecommerce server. We have been at the new server for 2 years but still have 337 404s showing up in google webmaster tools. I don't think it would affect users as very few people woudl find those old links but I don't want to mess with google. Also, how much are those 404s hurting my rank?
Technical SEO | | bhsiao1 -
301 redirects and old domain names
Thanks to the great advice i've received on this forum, I'm combining 50 different truck sites into a single, ultimate truck website. So my question is how long should I make a website 301 redirect to the appropriate page on my new website? My thought is that if it works well to have a single website, it might be nice to eventually sell off some of the old domain names that I won't be using anymore. Thanks! Andy
Technical SEO | | daenterpri0