Archive | July, 2015

What Is Cross Domain Tracking ?

31 Jul

Cross domain tracking makes it possible for Google Analytics to see sessions on two related sites (such as an ecommerce site and a separate shopping cart site) as a single session. This is sometimes called site linking.

  • How Cross Domain Tracking Works  ?
  • If you implement cross domain tracking on your website, then it is possible for Google Analytics to see this as a single session by a single user. Below is example of working of cross domain tracking :seo

Set up cross domain tracking by modifying tracking code :

  1. Set up a property in your Google Analytics account.
  2. Use the same tracking code snippet and tracking ID from that property for all of your domains.
  3. Edit the tracking code for the primary domain.
  4. Find the create line in the snippet. For a website called com, it looks like this:   ga(‘create’, ‘UA-XXXXXXX-Y’, ‘‘);
  5. Make the following changes to the snippet (the changes you need to make are inbold Green text):   ga(‘create’, ‘UA-XXXXXXX-Y’,‘auto’, {‘allowLinker’: true});
    ga(‘require’, ‘linker’);
      ga(‘linker:autoLink’, [‘com‘] );
  6. For three or more domains :
    Follow the example above, but add the other domains to the autoLink plugin. Even the additional comma here is important:ga(‘linker:autoLink’, [‘com, ‘] );
  7. NowEdit the tracking code on the secondary domain.

Find the create line in the snippet. Make the following changes to the snippet (the changes you need to make are in bold Blue text):

ga(‘create’, ‘UA-XXXXXXX-Y’, ‘auto’, {‘allowLinker’: true});
  ga(‘require’, ‘linker’);
  ga(‘linker:autoLink’, [‘’] );

Why Google Sent You That Message About Blocking JavaScript & CSS

29 Jul

Did you get an email from Google saying Googlebot can’t access your CSS and JS files? You’re not alone: This morning, Google began sending mass messages to verified Google Search Console webmasters notifying them if GoogleBot, their search crawler, cannot access their JavaScript and/or CSS files.

It seems that many WordPress users, including other popular CMS solutions like Joomla and others, have received such notifications. Simply because the default for these CMS solutions is to block the include folder, which has CSS and JavaScript within in.

Google is notifying these webmasters because almost a year ago, Google began rendering the full page as a user would see it. In October they changed their webmaster guidelines to inform webmasters to not block include files.

The rational, if Google cannot full see your web site, it may result in Google not fully understanding your web site, leading to “suboptimal rankings,” as Google put it.

seo-blocks-ss-19201-800x450 (1)

Google Panda 4.2 UPdate

23 Jul

Google tells Search Engine Land that it pushed out a Google Panda refresh this weekend.

Many of you may not have noticed because this roll out is happening incredibly slowly. Google says the update can take months to fully roll out because it will slowly impact your site. The Panda algorithm is still a site-wide algorithm, but some of your web pages might not see a change immediately.

The last time we had an official Panda refresh was almost 10 months ago: Panda 4.1 happened on September 25, 2014. That was the 28th update, but I would coin this the 29th or 30th update, since we saw small fluctuations in October 2014.

As far as I know, very few webmasters noticed a Google update this weekend. That is how it should be since this Panda refresh is rolling out very slowly.

New Chance For Some; New Penalty For Others

The rollout means anyone who was penalized by Panda in the last update has a chance to emerge if they made the right changes. So if you were hit by Panda, you unfortunately won’t notice the full impact immediately but you should see changes in your organic rankings gradually over time.

This is not how many of the past Panda updates rolled out, where typically you’d see a significant increase or decline in your Google traffic more quickly.