- Impact
- 177
Instead of owning keyword.com (though never turn it down if you can get it) - for a new project I'm trying the TLDs that make structural sense - e.g.
keyword.web for the website
keyword.chat for the chat interface (if present)
keyword.radio for the Internet Radio (if present)
etc.
keyword.net then would be the one used for infrastructure (subdomains possibly for DNS, SMTP, CDN, Administration, et.)
The idea being that all a customer has to work at remembering is keyword. Then it is easy for them to decide website / chat / radio station / etc. which will show up as they start typing keyword from their browser history. This way they don't have to remember what subdomain a particular service is on.
For it to work, one has to obtain keyword on the relevant gTLDs that are descriptive of the services being offered, but I really suspect doing that is a lot less expensive than bidding on keyword.com and probably will be for some time - as well as more user friendly because the TLD describes the service.
keyword.web for the website
keyword.chat for the chat interface (if present)
keyword.radio for the Internet Radio (if present)
etc.
keyword.net then would be the one used for infrastructure (subdomains possibly for DNS, SMTP, CDN, Administration, et.)
The idea being that all a customer has to work at remembering is keyword. Then it is easy for them to decide website / chat / radio station / etc. which will show up as they start typing keyword from their browser history. This way they don't have to remember what subdomain a particular service is on.
For it to work, one has to obtain keyword on the relevant gTLDs that are descriptive of the services being offered, but I really suspect doing that is a lot less expensive than bidding on keyword.com and probably will be for some time - as well as more user friendly because the TLD describes the service.
