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 -
How to handle potentially thousands (50k+) of 301 redirects following a major site replacement
We are looking for the very best way of handling potentially thousands (50k+) of 301 redirects following
Intermediate & Advanced SEO | | GeezerG
a major site replacement and I mean total replacement. Things you should know
Existing domain has 17 years history with Google but rankings have suffered over the past year and yes we know why. (and the bitch is we paid a good sized SEO company for that ineffective and destructive work)
The URL structure of the new site is completely different and SEO friendly URL's rule. This means that there will be many thousands of historical URL's (mainly dynamic ones) that will attract 404 errors as they will not exist anymore. Most are product profile pages and the God Google has indexed them all. There are also many links to them out there.
The new site is fully SEO optimised and is passing all tests so far - however there is a way to go yet. So here are my thoughts on the possible ways of meeting our need,
1: Create 301 redirects for each an every page in the .htaccess file that would be one huge .htaccess file 50,000 lines plus - I am worried about effect on site speed.
2: Create 301 redirects for each and every unused folder, and wildcard the file names, this would be a single redirect for each file in each folder to a single redirect page
so the 404 issue is overcome but the user doesn't open the precise page they are after.
3: Write some code to create a hard copy 301 index.php file for each and every folder that is to be replaced.
4: Write code to create a hard copy 301 .php file for each and every page that is to be replaced.
5: We could just let the pages all die and list them with Google to advise of their death.
6: We could have the redirect managed by a database rather than .htaccess or single redirect files. Probably the most challenging thing will be to load the data in the first place, but I assume this could be done programatically - especially if the new URL can be inferred from the old. Many be I am missing another, simpler approach - please discuss0 -
Moving html site to wordpress and 301 redirect from index.htm to index.php or just www.example.com
I found page duplicate content when using Moz crawl tool, see below. http://www.example.com
Intermediate & Advanced SEO | | gozmoz
Page Authority 40
Linking Root Domains 31
External Link Count 138
Internal Link Count 18
Status Code 200
1 duplicate http://www.example.com/index.htm
Page Authority 19
Linking Root Domains 1
External Link Count 0
Internal Link Count 15
Status Code 200
1 duplicate I have recently transfered my old html site to wordpress.
To keep the urls the same I am using a plugin which appends .htm at the end of each page. My old site home page was index.htm. I have created index.htm in wordpress as well but now there is a conflict of duplicate content. I am using latest post as my home page which is index.php Question 1.
Should I also use redirect 301 im htaccess file to transfer index.htm page authority (19) to www.example.com If yes, do I use
Redirect 301 /index.htm http://www.example.com/index.php
or
Redirect 301 /index.htm http://www.example.com Question 2
Should I change my "Home" menu link to http://www.example.com instead of http://www.example.com/index.htm that would fix the duplicate content, as indx.htm does not exist anymore. Is there a better option? Thanks0 -
One domain or two for one company with two lines of business?
Let's say you are building a new company that is involved in two lines of business. Let's for example say one line of business is handling logistics for large conventions where the customer(s) are large corporation and the other line is for wedding planning. Let's say that for certain reasons the owner wants to operate under one brand name, say "PROEVENT" So they will market themselves as PROEVENT Convention Logistics and PROEVENT Wedding Planners. From an SEO perspective, if you have one side of the business doing B-to-B corporate business and the other doing B-to-C do you create two different websites on different domains (proeventconventions.com and proeventweddings.com) with unique design and content, or, do you just use provent.com in order to build better domain authority and on your marketing you use conventions.provent.com that takes you to the convention section of the website and weddings.provent.com takes you to the weddings section?
Intermediate & Advanced SEO | | Jazee0 -
Other domains hosted on same server showing up in SERP for 1st site's keywords
For the website in question, the first domain alphabetically on the shared hosting space, strange search results are appearing on the SERP for keywords associated with the site. Here is an example: A search for "unique company name" shows the results: www.uniquecompanyname.com as the top result. But on pages 2 and 3, we are getting results for the same content but for domains hosted on the same server. Here are some examples with the domain name replaced: UNIQUE DOMAIN NAME PAGE TITLE
Intermediate & Advanced SEO | | Motava
ftp.DOMAIN2.com/?action=news&id=63
META DESCRIPTION TEXT UNIQUE DOMAIN NAME PAGE TITLE 2
www.DOMAIN3.com/?action=news&id=120
META DESCRIPTION TEXT2 UNIQUE DOMAIN NAME PAGE TITLE 2
www.DOMAIN4.com/?action=news&id=120
META DESCRIPTION TEXT2 UNIQUE DOMAIN NAME PAGE TITLE 3
mail.DOMAIN5.com/?action=category&id=17
META DESCRIPTION TEXT3 ns5.DOMAIN6.com/?action=article&id=27 There are more but those are just some examples. These other domain names being listed are other customer domains on the same VPS shared server. When clicking the result the browser URL still shows the other customer domain name B but the content is usually the 404 page. The page title and meta description on that page is not displayed the same as on the SERP.As far as we can tell, this is the only domain this is occurring for.So far, no crawl errors detected in Webmaster Tools and moz crawl not completed yet.0 -
Is it safe to 301 redirect old domain to new domain after a manual unnatural links penalty?
I have recently taken on a client that has been manually penalised for spammy link building by two previous SEOs. Having just read this excellent discussion, http://www.seomoz.org/blog/lifting-a-manual-penalty-given-by-google-personal-experience I am weighing up the odds of whether it's better to cut losses and recommend moving domains. I had thought under these circumstances it was important not to 301 the old domain to the new domain but the author (Lewis Sellers) comments on 3/4/13 that he is aware of forwards having been implemented without transferring the penalty to the new domain. http://www.seomoz.org/blog/lifting-a-manual-penalty-given-by-google-personal-experience#jtc216689 Is it safe to 301? What's the latest thinking?
Intermediate & Advanced SEO | | Ewan.Kennedy0 -
Redirect old .net domain to new .com domain
I have a quick question that I think I know the answer to but I wanted to get some feedback to make sure or see if there's additional feedback. The long and short of it is that I'm working with a site that currently has a .net domain that they've been running for 6 years. They've recently bought a .com of the same name as well. So the question is: I think it's obviously preferable to keep the .net and just direct the .com to it. However, if they would prefer to have the .com domain, is 301'ing the .net to the .com going to lose a lot of the equity they've built up in the site over the past years? And are there any steps that would make such a move easier? Also, if you have any tips or insight just into a general transition of this nature it would be much appreciated. Thanks!
Intermediate & Advanced SEO | | BrandLabs0