Splitting and moving site to two domains - How to redirect
-
I have a client who is going to split their retail and wholesale business and rebrand the retail biz. So let’s say they are going to move everything from currentdomain.com to either retaildomain.com or wholesaledomain.com. The most important business for them is the retail site, so they want to pass on as much ranking power as they can from currentdomain.com to retaildomain.com. I see two choices here:
We can 301 redirect all of currentdomain.com to retaildomain.com, and then redirect any wholesale pages to wholesaledomain.com. The advantage is that we can use GSC’s change of address tool to report the change to Google. The downside is that there is a redirect chain (2 hops) to wholesaledomain.com. Would this confuse Google?
Or we can 301 redirect page by page from currentdomain.com to the appropriate page on either new site. This means no redirect chains but it also means that we can’t use GSC’s change of address tool.
Which would you do and why? And is there another option that I'm missing? I appreciate any insights you can share.
-
You can do that. No problem. It will be best for wholesale customers.
My comments are designed to be best for retail rankings. If my connections to wholesale customers are poor then I would use your method. If my connections to wholesale customers are strong them I would do what's best for retail rankings. It is simply a matter of choice.
-
Your points about communicating as much as possible offline and by email, etc, are well taken.
I would still like to redirect existing wholesale pages to newwholesaledomain.com, primarily due to a desire to make everything as easy as we can for both types of customers. They want to emphasize the retail side but don't want to make it a pain for wholesale customers in the process.
So I'm inclined to redirect retail pages to newretaildomain.com and wholesale pages to newwholesaledomain.com. All page by page of course. Since the currentdomain.com home page will redirect to newretaildomain.com, we would put a notice on the new home page for our wholesale customers, pointing them to newwholesaledomain.com.
How does that sound? I think you are all correct that I should avoid redirect chains and meta refreshes.
-
I might also send out some... "Tell a Friend" email messages to past clients. They can then forward these to friends who may or may not have purchased in the past, but it will get them nice savings on their first purchase from your new domain.
I would make these offers so good that I don't make much money on them. This is just to get new people to the new domain. I would send them out in batches so my employees filling orders will not be so swamped that they will have trouble giving their normal fast service.
-
It would also be a good idea to plan and announce the move. This can be done by:
-
email and mail to important retail and wholesale clients.
-
before redirecting pages the old domain could include obvious messages to retail and wholesale clients, thanking them for their support, letting them know about the schedule of the move, and asking them to bookmark the new site.
-
inserts in retail shipments
-
special advertising before the move
-
special advertising and email after the move that gives old customers a nice discount when they make their first purchase on the new website.
-
-
Personally. I would not use metarefresh. I don't know how Google will treat it.
If I wanted to keep as much power as possible on the retail site I would have a plain page with my full internal navigation on it. It would also have a very clear message for wholesale visitors, that gives them as much time as they need to read, change their directories, and leave by their own action.
-
Interesting. At first I thought that it isn't a great experience for wholesale customers, but what if we added a meta refresh so that page has a message like... "The content you are looking for has moved. You will be redirected to the new location automatically in 5 seconds. Please bookmark the correct page at newwholesaledomain.com"
-
My first thought was exactly what EGOL suggested. However given the decission that they are dead set on rebranding I would suggest the following.
Split the wholesale site off first, leaving the current domain in place for a transitional period. After a pre-dertmined period of time (however long they feel it necessary for wholesale buyers to get used to the new website), then change the retail side to the new brand, and take full advatange of 301 and change of address.
My thoughts hope it helps,
Don
-
OK... thanks for the details.
In that case. I would build newretaildomain.com. Any pages that have equivalent or near-equivalent content on currentdomain.com would 301 direct page-by-page to newretaildomain.com.
All existing wholesale pages on currentdomain.com would 301 redirect to a new page on newretaildomain.com that explains your new wholesale website and has one outlink to newwholesaledomain.com. This page will keep all of the power of the wholesale pages on your new retail site, which must be competitive in the SERPs.
This maximizes power of newretaildomain.com and directs anyone who follows links to old pages on currentdomain.com to your new wholesale website.
This would be accompanied by multiple email and snail mail announcements to all wholesale clients. Sales agents would be trained how to transition.
-
I like this idea too
-
Thanks EGOL. Unfortunately they are committed to a full rebranding and want a new domain.
-
This is a great question and not easy. I would love to hear some others chime in. My guess is that splitting the pages immediately would be the best. Yes, you would lose the ability to do the change of address, but that really isn't essential. At the beginning, I would keep the content as similar as possible if not identical after the transfer (of course with different internal links).
-
If this was my biz and currentdomain.com is an appropriate domain for selling retail then I would start a brand new wholesale website and give it one link from the "about us" page on currentdomain.com. Any wholesale pages on current domain would redirect internally to the "about us" page. This keeps all of the power of currentdomain.com intact and does not divide it up.
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
-
How do we better optimize a site to show the correct domain in organic search results for the location the user is searching in?
For example, chicago-company.com has the same content as springfield-company.com and I am searching for a general non-brand term (i.e. utility bill pay) and am located in Chicago. How can we optimize the chicago-company.com to ensure that chicago's site results are in top positions over springfields site?
Intermediate & Advanced SEO | | aelite1 -
Domain Migration of high traffic site:
We plan to perform a domain migration in 6 months time.
Intermediate & Advanced SEO | | lcourse
I read the different articles on moz relating to domain migration, but some doubts remain: Moving some linkworthy content upfront to new domain was generally recommended. I have such content (free e-learning) that I could move already now to new domain.
Should I move it now or just 2 months before migration?
Should I be concerned whether this content and early links could indicate to google a different topical theme of the new domain ? E.g. in our case free elearning app vs a commercial booking of presential courses of my core site which is somehow but not extremely strongly related) and links for elearning app may be very specific from appstores and from sites about mobile apps. we still have some annoying .php3 file extensions in many of our highest traffic pages and I would like to drop the file-extension (no further URL change). It was generally recommended to minimize other changes at the same time of domain migration, but on the other hand implementing later another 301 again may also not be optimum and it would save time to do it all at the same time. Shall I do the removal of the file extension at the same time of the domain migration or rather schedule it for 3 months later? On the same topic, would the domain migration be a good occasion to move to https instead of http at the same time, or also should we rather do this at a different time? Any thoughts or suggestions?0 -
HTTPS Login on HTTP Site | 301 or 302 Redirect?
I've searched the forum on this and online and can't seem to find a definitive answer. Some e-commerce sites that are http use a 302 redirect to the https login while other sites use a 301 redirect. I know 302 is generally not recommended but in this case it may make sense. Can anyone advise on the correct practice?
Intermediate & Advanced SEO | | CallMeNicholi0 -
How do you 301 redirect URLs with a hashbang (#!) format? We just lost a ton of pagerank because we thought javascript redirect was the only way! But other sites have been able to do this – examples and details inside
Hi Moz, Here's more info on our problem, and thanks for reading! We’re trying to Create 301 redirects for 44 pages on site.com. We’re having trouble 301 redirecting these pages, possibly because they are AJAX and have hashbangs in the URLs. These are locations pages. The old locations URLs are in the following format: www.site.com/locations/#!new-york and the new URLs that we want to redirect to are in this format: www.site.com/locations/new-york We have not been able to create these redirects using Yoast WordPress SEO plugin v.1.5.3.2. The CMS is WordPress version 3.9.1 The reason we want to 301 redirect these pages is because we have created new pages to replace them, and we want to pass pagerank from the old pages to the new. A 301 redirect is the ideal way to pass pagerank. Examples of pages that are able to 301 redirect hashbang URLs include http://www.sherrilltree.com/Saddles#!Saddles and https://twitter.com/#!RobOusbey.
Intermediate & Advanced SEO | | DA20130 -
Site migration from non canonicalized site
Hi Mozzers - I'm working on a site migration from a non-canonicalized site - I am wondering about the best way to deal with that - should I ask them to canonicalize prior to migration? Many thanks.
Intermediate & Advanced SEO | | McTaggart0 -
Moving low ranking domain
I have a website, that I rewrote great content for, but I recently found that there are many, many links going to the subdomain that may be pulling it down. Has anyone had experience taking down a site and then moving the content to a new site? Will it be considered duplicate content if you completely take the old site down and use rel="canonical" on new site pages? I don't want to lose the good content, but I cannot have it on the current URL with all the bad backlinking (it's a complicated situation, as I need to keep those backlinks which are affiliates). Thank you.
Intermediate & Advanced SEO | | RoxBrock0 -
I run an (unusual) clothing company. And I'm about to set up a version of our existing site for kids. Should I use a different domain? Or keep the current root domain?
Hello. I have a burning question which I have been trying to answer for a while. I keep getting conflicting answers and I could really do with your help. I currently run an animal fancy dress (onesie) company in the UK called Kigu through the domain www.kigu.co.uk. We're the exclusive distributor for a supplier of Japanese animal costumes and we've been selling directly through this domain for about 3 years. We rank well across most of our key words and get about 2000 hits each day. We're about to start selling a Kids range - miniature versions of the same costumes. We're planning on doing this through a different domain which is currently live - www.kigu-kids.co.uk. It' been live for about 3-4 weeks. The idea behind keeping them on separate domains is that it is a different target market and we could promote the Kids site separately without having to bring people through the adult site. We want to keep the adult site (or at least the homepage) relatively free from anything kiddy as we promote fancy dress events in nightclubs and at festivals for over 18s (don't worry, nothing kinky) and we wouldn't want to confuse that message. I've since been advised by an expert in the field that that we should set up a redirect from www.kigu-kids.co.uk and house the kids website under www.kigu.co.uk/kids as this will be better from an SEO perspective and if we don't we'll only be competing with ourselves. Are we making a big mistake by not using the same root domain for both thus getting the most of the link juice for the kids site? And if we do decide to switch to have the domain as www.kigu.co.uk/kids, is it a mistake to still promote the www.kigu-kids.co.uk (redirecting) as our domain online? Would these be wasted links? Or would we still see the benefit? Is it better to combine or is two websites better than one? Any help and advice would be much appreciated. Tom.
Intermediate & Advanced SEO | | KIGUCREW0 -
WWW vs Non-WWW/Moving a site to a new CMS/Redirect all of the previous URLs
We are working on a new design for a website, which is currently on a CMS that has non-seo-friendly URLs. There is no redirection of 'www' to non-www or vice versa, or handling of homepage redirection so there is only one instance of 'home'. To move the site in the future, all of these URLs will have to be redirected to their new, and I hope, seo-friendly counterparts. Is it prudent now to redirect the four home page links so there is only one? and to redirect all non-www to 'www' so there is only one instance of each page? Or should I leave it and redirect all of them when the time comes?
Intermediate & Advanced SEO | | haan_seo0