Turning off a subdomain
-
Hi! I'm currently working with http://www.muchbetteradventures.com/. They have a previous version of the site, http://v1.muchbetteradventures.com, as sub domain on their site. I've noticed a whole bunch of indexing issues which I think are caused by this. The v1 site has several thousand pages and ranks organically for a number of terms, but the pages are not relevant for the business at this time. The main site has just over 100 pages. More than 28,400 urls are currently indexed.
We are considering turning off the v1 site and noindexing it. There are no real backlinks to it. The only worry is that by removing it, it will be seen as a massive drop in content. Rankings for the main site are currently quite poor, despite good content, a decent link profile and high domain authority.
Any thoughts would be much appreciated!
-
This is a fantastic answer, thank you.
-
Sounds like the indexing issues are causing some drops in ranking, even though good based content and domain authority are present.
Also, the .v1 site looks to be a testing platform?Could that be possible? I recently had an issue with an enterprise client site with very similar issues - with multiple testing versions of the domain up and indexable, causing massive amounts of duplicate content, indexed content and indexing issues.
I would plan to assess any content that could me migrated over to the main site from the .v1, and 301 redirect (and rel-canonical) the old .v1 site pages. Keep those in place for a few months to ensure that all the value of the 301 take effect.
By migrating some of this valuable content over (or all of it), just make sure you use both properly executed 301 redirects, and to take it a step further, apply the canonical tag on the .v1 pages with redirects to the exisiting and correct pages on the main domain. This way, we know for sure all any value is being passed.
SIDE NOTE: Having that many pages, indexed content doesn't mean the site will do well. In fact with this poor setup, the site's massive amount of page URL's might be causing more damage. Too many pages will bad page quality scores can and will bring a site down. Plan to migrate the pages or sections of the site to the main domain (that hold the most value), 301 and rel-canonical the other's, and remove the bad pages with little to no value that may be causing site wide damage in search indexing.
In dumping lots of content from the site - redirect those URL's (being dumped) to a helpful 404 page, which will try to salvage any user hitting the page, and redirecting them to back into sections of pages of the site. Also - make sure that page has a useful 'search' option that is clear to allow them to search for something they might have tried to land on through organic indexed content.
Finally, once you see indexing improve and redirect those pages automatically in the SERP's through reporting in weeks or months to come, then you can shut down the old .v1 pages without fear of losing any value you had.
It's a lengthy process and a big project, but the client (and site) should see huge value in the time you are taking to manage it. It will maintain value for the site in the long run and help build a better platform going forward.
Cheers!
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
-
Our subdomain hosts content that can not be optimized (static videos) - should I de-index it?
We host static tours on a subdomain that points to the video tour host. I can not add meta or optimize any of these video pages and there are thousands. Should I de-index the entire subdomain? I am seeing errors for no meta, dup content etc in MOZ reporting. If yes, do I add the Disallow: /subdomain.root.nl/ to the primary domain's website/CMS or in DNS records ? Our web company is saying the no follow needs to be added in DNS but I feel like it should be added to the robots.txt file if SERP's are going to acknowledge the sub is no longer to be crawled and the primary is no longer to be penalized. Thank you so much in advance!
Intermediate & Advanced SEO | | masonmorse0 -
301 Redirecting from domain to subdomain
We're taking on a redesign of our corporate site on our main domain. We also have a number of well established, product based subdomains. There are a number of content pages that currently live on the corporate site that rank well, and bring in a great deal of traffic, though we are considering placing 301 redirects in place to point that traffic to the appropriate pages on the subdomains. If redirected correctly, can we expect the SEO value of the content pages currently living on the corporate site to transfer to the subdomains, or will we be negatively impacting our SEO by transferring this content from one domain to multiple subdomains?
Intermediate & Advanced SEO | | Chris81980 -
Changing URL to a subdomain?
Hi there, I had a website www.footballshirtcollective.com that has been live since July. It contains both content and eCommerce. I am now separating out the content so that; 1. The master domain is www.footballshirtcollective.com (content) pointing to a new site 2. Subdomain is store.footballshirtcollective.com (ecommerce) - pointing to the existing site. What do you advise I can do to minimise the impact on my search? Many thanks Mike
Intermediate & Advanced SEO | | mjmaxwell0 -
Merging two different domains - subdomain or subfolder?
My company has two sites on different domains. We are considering merging the sites into one and keeping only the dominant domain. The dominate site is already a sub-domain of a larger organization so the new sub-domain would be two levels deep. I realize this is a little abstract so below is an example Dominant company site: company.root-domain.com Secondary company site: other-root-domain.com When they merge, everything will be on company.root-domain.com. Should it be other.company.root-domain.com or company.root-domain.com/other Note: The other site has several hundred pages. Both sites have strong authority and link profiles. I want to maintain as much of the value on the other site as possible with the merge.
Intermediate & Advanced SEO | | SEI0 -
Subdomain blog vs. subfolder blog in 2013
So I've read the posts here: http://moz.com/community/q/subdomain-blog-vs-subfolder-blog-in-2013 and many others, Matt Cutts video, etc. Does anyone have direct experience that its still best practice to use the sub folder? (hopefully a moz employee can chime in?) I have a client looking to use hubspot. They are preaching with the Matt Cutts video. I'm in charge of SEO / marketing and am at odds with them now. I'd like to present the client with more info than "in my experience in the past I've seen subdirectories work." Any help? Articles? etc?
Intermediate & Advanced SEO | | no6thgear0 -
Subdomains for US Regions
The company I work for is expanding their business to new territories. I've got a lot of stabilization to do in the region/state where we're one of the most well known companies of our kind. Currently, we have 3 distinct product lines which are currently distinguished by 3 separate URLS. This is affecting the user flow of our site, so we'd like to clean it up before launching our products into the various regions. The business has decided to grow into 5 new states (one state consisting of one county only) — none of which will feature all 3 products. Our homebase state is the only one that will have all 3 products this year. My initial thought was to use subdomains to separate out the regions, that way we could use a canonical tag to stabilize the root domain (which would feature home state content, and support content for all regions), and remove us from potential duplicate content penalization. Our product content will be nearly identical across the regions for the first year. I second guessed myself by thinking that it was perhaps better to use a "[product].root/region" URL instead. And I'm currently stuck by wondering if it was not better to build out subdomains for products and regions...using one modifier or the other as a funnel/branding page into the other. For instance, user lands on "region.root.com" and sees exactly what products we offer in that region. Basically, a tailored landing page. Meanwhile the bulk of the product content would actually live under "product.root.com/region/page". My head is spinning. And while searching for similar questions I also bumped into reference of another tag meant to be used in some similar cases to mine. I feel like there's a lot of risks involved in this subdomain strategy, but I also can't help but see the benefits in the user flow.
Intermediate & Advanced SEO | | taylor.craig0 -
Subdirectory vs. Subdomain
I work for a large franchise organization that is weighing the pros and cons of using subdomains versus subdirectories for our franchisee locations. What are the pros and cons of each approach?
Intermediate & Advanced SEO | | Glassdoctordfw0 -
Mobile Site - Same Content, Same subdomain, Different URL - Duplicate Content?
I'm trying to determine the best way to handle my mobile commerce site. I have a desktop version and a mobile version using a 3rd party product called CS-Cart. Let's say I have a product page. The URLs are... mobile:
Intermediate & Advanced SEO | | grayloon
store.domain.com/index.php?dispatch=categories.catalog#products.view&product_id=857 desktop:
store.domain.com/two-toned-tee.html I've been trying to get information regarding how to handle mobile sites with different URLs in regards to duplicate content. However, most of these results have the assumption that the different URL means m.domain.com rather than the same subdomain with a different address. I am leaning towards using a canonical URL, if possible, on the mobile store pages. I see quite a few suggesting to not do this, but again, I believe it's because they assume we are just talking about m.domain.com vs www.domain.com. Any additional thoughts on this would be great!0