Set preferred domain last June but now both www and non. showing

[stuartmcdonald]

After following the canonical domain discussion, last June I set my preferred domain to www.example.com in the Google webmaster tools. While I wasn't having any problems in this regard, I thought it would be a prudent move.

Just now while trying to figure out why I've seen a large and sustained traffic drop, I used the Google site: command and am now seeing more results for .example than what I initially selected -- www.example.com!

Aside from altering the .htaccess file as described in other threads, can anyone suggest anything else I should do to remedy a situation I thought was remidied last June when I did what Google asked?!

tks

[Quadrille]

Google don't (and cannot) guarantee to follow your wish. If, for example, there are folk out there linking toi both forms, then likely both will appear, damaging your ranking.

If YOU link to both forms, then trouble is almost certain.

Either way, your preference in Google will not affect how Y! and M$N work.

301 is, as ever, the wise way to go.

[piatkow]

The OP's reference to "Aside from altering the .htaccess file" suggests that he is using a hosted service that doesn't give him that option.

If a redirect is not on the agenda then all I can think of is that a "base" tag on the page might help.

[Quadrille]

Is it a hosting issue?

If that's the case, then it's time to seriously consider changing hosts. Many hosts have the option as a simple choice, no technical knowledge required. Not having control of your own destiny is no longer acceptable; you will not need to pay a cent more for a decent host.

If it's simply that you do not feel confident working with .htaccess (you are not alone!), and the problem appears to causing real damage, then check around here for detailed advice - but be sure you know your server type before making a move.

[stuartmcdonald]

Before I set the preferred domain in the webmaster tools, i had no results for example.com and all for www.example.com. (we'd always used a "base tag" solution)

It was only after setting the preferred domain, a good six months after setting it in fact, that the example.com results suddenly started showing. That's what left me scratching my head -- I would have assumed that by setting the preferred domain, you could avoid a problem like this happening.

It's not a hosting issue -- I hadn't used the htacess solution as, as the www.example.com vs example.com hadn't been a problem previous to setting the preferred domain, I didn't think it was necessary.

Now I know different!