Welcome to WebmasterWorld Guest from 18.104.22.168
Forum Moderators: open
I just relaunched a medium sized industry site. In the redesign process, we took the opportunity to run all texts by an external lector to check for spelling and phrasing. He found quite a lot of issues along these lines:
- tiny blue widgets
Spellings on the old site - usually different spellings mixed on a single page:
- tiny-blue widgets
- tinyblue widgets
- tiny blue-widgets
- tb-widgets (term sometimes used in my industry)
- tb widgets
- widgets which are tiny and blue
- tiny widgets in blue
- tiny blue widgest (typo inserted deliberately)
Now I have the problem that my site is 100% gramatically correct, but that pages are dropping from their (previous) top positions because the keywords, which users actually type in, are not found any more.
We have some compensation because all the old keywords are covered by AdWords, but having the pages back in top positions would be better.
The situation is even a little more complex since my native language uses special characters and we mixed writing the keywords with these characters and in their internationalized form without the special characters. The lector - of course - replaced them all into the correct form WITH the special characters.
Any best practice here? Or drop the correct spelling again and mix the most popular variants on the different pages again?
I've been thinking about my reply and wanted to add a couple of things.
I've never done what I suggested because 1) I'm pretty busy with other things and 2) I think they would be considered "doorway" pages (that's what they are) and could get your gramatically correct site in trouble.
For sure don't do 301s or auto refreshes.
Still, you can help people who don't spell very well. They really are looking for your site.
The linking of these pages are important, they need to be interlinked and linked with the rest of the site. You will find that these pages do indeed create traffic.
What's the visitor psychology if he does not come from a search engine but from the normal browsing of my site? Wouldn't he be "schocked" to find flat html pages all of a sudden?
How unique should the content be? There's only so much to say about blue widgets, and it's all on the "correct" page...
I link to these pages from my index page, but the links are as discreet as I can make them (not hidden, no 1*1 pixels, normal href links with keywords as linktext).
It is my philosophy that each page has a minimum of 3 links pointing to it, so I create a “cloud” of pages croslinked.
I use these flat html pages for optimization with misspellings, dynamic pages, flash sites and graphic heavy sites. I feel that it is a good compromise between the need for using pages that are relative easy to optimize and the disadvantage in having pages that fall outside your normal technical design
"Maybe you call it a WIDGETT or perhaps your favorite misspelling is WIDGETTE. Some people even use WIDGIT. But no matter how you spell it (or misspell it) our widgets are the best in the industry"...etc.
Again an example:
Correct hyphenation in my language:
Popular search terms with incorrect hyphenation:
- tinyblue widgets
- tinieblue widgets
Note that the last three samples are NOT(!) misspellings in my native language, but simply alternative but still correct ways of writing the word.
It's always a tough call when you need to make a decision on capturing variations on your keyword phrases. It is definitely easier to approach when you are targeting two words that could be searched as one string (bluewidgets vs. blue widgets).
<title>Blue Widgets - Best Prices for BlueWidgets</title>
The above is a fairly crude example but it gives you an idea.
Now, when it comes to misspellings you have to to be a little more creative. You can blatantly misspell the phrase or, you can accidentally misspell it. ;)
You may even include a paragraph at the beginning of the page that briefly describes the correct spelling of the term and then list all of the incorrect spellings. Problem is, this could be seen as somewhat unprofessional depending on the industry. But, you have the other side where some will appreciate the fact that you've provided them with the correct spelling.
So, what do you do? You break down content to its least common denominator. Then you focus on where you are going to target variations of spelling and also misspellings. The more pages you have about bluewidgets and blue widgets, the more areas you have to work with.
P.S. With the major search engines now using stemming, the one word vs. two word keyword phrases may not be a factor anymore.
You also have... Did you mean: bluewidgets
Actual mis-spellings are a minor component of my problem. I mentioned already that I'm not talking about English, but about a European language with special characters in it. There IS an official way how to write these special characters in 7-bit charsets - so I already have TWO possible spellings. And then there is the issue with the blanks/spaces, which DO show different SERPS for my queries.
In your title-example you more or less described the old state of my pages. The more I think about it the more I'm inclined to revert back to it.
Now stemming. Mhmm. Will it work with non-English pages? I have used lang-tags, so the spiders "should" know it's not English...