New website branding, differences between http://www and http://
-
Hey Mozers!
We will be creating another brand pretty soon with some pretty cool interactive features and before we start development of the site I was wondering if there are any pros/cons to branding the site sans the www.
For example http://example123.com and http://www.example123.com. I would much prefer to brand it has http://example123.com but I just wanted to check first to see if that would have any negative SEO ramifications.
It seems that it might just be a preference as I looked at Facebook and Twitter and they both do it differently, same with Groupon and LivingSocial.
Looking forward to hearing from you guys!
-
Given that we know there isn't any difference from an SEO perspective it comes down to purely external factors. Some questions to think about...
- Are people going to constantly link to the www version any way?
- In a competitive space is one more eye-catching than the other?
- What's more memorable to the visitor?
-
Yea that was a concern I had going in, but I was thinking about it and in general when people link to different products or areas of the site I would assume they might just go copy the link from the url bar (at least that is what I do).
I wonder if the % is really enough to matter when people link to http://zebraswithhats or http://www.zebraswithhats - no thankfully that is not the domain
-
Oof, massive failure on my part lol, there just so happens to be this "check, this answered by question!" Thanks for pointing it out for me
-
Actually a pretty neat feature of the Q&A forum is that you can mark answers as helpful (which highlights the post in green and gives the person a shiny 3 MozPoints).
There should be a text link saying something like 'This answered my question' with a tick at the bottom of their posts which you can click (at least I think that's how to mark them, I've not asked a question yet :D)
-
More people out there are linking to the www.name version and even if you do the 301 redirect you will still lose some vote %.
Since it's a new brand and you are starting this now you should take your time and consider every aspect from the start and make your call based on all facts.
I always vote for the www version but that, beside the linking and look factor of the url is a personal thing.
-
Definately what I was looking for guys, thank you for the awesomely quick responses! I figured that it wasn't that big of a concern for SEO but since we are starting from scratch I just want to make sure its correct from the start! Tossed you both thumbs up!
-
The only difference is from the user perspective. Search engines treat both versions the same.
What you want to be careful about is maintaining consistency within your site. This is especially true at larger organizations with multiple publishing points. If everyone isn't made aware (and reminded from time to time) of this branding decision, inconsistencies will begin to pop up.
Furthermore, you should be sure to redirect all versions of pages to the option you choose. This is true for both the home page and all other pages. For example, if you choose http://example123.com...
- http://www.example123.com should be 301 redirected to http://example123.com
- http://www.example123.com/whatever should also be 301 redirected to http://example123.com/example123
Finally, be sure to share your choice with all parties that communicate externally. This includes PR, Social Media, Marketing, etc. for inclusion in their posts, your company boilerplate, emails, etc.
-
No difference from an SEO perspective. After the Q&A last year at SMX Advanced with Matt Cutts, I went up and asked him this very question. He said make sure one version redirects to the other, and if it is an existing site, Google will likely display the version with more pagerank. If this site is still in development, when you release it, have all links go to the sans www versions and make sure the www versions 301 redirect to the sans www URL's.
From a branding perspective, it only matters if you plan on displaying the .com on the page or in the logo or something like that. If you plan to display the .com, then sans www. Looks cleaner and just better recognition overall.
If you aren't planning to display the .com anywhere, then it really doesn't matter as hardly anyone outside this industry pays attention to which version of a URL they are on.
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 -
Website URL, Robots.txt and Google Search Console (www. vs non www.)
Hi MOZ Community,
Technical SEO | | Badiuzz
I would like to request your kind assistance on domain URLs - www. VS non www. Recently, my team have moved to a new website where a 301 Redirection has been done. Original URL : https://www.example.com.my/ (with www.) New URL : https://example.com.my/ (without www.) Our current robots.txt sitemap : https://www.example.com.my/sitemap.xml (with www.)
Our Google Search Console property : https://www.example.com.my/ (with www.) Question:
1. How/Should I standardize these so that Google crawler can effectively crawl my website?
2. Do I have to change back my website URLs to (with www.) or I just need to update my robots.txt?
3. How can I update my Google Search Console property to reflect accordingly (without www.), because I cannot see the options in the dashboard.
4. Is there any to dos such as Canonicalization needed, or should I wait for Google to automatically detect and change it, especially in GSC property? Really appreciate your kind assistance. Thank you,
Badiuzz0 -
Www to non-www redirect without loop still necessary?
Hi Guys, My question is: Is it still necessary to redirect www. to non www. version of your website or other way around?
Technical SEO | | gaben
I ask because I feel that Google should be able to read these as the same by now. Thank you in advance.
Gabe0 -
Getting a ton of "not found" errors in Webmaster tools stemming from /plugins/feedback.php
So recently Webmaster tools showed a million "not found" errors with the url "plugins/feedback.php/blah blah blah." A little googling helped me find that this comes from the Facebook comment box plugin. Apparently some changes recently have made this start happening. The question is, what's the right fix? The thread I was reading suggested adding "Disallow: /plugins/feedback.php" to the robots.txt file and marking them all fixed. Any ideas?
Technical SEO | | cbrant7770 -
New website's ranking dropped
Hi, Im working on brand new website i didn't even start my link building yet, just added to local directories i slowly started getting my ranking on 3rd page of Google then few weeks ago my ranking fell for all the keywords so now the website doesn't even rank on 10th page. Its been like this for a few weeks now. Here's the website Screenshot http://screencast.com/t/wDWk8sxLw Thanks for your help
Technical SEO | | mezozcorp0 -
My beta site (beta.website.com) has been inadvertently indexed. Its cached pages are taking traffic away from our real website (website.com). Should I just "NO INDEX" the entire beta site and if so, what's the best way to do this? Please advise.
My beta site (beta.website.com) has been inadvertently indexed. Its cached pages are taking traffic away from our real website (website.com). Should I just "NO INDEX" the entire beta site and if so, what's the best way to do this? Are there any other precautions I should be taking? Please advise.
Technical SEO | | BVREID0 -
Robots.txt to disallow /index.php/ path
Hi SEOmoz, I have a problem with my Joomla site (yeah - me too!). I get a large amount of /index.php/ urls despite using a program to handle these issues. The URLs cause indexation errors with google (404). Now, I fixed this issue once before, but the problem persist. So I thought, instead of wasting more time, couldnt I just disallow all paths containing /index.php/ ?. I don't use that extension, but would it cause me any problems from an SEO perspective? How do I disallow all index.php's? Is it a simple: Disallow: /index.php/
Technical SEO | | Mikkehl0 -
/forum/ or /hookah-forum/
I'm building a new website on Hookah.org. It will have a forum and blog. Should I put them in Hookah.org/hookah-forum/ and Hookah.com/hookah-blog/ or Hookah.org/forum and Hookah.org/blog I think /forum/ and /blog/ are easier for users but am not sure how much adding the word hookah helps with SEO.
Technical SEO | | Heydarian0