Welcome to the Q&A Forum

1st of all if the developer says he won't use the 301 then he's one very strange developer it's the basic of frontend development. But that being as it is, 301 is the best and most viable option but you do have a few other:

1. tell GWT your prefered domain.
2. have the devloper make a dynamic rel canonical, something like this (in php)
   ' ?>
   in the above situation he of cause would have to make a function called checkURL to test for if the url begins with http://www and returns the right formatted version. and tell GWT what domain you prefer.

But again the only right way is a 301 and it's ridiculously simple to make.

We all know that some of the link juice dies with 301's but I suspect that with a 302 you would keep the link juice.

to make a test I guess you would have to make two pages, with different gibberish on them and then place the keyphrase 2 times on the same char positions (on in the beginning of the document and one at the end.) on each page, but otherwise exactly the same (title exc..). that way we can rule duplicate content out.

I mean something like this:

page 1:

<title>key-phrase bla bla</title>
asd fgh key-phrace jhjd hjd lkd skl ælkjh ghsd sdf fsd key-phrase asd

page 2:

<title>key-phrase poi ert</title>
dsa qwe key-phrace kjhg tyu poi ert mnbvc asdf qwe tyu key-phrase qwe

hope I made sence

The quick response to this, is that with 301 your fairly sure that all bots (not only google/Bing) will understand and apart from that it's way easier to manage the 301's then it is to manage rel's. Both should work without a problem but there are allot of pitfalls with rel's fore instance it's possible  to make an infinite loop with rel's.

it could be any one out of the following 3 scenarios.

1: The page in question was moved at some point and since the CMS still accepts the old URL, when google re-visits the old URL it still finds it. So in this scenario it will find both the old URL and the new URL and index both.

2: google hasn't revisited the page for a long while but it is still in it's index, even though it would get a 301 by the CMS when it visits the page. Can be easily fixed by going to webmaster tools and ask it to remove it from the index.

3: there are still links to the old URL either on site or off site and since the CMS doesn't 301 the oid page it will index it again with a new URL.

4:the page still exists in the CMS because of some strange setting or equivalent in the CMS.

as mentioned before the easy fix is to use a robots.txt and deny access to the page and ask google to remove it from it's index. the better fix is to find the problem in the CMS and solve it. a midway fix could be to 301 it in the .htaccess or equvilent on an ISS server.

hope it helped

I have come across this sort of issue a gazillion times + infinite.. almost all of our clients seem to have dub cont problems of one kind or another

but often it is different things that is the problem. But I'm afraid that I can't point you in the right direction, since I have no experience with your CMS. To be able to do that I would need to have access to the site itself. (since I don't know the CMS.) My advice would be to get a developer on the issue or to grab hold of the support for the CMS (if any.)

Well it kinda have to be in the CMS, since it has 2 different paths.. But you could fix it by going to the .htaccess (if you have access and redirect it to the right URL and make a robots.txt and disallow access to the page.

if the page has been moved to a new location theres a good chance that the CMS is setup to remember the old URL and show the page. This is indeed a problem, but a potential problem with the CMS.

Go to webmaster tools and ask them to delete the dublicate from thier index.

You specific problem could originate from a ton of different problems and it is kinda har to fix without direct access to everything. What CMS is it your using?

cabbagetoe is right, and so is Ryan:
Repeating the keywork fraces too many times will seem spammy. Personally I would go for something like:
size 9 work shoes | buy cheap work shoes at greatshoes.co.uk
or
buy cheap work shoes | greatshoes.co.uk | size 9 work shoes
all depending on if the brand name is vital. it's kinda trial and error what will work for one site might not work for another. And note that I included a call to action in the title.
Whether u use | - _ or whatever in you title will have the same effect in google. It will ignore them. you could for that matter use a . or a , whatever you chose just bare in mind that you need to make the title easy to read for the end consumer. And you should modify the page title and experiement to find out what generates the most clicks. If you notice your bounce rate jump but and your CTR do the same, then you have a title that generates allot of clicks but the content on the page isn't what the consumer expects or it a bad design or... (could be a gazillion things.)
What I'm trying to say is that there is not one winning strategy, you need to experiment and find out what works for you.

be careful when optimizing for both, you might end up in a situation where it will look like keyword spamming. I personally wouldn't optimize for both in the page title, just the primary. And then optimize for the secondary and the primary one in the H1,H2 to Hwhatever..

You don't want to look like a spammer.

Google / Bing will understand that your plural keyword is probably the same. But it will rank you better if you optimize for the exact match key-phrase. So my advise would be to keep focus on the one with the most searches and mention the other a few times. That way you get both, but make sure that the language is something that makes sense and reads well.

I would never recommend multiple domains for the same content. it will generate duplicate content and will harm you more then help you.

I think you should do the following, check the IP look it up and then ASK! the user if he/she wants to go to the Australian version or stay at the American version. Or maybe have dynamic content that makes the user aware of the Australian office.

I would personally have all of the TLD's point to different sites with different content. That way you can GEO target, have the sites located localy and use local TLD's all of witch will help you out greatly in your SEO efforts.

Here's to hoping my reply made sense

There are other SE's out there then google and you don't want to loose that traffic, so as Ryan stated you can't fix it in GWT.

2 things you should keep in mind about with and without www:

• how many pages does google have indexed with and without
• how many links do you have that points towards www vs non-www.. this one is important since not all of your PR will get passed on after a 301. Most but bot all of it

hope it helped

Right back at you Ryan, good point

Ryan is clearly less lazy then me just a short remark to the internal linking:

use relative paths and you will never have to worry about it.

meaning use: /images/someImg.jpg instead of www.yourdomain.com/images/someImg.jpg

crowsnest they did ours

the site should work even though you google translate it. and you can see the portfolio here:

short answer: yes

actually it will affect SEO in a positive way, since google will notice that the hosting server is located in the region it targets. BUT and there are several:

• You will have unhappy visitors, what if I visited your site while I was travelling in Spain, since I don't understand a word Spanish I wouldn't be a very happy camper.
• Google will only see one of your languages since it has a fixed IP.

The right way to do it:

• have a separate domain name for each country. Eg: Danish target group .dk English UK .co.uk English US .com German .de and so on
• Have a well written (translated by a translator not google translate) version for each language
• Give the visitor the opportunity to select the language he/she want to read, don't force them, guide them.
• have your different languages hosted in the target areas.

as i said you need a requirements specification paper and a developer to get a real idea of the time / money involved in a project like yours.

And from what I hear from you so far most of the site is already made, meaning it's a question of building on top of an existing platform.

But I'm shooting in the dark here without a detailed spec it's impossible to guess on how long it would take, well ok you could guess but you would most likely be wrong

I completely agree with ennovation..

You most likely won't find a boxed solution that will work for you. You need a custom solution. Get your developers on the job.