Moz Q&A is closed.
After more than 13 years, and tens of thousands of questions, Moz Q&A closed on 12th December 2024. Whilst we’re not completely removing the content - many posts will still be possible to view - we have locked both new posts and new replies. More details here.
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.
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
-
Moving site from www to non www and also hosting to vps what will be the effect?
Hi SEO gurus,
Intermediate & Advanced SEO | | SeoBlogs61
I am trying to move my site from shared hosting to VPS hosting and also moving from www to non www version.
What is the best possible way to avoid any issue and without losing the backlinks.
Is it good or bad to do? URL: https://buylikesservices.com/0 -
Using a Reverse Proxy and 301 redirect to appear Sub Domain as Sub Directory - what are the SEO Risks?
We’re in process to move WordPress blog URLs from subdomains to sub-directory. We aren’t moving blog physically, but using reverse proxy and 301 redirection to do this. Blog subdomain URL is https://blog.example.com/ and destination sub-directory URL is https://www.example.com/blog/ Our main website is e-commerce marketplace which is YMYL site. This is on Windows server. Due to technical reasons, we can’t physically move our WordPress blog to the main website. Following is our Technical Setup Setup a reverse proxy at https://www.example.com/blog/ pointing to https://blog.example.com/ Use a 301 redirection from https://blog.example.com/ to https://www.example.com/blog/ with an exception if a traffic is coming from main WWW domain then it won’t redirect. Thus, we can eliminate infinite loop. Change all absolute URLs to relative URLs on blog Change the sitemap URL from https://blog.example.com/sitemap.xml to https://www.example.com/blog/sitemap.xml and update all URLs mentioned within the sitemap. SEO Risk Evaluation We have individual GA Tracking ID and individual Google Search Console Properties for main website and blog. We will not merge them. Keep them separate as they are. Keeping this in mind, I am evaluating SEO Risks factors Right now when we receive traffic from main website to blog (or vice versa) then it is considered as referral traffic and new cookies are set for Google Analytics. What’s going to happen when its on the same domain? Which type of settings change should I do in Blog’s Google Search Console? (A). Do I need to request “Change of Address” in the Blog’s search console property? (B). Should I re-submit the sitemap? Do I need to re-submit the blog sitemap from the https://www.example.com/ Google Search Console Property? Main website is e-commerce marketplace which is YMYL website, and blog is all about content. So does that impact SEO? Will this dilute SEO link juice or impact on the main website ranking because following are the key SEO Metrices. (A). Main website’s Avg Session Duration is about 10 minutes and bounce rate is around 30% (B). Blog’s Avg Session Duration is 33 seconds and bounce rate is over 92%
Intermediate & Advanced SEO | | joshibhargav_200 -
Move to new domain using Canonical Tag
At the moment, I am moving from olddomain.com (niche site) to the newdomain.com (multi-niche site). Due to some reasons, I do not want to use 301 right now and planning to use the canonical pointing to the new domain instead. Would Google rank the new site instead of the old site? From what I have learnt, the canonical tag lets Google know that which is the main source of the contents. Thank you very much!
Intermediate & Advanced SEO | | india-morocco0 -
Google Is Indexing my 301 Redirects to Other sites
Long story but now i have a few links from my site 301 redirecting to youtube videos or eCommerce stores. They carry a considerable amount of traffic that i benefit from so i can't take them down, and that traffic is people from other websites, so basically i have backlinks from places that i don't own, to my redirect urls (Ex. http://example.com/redirect) My problem is that google is indexing them and doesn't let them go, i have tried blocking that url from robots.txt but google is still indexing it uncrawled, i have also tried allowing google to crawl it and adding noindex from robots.txt, i have tried removing it from GWT but it pops back again after a few days. Any ideas? Thanks!
Intermediate & Advanced SEO | | cuarto7150 -
Two blogs on a single domain?
Hi guys, Does anyone have any experience of having (trying to rank) two separate blogs existing on one domain, for instance: www.companysite.com/service1/blogwww.companysite.com/service2/blogThese 2 pages (service 1 and service 2) offer completely different services (rank for different keywords).(for example, a company that provides 2 separate services: SEO service and IT service)Do you think it is a good/bad/confusing search engine practice trying to have separate blogs for each service or do you think there should be only one blog that contains content for both services?Bearing in mind that there is an already existing subdomain for a non-profit part of business that ranks for different keywords: non-profit.companysite.comand it will potentially have another blog so the URL would look like: non-profit.companysite.com/blogAny ideas would be appreciated!Thanks
Intermediate & Advanced SEO | | kellys.marketing0 -
Domain Redirect and SSL Cert
Hi, When redirecting an entire site to another domain, do you have to maintain the SSL certificate? The SSL expires 3 days before the planned redirect. Thanks in advance.
Intermediate & Advanced SEO | | sofla_seo0 -
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 -
Redirecting one site to another for link juice
I have two sites with same theme - buying cars. I am going remove one of the sites from being crawled permenantly (ie junkthecars.com) and point domian via 301, to another similar theme site (sellthecars.com). The purpose is to simply pass the SEO link juice from one site to the other as we retire junkthecars.com.... Is a forwarding of the domain OK and the best way for the search engines to increase the rank of sellthecars.com (we hate to wast the link work done on Junkthecars.com)? What dangers should I look for that could hurt sellthecars.com if we do the redirect at a simple TLD?
Intermediate & Advanced SEO | | bestone0