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
-
Google is still indexing the old domain a year after 301 redirects are put in place
Hi there, You might have experienced this before but for me this is the first. A client of mine moved from domain A (www.domainA.com) to domain B (www.domainB.com). 301 redirects are all in place for over a year. But the old domain is still showing in Google when you search for "site:domainA.com" The HTTP Header check shows this result for the URL https://www.domainA.com/company/cookie-policy.aspx HTTP/1.1 301 Moved Permanently =>
Technical SEO | | iQi
Cache-Control => private
Content-Length => 174
Content-Type => text/html; charset=utf-8
Location => https://www.domain_B_.com/legal/cookie-policy
Server => Microsoft-IIS/10.0
X-AspNetMvc-Version => 5.2
X-AspNet-Version => 4.0.30319
X-Powered-By => ASP.NET
Date => Fri, 15 Mar 2019 12:01:33 GMT
Connection => close Does the redirect look wrong? The change of address request was made on Google Console when the website was moved over a year ago. Edit: Checked the domainA.com on bing and it seems that its not indexed, and replaced with domainB.com, which is the right. Just Google is indexing the old domain! Please let me know your thoughts on why this is happening. Best,0 -
Choice of domain
Hi. I want to build a new site that is optimised for a training product that we have. We have an existing domain which I'm considering pointing at this new site. This domain is one of the new .training TLDs. Let's call this domain foo.training where my main keyword to optimise for will be "foo training". I've also looked and can see that foo-training.com is available. I read up on best practices for domains here : https://mza.bundledseo.com/learn/seo/domain My question is will the .training domain be seen as "spammy" in any way? Am I better to just go ahead and register the .com?
Technical SEO | | rmcatalyst0 -
Why does my 301 show the old urls with new descriptions and titles?
Hi all, We've just rebranded. The 301 appears to have worked well and moved the results and rankings onto the new domain. However a site:olddomain.com search in Google brings up about a hundred pages that have the new titles and descriptions but show the old urls - does anyone have any idea how to make the old domain disappear from the SERPS? Many thanks, Richard
Technical SEO | | panini0 -
301 redirect + new website copy
Hi There, We are currently redeveloping our website and we're rewriting and optimising our many of our service pages. I think I may already know the answer but should we apply 301 redirects from our old services pages to the new versions? The content subject matter will be the same on the new versions, they will just be completely reworded. I would be interested to hear your views. Thanks, Stu
Technical SEO | | Stuart260 -
301 redirects
At the moment it's possible to access the home page of my website via two different urls, with and without www. and you've told me that this can be resolved with Canonicalization and a 301 redirect. Do I do this with my web hosting package or in my html pages? If I can't do it with my web host (1&1) then is there an idiot's guide of how to do it yourself? I've also got both the domain vamospaella.co.uk and vamospaella.com. Is it better to have one of these redirecting to the other for UK traffic (at the moment .co.uk redirects to .com) Thanks
Technical SEO | | melissa10 -
Is it worth setting up 301 redirects from old products to new products?
This year we are using a new supplier and they have provided us a product database of approx. 5k products. About 80% of these products were in our existing database but once we have installed the new database all the URLs will have changed. There is no quick way to match the old products with the new products so we would have to manually match all 5k products if we were were to setup 301 rules for the old products pointing to the new products. Of course this would take a lot of time. So the options are: 1. Is it worth putting in this effort to make the 301 rules? 2. Or are we okay just to delete the old product pages, let the SE see the 404 and just wait for it to index the new pages? 3. Or, as a compromise, should we 301 the old product page to the new category page as this is a lot quicker for us do do than redirecting to the new product page?
Technical SEO | | indigoclothing0 -
301 Redirects
Last year we merged 3 websites into 1 website and launched the new site in February. When developing the new site I created 301 redirects for all the pages from the old sites to the new site. Unfortunately when the new website was created the URLs were not optimised for search engines. I now need to optimised the page URLs. In theory I need to create new 301 redirects from this existing pages to the new optimised URLS. I am concerned that in a few years I might end up with a string of 301 redirects and if I break some links I might loose some ranking. How many redirects will link juice work for? I hope I'm clear here, if not I've attached a image showing what I'm doing. Thank you. unledfh.jpg
Technical SEO | | Seaward-Group0 -
301 Redirect vs Domain Alias
We have hundreds of domains which are either alternate spelling of our primary domain or close keyword names we didn't want our competitor to get before us. The primary domain is running on a dedicated Windows server running IIS6 and set to a static IP. Since it is a static IP and not using host headers any domain pointed to the static IP will immediately show the contents of the site, however the domain will be whatever was typed. Which could be the primary domain or an alias. Two concerns. First, is it possible that Google would penalize us for the alias domains or dilute our primary domain "juice"? Second, we need to properly track traffic from the alias domains. We could make unique content for those performing well and sell or let expire those that are sending no traffic. It's not my goal to use the alias domains to artificially pump up our primary domain. We have them for spelling errors and direct traffic. What is the best practice for handling one or both of these issues?
Technical SEO | | briankb0