Google Analytics and SEO

Written by Benjamin Mangold

Fixing Campaign Tagged URLs for Improved SEO

While attending the 2008 GAAC Summit at the Googleplex Robbin Steif of Lunametrics raised an interesting point regarding URLs that have Google Analytics campaign tags. Robbin pointed out that campaign tagged URLs can adversely effect SEO (Search Engine Optimization) as a result of duplicate content and that the _setAllowAnchor(true) function can be used to alleviate the problem.

Okay, great, but can you repeat that in English?

Basically, Google sees a page on your site and campaigned tagged URL for the same page as actually being two separate pages. Then when we come to SEO, websites and pages can be given lower priority if there is duplicate content.

We have a landing page about being a Google Analytics Authorized Consultant: www.mangoldsengers.com/google-analytics-authorized-consultant

And we have a campaign tagged link to the same page on the Google Analytics partner page that looks like this: www.mangoldsengers.com/google-analytics-authorized-consultant?utm_source=gaac-listing&utm_medium=referal&utm_campaign=google-analytics

Although these are the same page Google sees them as two separate pages, so now the question is how do I fix the problem?

How to Fix Campaign Tagged URLs for SEO

Luckily, Google doesn't index anything after a # in a URL, so basically we need to change this: www.mangoldsengers.com/google-analytics-authorized-consultant?utm_source=gaac-listing&utm_medium=referal&utm_campaign=google-analytics to this: www.mangoldsengers.com/google-analytics-authorized-consultant#utm_source=gaac-listing&utm_medium=referal&utm_campaign=google-analytics

Google does not index anything after a destination anchor (i.e. the #), so now: www.mangoldsengers.com/google-analytics-authorized-consultant and www.mangoldsengers.com/google-analytics-authorized-consultant#utm_source=gaac-listing&utm_medium=referal&utm_campaign=google-analytics will be seen as the same page by Google. No more duplicate content!

Now that you have fixed the URLs, we need to get the campaign variables into Google Analytics. This is simply achieved by using the _setAllowAnchor(true) function that Robbin mentioned at the summit.

Your GATC (Google Analytics Tracking Code) will need to be modified (you will need to replace UA-XXXXXXX-X with your Google Analytics profile ID):

If you have any questions or need help implementing SEO friendly campaign tags for Google Analytics then please get in touch!

Labels: ga.js, Google Analytics, Google Analytics Tips, SEO

Updated Google Analytics tracking code (ga.js)

Written by Benjamin Mangold

Google has updated the ga.js tracking code due to a number of problems Google Analytics users were experiencing. The initial release of the new Google Analytics Tracking Code (GATC) prevented websites from validating, did not publish correctly within Blogger templates and the new code did not work with ASP websites. The updated tracking code solves these problems.

Updated version of the ga.js tracking code:

<script type="text/javascript">
var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
</script>
<script type="text/javascript">
var pageTracker = _gat._getTracker("UA-XXXX-XX");
pageTracker._initData();
pageTracker._trackPageview();
</script>

This updated tracking code does not validate for XHTML Strict websites, however adding CDATA tags solves this problem.

XHTML compliant version of the updated ga.js tracking code:

<script type="text/javascript">
//<![CDATA[
var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
//]]>
</script>
<script type="text/javascript">
//<!--[CDATA[
var pageTracker = _gat._getTracker("UA-XXXX-XX");
pageTracker._initData();
pageTracker._trackPageview();
//]]-->
</script>

Here is a copy of the tracking code before the update for those of you who are interested.

Previous version of the tracking code:

<script type="text/javascript">
var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
document.write("\
\<\/script>" );
</script>
<script type="text/javascript">
var pageTracker = _gat._getTracker("UA-XXXX-XX");
pageTracker._initData();
pageTracker._trackPageview();
</script>

Thank you to Justin Cutroni who posted about the updated ga.js tracking code and Jason Green who provided the XHTML Strict solution.

Labels: ga.js, Google Analytics, new Google Analytics features

New Google Analytics Tracking Code (ga.js) released

Written by Benjamin Mangold

The new Google Analytics Tracking Code (ga.js) is now live. The new tracking code will give you access to new features as they are released, the first new feature will be Event Tracking.

Key features:

Smaller tracking code = faster loading speed
Easier to use
Automatic detection of HTTPS
Required for new features

You will have to replace the legacy tracking code (urchin.js) with the new tracking code on your website. Google has stated that the legacy tracking code will continue to function for at least 12 months from the release of the new tracking code.

The following steps show you how to find the new Google Analytics Tracking Code:

Step 1

Click 'Edit' next to the desired profile.