I would only go with a domain hack if the .com is also available. A certain portion of users will type in the .com version, and if you are popular enough, the owner of the .com might be malicious enough to capitalize on it. e.g. http://del.icio.us forwards to http://delicious.com/, but imagine what would happen if they didn't own the .com.
IMHO, building a solid product that people want to buy is more important than your exact domain name.
If you disagree with this philosophy and choose a marketing strategy that depends on getting a strategic domain, you should have your domain in hand early on -- before you announce the product, so everything you have to say about it points to the same URL.
Also, if you're willing to be flexible about renaming the product to match the available domains, you can circumvent the whole mess.
Unless your site is for people who know what a "domain hack" is, you need a .com domain. People in the real world either go directly to the .com version or Google it. They're not going to remember your name or domain name if it's something impossible to remember like iluv.che.er.ios.
Might want to avoid .co -- I have found .co to be problematic for my customers. Because it's so close to ".com", I am constantly explaining "it's .co, no m at the end like .com".
Stick with dot com by prepending or appending words or letters. For example eYoursite.com or getyourApp.com etc..
If you plan to go with a .net or .org, in most cases you will have to include the tld's with your logos, but not with dot.com unless generic.
Also, I don't recommend domains like .io and .ly unless your site is targeted towards devs/techi people. A while ago there was a site: foundat.io/n . That is extreme domain hacking.
15 comments
[ 4.8 ms ] story [ 51.5 ms ] threadAnything that uses something other than a .com in a way that relates to the brand name.
If you disagree with this philosophy and choose a marketing strategy that depends on getting a strategic domain, you should have your domain in hand early on -- before you announce the product, so everything you have to say about it points to the same URL.
Also, if you're willing to be flexible about renaming the product to match the available domains, you can circumvent the whole mess.
If you plan to go with a .net or .org, in most cases you will have to include the tld's with your logos, but not with dot.com unless generic.
Also, I don't recommend domains like .io and .ly unless your site is targeted towards devs/techi people. A while ago there was a site: foundat.io/n . That is extreme domain hacking.