When is Registering or Using a .Net Domain a Better Alternative Than it Might Look Like at First Glance?

When is it nice to be a .Net?

[Webwork]

1. When the .Com version of the same (generic) domain is parked.

2. When the domain itself is just a really nice domain.

For example, when it's a domain like:

(State)Attorney.net
(State)Insurance.net
(State Abbreviation)Attorney.net
(State Abbreviation)Insurance.net

What's nice about having the parked .Com domain is that many folks will default to checking the .Net.

What's nice about certain .Net domains is that they are 1) simply so robust in their generic quality; and, 2) their converted lead and/or PPC value is SO high that only a few visits will be all it takes to make the investment pay off.

So, anyone have another reason why or when it's nice to be a .Net? :)

[stever]

When you can parlay it into being a "net" (or indeed an "org") as in your examples above. Opens up possibilities for "community link-building" or "community self-promotion".

[piatkow]

Nice to be a .net?
When it is being used correctly for the site of a network provider.

[mikeyb]

What's nice about having the parked .Com domain is that many folks will default to checking the .Net

Really?
I would never have thought of doing that myself, I would do a search after hitting a parked domain.
I may check the ccTLD for where I am, but generally search.

[Webwork]

I would never have thought of doing that myself

Me, neither or rarely but it's a large numbers game and the numbers of people looking for something is sometimes large. In that case - if you are already in direct navigation mode - all that is required is to delete the .Com and type-in .Net. Easy, right? :)

Piatkow, that's pretty much the rule that I have followed with rare exception - such as those I've described. The rules of exception are high value / high volume traffic, often with a parked .Com version of the same generic phrase.

[edited by: Webwork at 12:41 pm (utc) on May 5, 2009]