A Hyphenated Future?

[tolkein]

I have this weird feeling that most domain names will be hyphenated in the future. It certainly makes sense because search engines read "wireless-email" the same as "wireless email" - most of .de domains (German) are hyphenated.

Opinions?

 

[Grrilla]

IMO, hyphenated names are most often registered as a compromise- the non-hyphenated name is taken and someone just can't live w/o the term. In some cases, this works out, but more often than not, it doesn't.

There are definitely some good hyphenated names that have been branded and that have the exposure and are seen frequently enough, that when people think of them, they visulaize a hyphenated name. But most companies w/ that kind of clout, also own the non hyphenated version, ie U-Haul, Q-tip.

There are also some good looking tech-names that are hyphenated, and what carries the day for these domains, are good corresponding websites that people want to go to and, if they mistakenly go to the non hyphenated site, they quickly make the adjustment and retype the address.

Another, area where hyphenated names are the preferred choice, is where the word combinations are confusing to both user and SE, as Adotible just pointed out.

I, personally, like L-L, N-L, and N-N names, (the only possibility for a two character- hyphen excluded- name in info, biz and us). I have k-o, q-q, r-f, s-w, v-8 , v-p and the like, and plan on holding onto them, until the word gets out and the market for themcatches up.

Some "i-" and "e-" names, particularly when the attached keyword can borrow, (legally), some of the spillover from a successful name that is similarly themed, (ie i-podcast), or when the keyword is *very* strong and can carry the extra weight, (ie E-Loan). But generally, just throwing on an "i-" or "e-" up infront of a name, (w/ or w/o the "-"), for the purpose of capturing a word, is a bad strategy.

Another use of hyphens, that I've heard works well, is to seperate a highly searched keyword combination, (that is unavail), for SEO purposes, (because the SE disregards the hyphen when pulling up results), but I don't have enough experience w/ these domains to be very definitive on the subject.

Without a hyphen, the SE's could potentiall read it as "Student sExchange". You'd either be listed in the wrong SE lists, or maybe even be banned.

Those are what I call "double dippers". If one approach doesn't work, you've always got a back-up. Doesn't work so well w/ the example you are using, but replace "student" w/ "male", and there's a whole different spin to it.

 

[ThreeD]

I make it simple, when my company starts a new project we register the normal domain name and the hyphenated version that way you get rid of potential immitations and you can redirect any traffic from the hyphenated site to the main domain.

 

[Grrilla]

I make it simple

I like simple, whenever possible. In the scenario you describe, it is simple because a) you have a clearly defined objective and b) both versions are available for your name of choice. However, if one of the versions in unavail and the objective is not as straight forward as site development, (ie the terms quality as it relates to ease of SEO and monetization), it isn't always possible to keep it that simple. It starts to get more complex when weighing name values for other purposes, (ie the non hyphened is unavail for your client and you have to start looking for alternatives and their relative values.)

"Is the name strong enough for us to go w/ the hyphenated version alone, or should we start looking at some other alternatives, and, if we do, what is the strength of these alternative names when compared to going the hyphenated route w/ the name that we really like?"

 

[ThreeD]

In the scenario you describe, it is simple because a) you have a clearly defined objective and b) both versions are available for your name of choice.

b) has not always been true. It has happened on occasion that we had to buy the hyphenated domain from somebody else, just to ensure that nobody would immitate our work or steal any traffic. I guess we've been lucky so far because we have NOT encoutered any individual who refused to sell his domain name, wether it was hyphenated or not. Some people have been difficult at times, but we've always come up with a solution so far.

"Is the name strong enough for us to go w/ the hyphenated version alone, or should we start looking at some other alternatives, and, if we do, what is the strength of these alternative names when compared to going the hyphenated route w/ the name that we really like?"

We've made it a rule that we never go for the hyphenated version alone, you end up loosing too much traffic to the non-hyphenated domain name even with the right promotion. When we tell our clients that, they usually agree with us. Ofcourse it can be difficult to find alternative names with the same strength and brandability, but when you sit down with your clients and brainstorm your options you will most likely find a good replacement. It could be that you'd have to cash out a little more if one of the domains is registered but if the owner is willing to sell and the price is reasonable, in general the clients give you the go-ahead signal.

However, when we DO have to come up with alternative names our clients are usually satisfied with the solution we put on the table. The domain name may not be as strong and representable, but with some extra promotion / marketing that problem can be balanced to some degree.

 

[Grrilla]

I've had a good deal of experience working in the B2B group dynamic, but not in the area of domain names. Appreciate the inside peek at the developer-client relationship being applied, specifically, to domain names. Interesting stuff, ThreeD.

So, from the sellers POV, *if* one were to learn that an offer was coming from a company that had regged the hyphenated version of a name, might there be a little bit of added leverage in negotiations?

 

[tolkein]

Wow, my thread's reopend! I must've been missing in action for too long

 

[ThreeD]

I've had a good deal of experience working in the B2B group dynamic, but not in the area of domain names. Appreciate the inside peek at the developer-client relationship being applied, specifically, to domain names. Interesting stuff, ThreeD.

So, from the sellers POV, *if* one were to learn that an offer was coming from a company that had regged the hyphenated version of a name, might there be a little bit of added leverage in negotiations?

Sorry for the late reply Grrilla (my ISP had some inet problems this week and I was away for a couple of days so I didn't get a chance to check this thread until today) Glad you appreciate the feedback

If one as a seller is contacted by a company who is interested in buying your domain(s) I would definately say there is more space for negotiation and the chances of getting a higher price for the domain is also very realistic.

Companies in general have more cash to splash out, especially if they are working for companies where money really isn't an issue. If they have a product they want to put on the market, whether it has to do with promotion or branding, they do not want to (and can't afford to) loose traffic or potential buyers/visitors. It's vital for that company to secure success by covering the whole range of domain names (with and without hyphens), not only because of traffic but also to prevent other people from duplicating their work or stealing traffic. We tell our clients this every single time, there will be people out there trying to take advantage of the situation - so it is important for the company to secure their product/brand in every possible way - even if they have to spend more $$$. The first step is to cover the domain names involved - and I've yet to experience a company that hasn't agreed with us.

So yes, if one were to learn that a company is about to put up an offer for a domain name, I would do a little reasearch and check what their plans may be. Check if they own other domain names that are similar, also check out their website to see if you can find any interesting information. You may be lucky and get a lot more $ than you had hoped for - especially if we're once again talking about companies where money isn't an issue

 

[Grrilla]

It's vital for that company to secure success by covering the whole range of domain names

That can end up being quite expensive for the little guy, as I've learned, particularly, if you are working w/ a concept and not a particular company name. I'm in the early stages of development of a project that involves a novel activity that can be employed w/ several different themes. I started "tying up" the market about 3-4 mos ago w/ the initial registration of about 50 of the most pertinent terms and theme combinations. I obviously, won't be using them all as sites, (most will be pointers), but I wanted to usurp potential competition while I await a utility patent. At last count, I had surpassed the 100 the mark, and still haven't touched on what the topic of this thread is- hyphenated names. Which reminds me... :hehe: