does this mean that although the .co.uk name is 'parked', and all content will actually be served from the .com site it will still appear in the Google UK index?
That's correct. I have not done any studies that would show how a site with multiple locals would show up, so be warned it *may* be an either/or switch. Either you are Canadian or UK, for example. I'm not certain - it's on my "to do" list for research.
One way around this is to create subsites under your main site, and park the country TLD's on different pages. You don't necessarily have to park a domain on the main page - you can park it on internal pages as well. An example of this is if you type in www.calgaryherald.com it will resolve to a subdirectory of http://www.canada.co...rald/index.html
You could just as easily have www.mydomain.ca resolve to www.mydomain.com/canada/ or whatever. This would allow you to have multiple pages catering to multiple countries. I haven't tested it, but I think the default would be that any one particular page would and could only have one country associated with it.The Ginger Surfer:
I don't believe the use of a particular language would trip a country designation. If it did, I would not be happy. An example would be the use of french on a page tripping an assumption that the page is from France - it could also be from Canada, Belgium, or numerous other places.
The best way is to use the country TLD - ie the .de extension. I would perhaps have the german language website as a subdirectory (www.mydomain.com/deutsch/) and then resolve www.mydomain.de to it, rather than the home page.Tonemeister
Good to hear! One way to speed things up is to have a site map that points to all the pages using the .co.uk extension rather than the .com version. That way you are telling the SE that you want all of the pages considered UK, and not just the first one.ALL
Sorry I didn't respond to some of these questions earlier - I honestly missed them somehow