<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: US v British/Australian English in Website Copywriting</title>
	<atom:link href="http://www.divinewrite.com/blog/copywriting/us-v-britishaustralian-english-in-website-copywriting/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.divinewrite.com/blog/copywriting/us-v-britishaustralian-english-in-website-copywriting/</link>
	<description>All things copywriting - and quite a bit about SEO</description>
	<lastBuildDate>Tue, 31 Jan 2012 22:04:21 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Glenn Murray</title>
		<link>http://www.divinewrite.com/blog/copywriting/us-v-britishaustralian-english-in-website-copywriting/comment-page-1/#comment-32369</link>
		<dc:creator>Glenn Murray</dc:creator>
		<pubDate>Tue, 01 Dec 2009 06:15:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.divinewrite.com/blog/2008/10/17/us-v-britishaustralian-english-in-website-copywriting/#comment-32369</guid>
		<description>Hi Eric. Sorry for my delay in responding. I had some issues with my blog&#039;s comments. 

You&#039;re right. If you have different domains for each localised version (i.e. yoursite.co.uk for the UK version and yoursite.com for the US version), you&#039;d have all the duplicate content issues. You can, however, reduce the risk of duplicate content issues by specifying (in Google&#039;s Webmaster Tools) which domain is for which location. Then the most appropriate page should usually be returned.

Probably the bigger problem is that you end up splitting incoming links between each of your domains, thereby diluting domain popularity of each individual site. 

There are two ways around this: 1) Use a sub-domain (i.e. uk.yoursite.com) and you reduce that dilution of domain popularity somewhat. 2) You could use a sub-folder (i.e. yoursite.com/uk/) and you eliminate dilution altogether (all inbound links contribute to your domain popularity). Unfortunately, however, these approaches aren&#039;t that intuitive for users. Also, with both of these options, you can&#039;t host each localised version in the appropriate country, which can be important.

More on all of that here: http://www.youtube.com/watch?v=6hSoXutuj0g&amp;feature=player_embedded#t=700 and here: http://www.seomoz.org/blog/seo-guide-international-versions-of-websites. 

Cheers.</description>
		<content:encoded><![CDATA[<p>Hi Eric. Sorry for my delay in responding. I had some issues with my blog&#8217;s comments. </p>
<p>You&#8217;re right. If you have different domains for each localised version (i.e. yoursite.co.uk for the UK version and yoursite.com for the US version), you&#8217;d have all the duplicate content issues. You can, however, reduce the risk of duplicate content issues by specifying (in Google&#8217;s Webmaster Tools) which domain is for which location. Then the most appropriate page should usually be returned.</p>
<p>Probably the bigger problem is that you end up splitting incoming links between each of your domains, thereby diluting domain popularity of each individual site. </p>
<p>There are two ways around this: 1) Use a sub-domain (i.e. uk.yoursite.com) and you reduce that dilution of domain popularity somewhat. 2) You could use a sub-folder (i.e. yoursite.com/uk/) and you eliminate dilution altogether (all inbound links contribute to your domain popularity). Unfortunately, however, these approaches aren&#8217;t that intuitive for users. Also, with both of these options, you can&#8217;t host each localised version in the appropriate country, which can be important.</p>
<p>More on all of that here: <a href="http://www.youtube.com/watch?v=6hSoXutuj0g&#038;feature=player_embedded#t=700" rel="nofollow">http://www.youtube.com/watch?v=6hSoXutuj0g&#038;feature=player_embedded#t=700</a> and here: <a href="http://www.seomoz.org/blog/seo-guide-international-versions-of-websites" rel="nofollow">http://www.seomoz.org/blog/seo-guide-international-versions-of-websites</a>. </p>
<p>Cheers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Mayfield</title>
		<link>http://www.divinewrite.com/blog/copywriting/us-v-britishaustralian-english-in-website-copywriting/comment-page-1/#comment-32319</link>
		<dc:creator>Eric Mayfield</dc:creator>
		<pubDate>Mon, 30 Nov 2009 02:40:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.divinewrite.com/blog/2008/10/17/us-v-britishaustralian-english-in-website-copywriting/#comment-32319</guid>
		<description>So my question is what do you guys exactly think is the best middle ground? I&#039;m in this exact quandary at the moment and would love to have localized versions. My biggest problem is that if one version is US optimized and one UK optimised ;0) I&#039;ll still suffer from Google due to all the other duplicate content. So really each version would need to be unique in at least content if not &quot;look and feel&quot;. I feel this would be a great subject to be discussed more in-depth.</description>
		<content:encoded><![CDATA[<p>So my question is what do you guys exactly think is the best middle ground? I&#8217;m in this exact quandary at the moment and would love to have localized versions. My biggest problem is that if one version is US optimized and one UK optimised ;0) I&#8217;ll still suffer from Google due to all the other duplicate content. So really each version would need to be unique in at least content if not &#8220;look and feel&#8221;. I feel this would be a great subject to be discussed more in-depth.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

