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.
Www2 vs www problem
-
Hi,
I have a website that has an old version and a new version. The content is not duplicate on the different versions.
The point is that the old version uses www. and non-www before the domain and the new one uses www2.My questions is: Is that a problem and what should be done?
Thank you in advance!
-
Good luck!
-
Hey,
the non-www version redirect to the old version - I know, pretty poor. But this is a situation I inherited So, I will try to do something because now all the link juice is going to the old version and dilutes because of the redirects.
Thanks for the help guys.
Especially you, Jane
-
Hi,
I doubt you will see too many SEO detriments to this, but that depends on how the site is configured re: the non-www version of the site. If you access http://domain.dk/, what happens? Are you redirected to www.domain.dk, www2.domain.dk, or does one of the two categories' content load on the non-www URL?
Google should simply treat www and www2 as different subdomains. I have not heard of ranking / indexing confusion based on using www1, www2 etc. but it's definitely the usability issue that would really bother me. Definitely good to work on convincing the client to hurry up with the complete redesign so you can get it all back on the www
-
Hi Jane,
I don't think that's possible. The client is a bit conservative in terms of changing the domain URLs. I think we just need to hurry up convincing them to finish the last section redesign. I was just wondering what the consequences now would be because of this www2. - referring consequences for the categories on it.
-
Hi Tihomir,
Is there a way you can rename the subdomains? E.g., name the old design / category something like http://categoryname.domain.dk/ and have the new content on http://www.domain.dk/?
-
Hi Jane,
Thanks for the comment.
The point is that the company, that possesses the website, want for now to leave the old design for this category and move the other two on a new design (which resides in www2). The new categories are on www2 and their tabs from www redirect.
-
Hi Tihomir,
Are you planning to give the remaining category a facelift too?
It would be best to include all three categories under the same subdomain (e.g. the "www." subdomain) and place them in folders, e.g. www.domain.dk/category1, www.domain.dk/category2 and www.domain.dk/category3. www2 isn't technically damaging but it's bad from a usability point of view. It's incredibly unlikely to be remembered, for one, and even more likely to be mistyped as www.
-
Thanks a lot Rickus,
I answered together with Alex's answer
-
Thanks for the response Alex and Rickus,
The point is that the website have three main categories. Two of them had been facelifted and moved to www2.domain.dk. Their tabs on www.domain.dk redirect to www2. The point is that on the www.domain.dk left the first category which is still not redesigned.
So, we basically can't remove any of these 3 categories - we end up with one category on the www & non-www version and with two categories on the www2 version. -
Do you still need the old domain? If not you should make the new website reside at www. or non-www.
Imagine telling people your URL "it's at www2.example.com" - most people don't know anything other than www. so it could cause confusion.
Also, if you have the same content residing at the www. and non-www. versions of your website, the two versions will be conisdered duplicate content so you should make sure only one exists.
-
Hi there Tihomir,
Although the www to www2 differs the .domain.com will still be the same, this will be seen as a duplicate domain in a way by Google or any other search engine. And will definitely damage ranking of your site.
So the best thing to do here is to remove the old site completely or just edit it so that google cant crawl the site if it is a necessity to have the old one live.
Hope this helps
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
-
Solved Should I consolidate my "www" and "non-www" pages?
My page rank for www and non-www is the same. In one keyword instance, my www version performs SO much better. Wanting to consolidate to one or the other. My question is as to whether all these issues would ultimately resolve to my chosen consolidated domain (i.e. www or non-www) regardless of which one I choose. OR, would it be smart to choose the one where I am already ranking high for this significant keyword phrase? Thank you in advance for your help.
Technical SEO | | meditationbunny0 -
Bing Webmaster Shows Domain without WWW
One of our sites shows thousands of 301 redirects due to domain without www in Bing Webmaster under crawl Information page. It’s been like this for a long time. None of the internal pages have domain without www, it was tested through Screaming Frog. We do have www preference set in google webmaster, but unfortunately bing doesn’t have this option. We also specify URL with www preference through structural data, but that still doesn’t help. Did anyone have similar problems with Bing, and how did you resolve it?
Technical SEO | | rkdc1 -
Best Practice for www and non www
How is the best way to handle all the different variations of a website in terms of www | non www | http | https? In Google Search Console, I have all 4 versions and I have selected a preference. In Open Site Explorer I can see that the www and non www versions are treated differently with one group of links pointing to each version of the same page. This gives a different PA score. eg. http://mydomain.com DA 25 PA 35 http://www.mydomain.com DA 19 PA 21 Each version of the home page having it's only set of links and scores. Should I try and "consolidate" all the scores into one page? Should I set up redirects to my preferred version of the website? Thanks in advance
Technical SEO | | I.AM.Strategist0 -
Duplicate Content Issue WWW and Non WWW
One of my sites got hit with duplicate content a while ago because Google seemed to be considering hhtp, https, www, and non ww versions of the site all different sites. We thought we fixed it, but for some reason https://www and just https:// are giving us duplicate content again. I can't seem to figure out why it keeps doing this. The url is https://bandsonabudget.com if any of you want to see if you can figure out why I am still having this issue.
Technical SEO | | Michael4g1 -
Tool to search relative vs absolute internal links
I'm preparing for a site migration from a .co.uk to a .com and I want to ensure all internal links are updated to point to the new primary domain. What tool can I use to check internal links as some are relative and others are absolute so I need to update them all to relative.
Technical SEO | | Lindsay_D0 -
Having www. and non www. links indexed
Hey guys, As the title states, the two versions of the website are indexed in Google. How should I proceed? Please also note that the links on the website are without the www. How should I proceed knowing that the client prefers to have the www. version indexed. Here are the steps that I have in mind right now: I set the preferred domain on GWMT as the one with www. I 301 redirect any non www. URL to the www. version. What are your thoughts? Should I 301 redirect the URL's? or is setting the preference on GWMT enough? Thanks.
Technical SEO | | BruLee0 -
Syndication: Link back vs. Rel Canonical
For content syndication, let's say I have the choice of (1) a link back or (2) a cross domain rel canonical to the original page, which one would you choose and why? (I'm trying to pick the best option to save dev time!) I'm also curious to know what would be the difference in SERPs between the link back & the canonical solution for the original publisher and for sydication partners? (I would prefer not having the syndication partners disappeared entirely from SERPs, I just want to make sure I'm first!) A side question: What's the difference in real life between the Google source attribution tag & the cross domain rel canonical tag? Thanks! PS: Don't know if it helps but note that we can syndicate 1 article to multiple syndication partners (It would't be impossible to see 1 article syndicated to 50 partners)
Technical SEO | | raywatson0 -
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