[For those of you looking for the quick fix, skip to SOLUTION]
When you’re building a website, you want to pick a good domain name. What to do once you found that domain name? Most of us are satisfied with just one domain name, e.g. mydomainname.com . But sometimes, you’ll want to play “safe” by preventing other people from buying related domain names.
A few days ago, I wrote a post titled “One Joomla! site, one domain” in which I explained how we bought every ‘alternative’ for ofan-workforce.com to protect our ‘brand’. From a SEO point of view, that’s a bad idea, so we wanted to “rewrite” the domain names to the main domain name, ofan-workforce.com.
I assumed that SH404SEF would do a great job handling this rewriting. I soon learned that it isn’t. SH404SEF goes berserk when multiple domain names point to one Joomla! website. To illustrate what happens, I’ve added an image, which shows you what happened when you’d type www.ofan-workforce.net in your browser.
Result? All the additional domains are worthless. I don’t write this post to complain, I’m writing this post to offer a solution!
The solution(s) I found are both workarounds. you can’t solve this problem in the SH404SEF settings, and updating to the last version won’t do you any good. So if you’ve got this problem, choose one of the solutions below – the really simple one or the more complicated one.
The simple fix (discovered by Joomla-and-more.com
We like simple fixes, because… well, because they’re simple. Our proposed solution is pretty simple; and once again I refer you to the article I linked to. Here’s what to do:
1) Download the Canonicalization plug-in. For your ease of use, we’ve uploaded it to our Skydrive.
2) Install the plug-in.
3) Configure the plug-in. This is pretty simple: Choose the “main” domain name, e.g we chose to use www.ofan-workforce.com
4) Enable the plug-in
Once you’ve done this, the plug-in will help SH404SEF to “behave”. We’d have rather solved this in SH404SEF, but halas. There doesn’t seem to be a way.
CREDIT goes to Sam Moffatt for developing the Canonicalisation plugin.
If you’re not afraid of some coding, you can try the fix you’ll find in this blog. We haven’t tested this fix (we’re pretty happy with our own solution) but some of you might find it useful.
As always, we hope that this post fixes your problems!