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://mza.bundledseo.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.
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
-
Old Content after 301 Redirect Success
Hi, I want to ask what need I do to the old content after my 301 redirect to the new domain with the same content success? Do I need to remove that old content? Nothing bad happen right? Thanks
Technical SEO | | matthewparkman0 -
Https to http
Two versions of the same page are being served at the moment. Certain pages on the site redirect to the https version whilst others don't. I am being flagged for duplicate content because of this. Is this a simple fix? As in just redirect all to the https version and set the preferred version in WMT?
Technical SEO | | TAT1000 -
Changed site to https now GWT and analytics - do I Know have to re-add it
Hi had the previous version (wordpress) site in GWT working just fine - now everything seems to have stopped. Do I have to treat this as an entirely new site and now add a new account for the https version? Many thanks,
Technical SEO | | AndreavanEugen0 -
Domain Change -- Drop in Rank
So I had a client that recently decided to change their URL to make it more "searchable"/shorter. Since doing so, I have noticed a significant drop in rankings for a number of the keyword terms we were previously ranking for. Is there a way to push the links to the new URL or is the only solution to revert back to the old URL?
Technical SEO | | maxcarnage0 -
Find all old links from a site to 301
We worked on this site a while ago - http://www.electric-heatingsupplies.co.uk/ Whilst we did a big 301 redirect exercise, I wanted to check that we "got" all of them. Is there a historical way I can check all the old indexed links to make sure they correlate to the new links? Thanks!!
Technical SEO | | lauratagdigital0 -
Preferred domain
In GWT it gives an option to do the following but which is best? and why? If you specify your preferred domain as http://www.example.com and we find a link to http://example.com, we'll consider both links the same. | <label for="no_assoc">Don't set a preferred domain</label> |
Technical SEO | | jwdl
| <label for="use_www">Display URLs as ** www.example.com**</label> |
| <label for="use_nowww">Display URLs as example**.com **</label> |0 -
Should we 301 redirect our old domain to the new domain
We have a product that when started was under the domain appnowgo.com. We've since changed the name and the domain is now knackhq.com. The latter domain doesn't rank nearly as well as the former for many of the keywords we are targeting. For example... "online database builder" and "web app builder" are two of those keywords. Obviously having app in the domain is not a bad thing but it is our old name. The question is, should we 301 the appnowgo.com domain to knackhq.com? Or should we use that better rank and just link users to knackhq.com from the appnowgo.com site until we can increase our ranking for knackhq.com? We don't plan to update the content on appnowgo.com anymore and we obviously don't want to drop off rank if at all possible. Thanks! Eric
Technical SEO | | sitestrux0 -
Keyword in Domain or not?
My on page optimization grade is an "A" with the following factors; Factor Overview <dl class="scoreboard clearfix"> <dt>Critical Factors</dt> <dd>4 / 4</dd> <dt>High Importance Factors</dt> <dd>7 / 7</dd> <dt>Moderate Importance Factors</dt> <dd>8 / 9</dd> <dt>Low Importance Factors</dt> <dd>11 / 11</dd> <dt>Optional Factors</dt> <dd>5 / 5</dd> </dl> The main thing I appear to be missing is keywords in my URL. How truly important is that in today's SEO world and how much time or ranking would be lost if I do not have control to change the external links to my website if I decided to migrate to a keyword relevant url?
Technical SEO | | classa0