{"id":1171,"date":"2015-09-02T21:01:11","date_gmt":"2015-09-03T04:01:11","guid":{"rendered":"http:\/\/www.ultimatewb.com\/blog\/?p=1171"},"modified":"2024-01-29T14:44:47","modified_gmt":"2024-01-29T22:44:47","slug":"why-use-www-for-your-website","status":"publish","type":"post","link":"https:\/\/www.ultimatewb.com\/blog\/1171\/why-use-www-for-your-website\/","title":{"rendered":"Why use “WWW” for your website?"},"content":{"rendered":"

\"www-domain\"<\/p>\n

You have 2 options for the url display of your website – with the “www” in the beginning, or without the “www”, otherwise\u00a0known\u00a0as a\u00a0“naked\u00a0domain”. \u00a0That terminology itself might persuade you to lean towards the “www” version for your website, and it’s actually a pretty good portrayal of the domain not having as much protection from the elements as one with the “www”.<\/p>\n

Naked domains & CNAME records for server traffic redirects<\/h2>\n

So, what makes the “www” domain more protected than the non-www domain? \u00a0Naked domains can’t have CNAME records. \u00a0If you have a large website, with a lot of traffic, with millions of page views per day, you will want to redirect traffic from a failing server to a healthy server using DNS CNAME records. \u00a0The workaround to this would be to run your own server farms, but you will be unable to use such services to their full extent.<\/p>\n

\"Cookie_monster\"Cookies…mmm cookies! Security, speed, and caching…<\/h2>\n

And then there’s\u00a0“cookies”. \u00a0Computer\u00a0cookies are\u00a0small pieces of data that are sent from a website to a user’s web browser, stored for later use, such as customizing the user experience, or logging in users to the website. \u00a0With the naked domain, the cookies get sent to all the subdomains, unlike the “www” domain which only does this if you tell it to. \u00a0Potentially, this could be a security risk<\/a> for naked domains. \u00a0Also, for the naked domain this can mean slower access to the static content, and the caching may possibly not work either. \u00a0 \u00a0The workaround to this access issue would be to buy additional domains just for your static content, like Twitter does. \u00a0(Yes Twitter\u00a0redirects to just twitter.com, did you notice?!) \u00a0If you explicitly share your cookies across your sub domains, for example to implement single sign on across various applications on the sub domains like Google does, you will also need to have additional domain names.<\/p>\n

In Summary<\/h2>\n

So, in summary, if you are planning on having a large, interactive website, it’s better to go with the “www” domain because it can be potentially safer and less problems\/hassle. \u00a0If you just have a static website, just displaying information like Google’s parent company, Alphabet at abc.xyz, you can go with the naked domain and still feel covered. \u00a0Google does redirect its apps, like Google search, to the “www” version.<\/p>\n

We choose to go with www.ultimatewb.com on our website here, and redirect users to this when they just type in ultimatewb.com. \u00a0If you are using UltimateWB software, you get this code included in your .htaccess file. \u00a0You can get the code here:\u00a0WWW or no WWW \u2013 That is the question<\/a><\/p>\n

Are you ready to design & build your own website? Learn more about\u00a0UltimateWB<\/a>! We also offer\u00a0web design packages<\/a>\u00a0if you would like your website designed and built for you.<\/p>\n","protected":false},"excerpt":{"rendered":"

You have 2 options for the url display of your website – with the “www” in the beginning, or without the “www”, otherwise\u00a0known\u00a0as a\u00a0“naked\u00a0domain”. \u00a0That terminology itself might persuade you to lean towards the “www” version for your website, and … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[345,100,336],"tags":[375,799,235,815,82,812,814,816,765,817,813],"class_list":["post-1171","post","type-post","status-publish","format-standard","hentry","category-domain-names","category-web-hosting-2","category-website-security-2","tag-htaccess","tag-alphabet","tag-domain-name","tag-domain-redirect","tag-google","tag-naked-domain","tag-non-www","tag-security","tag-twitter","tag-website-speed","tag-www"],"_links":{"self":[{"href":"https:\/\/www.ultimatewb.com\/blog\/wp-json\/wp\/v2\/posts\/1171"}],"collection":[{"href":"https:\/\/www.ultimatewb.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.ultimatewb.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.ultimatewb.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.ultimatewb.com\/blog\/wp-json\/wp\/v2\/comments?post=1171"}],"version-history":[{"count":6,"href":"https:\/\/www.ultimatewb.com\/blog\/wp-json\/wp\/v2\/posts\/1171\/revisions"}],"predecessor-version":[{"id":4555,"href":"https:\/\/www.ultimatewb.com\/blog\/wp-json\/wp\/v2\/posts\/1171\/revisions\/4555"}],"wp:attachment":[{"href":"https:\/\/www.ultimatewb.com\/blog\/wp-json\/wp\/v2\/media?parent=1171"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.ultimatewb.com\/blog\/wp-json\/wp\/v2\/categories?post=1171"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.ultimatewb.com\/blog\/wp-json\/wp\/v2\/tags?post=1171"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}