PDA

View Full Version : Keywords separated by hyphen in URL - Better Ranking?


northwest
06-29-2004, 09:24 PM
Hi all,

I'm a newbie... Is it better to have keywords seperated by hyphens or underscore in URL? Does it have better ranking? For example:

1. computerparts.com
2. computer-parts.com
3. computer_parts.com

Personally, I would like to have #1 because it looks better (professional) and easy to remember and type. But do search engines rank them differently?? IS there any importance of having seperated keywords in the URL?

Thanks

David Wallace
06-29-2004, 09:56 PM
If you are referring to the main domain name, then no, there is no benefit separating them out. Also, FYI, you cannot purchase a domain with underscores.

As far as file names, Google at least has admitted that they recognize hyphens as word separators whereas underscores are ignored. Therefore, computer-parts would be seen as " computer parts" whereas computer_parts would be seen as "computerparts".

northwest
06-29-2004, 11:40 PM
Thanks for the quick response. Yes, I was referring to the main domain name. So you are saying that the filenames with seperated keywords are helpful so I am assuming that the subdomain name with seperated keywords can be helpful.

hard-drive/computerparts.com points to computerparts.com/hard-drive.html

The above may be better than

harddrive/computerparts.com points to computerparts.com/harddrive.html

Thanks again

dannysullivan
06-30-2004, 05:51 AM
I'd also recommend you look at these two good threads:


Hyphenated URLs (http://forums.searchenginewatch.com/forum/showthread.php?t=87)
SEO and file names (http://forums.searchenginewatch.com/forum/showthread.php?t=257)

David Wallace
06-30-2004, 12:34 PM
So you are saying that the filenames with seperated keywords are helpful so I am assuming that the subdomain name with seperated keywords can be helpful.
Not really saying that at all, only stating the difference between hyphens and underscores and how Google at least sees them.

I don't think what file names are called makes that much of a difference to even worry about it. I just name files logically with no real worry about whether they are going to help me SEO wise or not.

northwest
06-30-2004, 02:32 PM
Thanks for the response. I read the other 2 threads with the same question. very helpful.

traian
09-23-2004, 05:02 AM
Here's official Google APIs guideline:

Special Characters

By default, all non-alphanumeric characters that are included in a search query are treated as word separators.

The only exceptions are the following: double quote mark ( " ), plus sign ( + ), minus sign or hyphen ( - ), and ampersand ( & ).

The ampersand character ( & ) is treated as another character in the query term in which it is included, while the remaining exception characters correspond to search features listed in the section below.


I hope it helps

seomike
09-23-2004, 02:47 PM
Here's official Google APIs guideline:

Special Characters

By default, all non-alphanumeric characters that are included in a search query are treated as word separators.

The only exceptions are the following: double quote mark ( " ), plus sign ( + ), minus sign or hyphen ( - ), and ampersand ( & ).

The ampersand character ( & ) is treated as another character in the query term in which it is included, while the remaining exception characters correspond to search features listed in the section below.


I hope it helps

that's for querying the API. People don't do searches for real-estate-for-sale which the above explains that in that case a - is not a word seperator. This has nothing to do with url or file name.

traian
09-23-2004, 02:55 PM
that's for querying the API. People don't do searches for real-estate-for-sale which the above explains that in that case a - is not a word seperator. This has nothing to do with url or file name.

Yes indeed. But that gives you a clue. Besides:

Wednesday, August 04, 2004

Greets from GoogleGuy!
Some other Googlers have stopped by to introduce themselves, so it seems appropriate to say hello. Many Google Blog readers may not have heard the story of how GoogleGuy got started, so forgive this bit of historical rambling.

I'm a Google engineer. About three years ago, I was waiting for a program to finish compiling, and I was reading what people online were saying about Google. I remember seeing a question from a site owner about how to structure his site for better crawling, and thinking it would be great if a Googler could just pop by to answer technical questions like that. And then I thought, I'm a Google engineer. I can answer technical questions like that. So I did. Since then, I've managed to post around 2,000 messages in various web forums, setting the record straight whenever possible.

Of course, I had to have an online nickname. What if I got sick, or needed to take a break? I needed a handle that someone else could step into if necessary. After not a lot of consideration, GoogleGuy seemed just right. My primary inspiration was the Man in Black in The Princess Bride. When he returned to Buttercup, he could just hand the reins to a new Man in Black. It didn't bother him that no one knew his true identity:

Fezzik: Why do you wear a mask? Were you burned by acid, or something like that?
Man In Black: Oh no, it's just they're terribly comfortable. I think everyone will be wearing them in the future.

So there you have it. Lately, I've been pretty quiet, but at some point I'll hit the Google blog again to hold forth on, say, which is better in a url: hyphen or underscore.

Later -- but hopefully, soon,

GoogleGuy

P.S. Usually, it's a hyphen.

P.P.S. If anyone knows of a good source of iocaine powder, lemme know. I've spent the last few years building up an immunity to it just in case. But you know how it is: hard to find these days.

Of course you never know who writes these blogs.