THE RKGBLOG

Estimating Google Organic Search Visits Hidden by iOS 6

iOS 6 Safari Search Bar

As we pointed out earlier this quarter, the vast majority of Google search traffic from devices running iOS 6 is being passed without a referrer as a result of Apple’s move to default its Safari search box to Google’s Secure SSL search.

Without the referrer, analytics packages are unable to correctly attribute organic search traffic as such, and the traffic is instead seen as direct.  This presents a significant challenge for SEOs looking to accurately measure and assess the efficacy of their efforts over time.

With mobile generating a 25% or higher share of search visits for many sites, and iOS making up the majority of that, organic traffic comparisons from year to year, or even month to month, have already been thrown off considerably by iOS 6.

Unless Apple changes its default search option or Google employs a workaround to deliver a referrer scrubbed of the search query — as it does for secure desktop searches — the extent to which organic search visits are “hidden” by iOS 6 will only grow as its adoption rate increases.

This leaves SEOs little recourse but to work to provide estimates of the true volume of Google organic search visits from iOS 6, and in turn, the full picture for the organic channel.  Here are some tips to do just that.

Determining The Percentage of Google iOS 6 Traffic Without a Referrer

How we go about estimating organic iOS 6 traffic will depend on the information we have at our disposal.  We’ll outline two common scenarios below, both of which will first require knowing the approximate percentage of Google iOS 6 organic search traffic that does not have a referrer.  Again, this is the segment that will be seen as a direct visit by analytics packages, even if it came through Google organic search.

To get this number, we can use our results from paid search as a close proxy.  Most sophisticated paid search programs employ a redirect for tracking purposes.  Upon an ad click, this redirect can capture the browser’s user-agent, which tells us about the device and its OS, and parameters in the ad URL that indicate the source of the click, e.g. Google.  We can therefore determine what percentage of the time an iOS 6 user from Google paid search did not pass a referrer.

Our original post found this number to be 82% for an aggregate sample of sites.  In a follow-up analysis we found the median result to be similar at 79% with a mean absolute deviation of 7%.  If you or your paid search manager cannot determine the value for your site, you could employ 80% as a reasonable stand-in.

Case 1:  We Can See Google Organic Traffic by OS Version (Google Analytics/RKG Attribution)

For sites employing analytics packages that can deliver results specific to the operating system version — iOS 5 vs iOS 6, and so on — the calculations to estimate the number of visits improperly attributed to direct due to iOS 6 are fairly simple.

If we know that, say 80%, for a nice round number, of iOS 6 search visits do not pass a referrer, we can say that only 20% of Google organic iOS 6 visits are accurately attributed.  With that knowledge, we take the number of iOS 6 visits recorded for Google organic and multiply it by 5 to get an estimate for the true volume, according to the following formula:

(1/(1 – % iOS 6 Search Traffic Without Referrer)) * (Number of Recorded iOS 6 Google Organic Visits) = Actual iOS 6 Google Organic Visits

To calculate just the number of Google organic visits hidden by iOS 6, we can subtract the recorded visits from the figure we obtained above or follow a slightly different path from the beginning using this formula:

((% iOS 6 Search Traffic Without Referrer)/(1 – % iOS 6 Search Traffic Without Referrer)) * (Number of Recorded iOS 6 Google Organic Visits) = Hidden iOS 6 Google Organic Visits

Users of Google Analytics can create a custom report to obtain the number or iOS 6 visits that were correctly recorded for Google organic search:

In the example above, we are applying filters to limit visits to the Source / Medium of “google / organic”, the Operating System of “iOS”, and the Operating System Version of “6\.”.  Note that for the Operating System Version we are using a Regex, which will capture all versions of iOS 6.  Currently, it is common to see iOS 6.0, 6.0.1 and occasionally 6.1.

This example also includes a keyword-level breakdown for those SEO programs where it is important to include that granularity.  A quick aside, if you run this report, you should not see any (not provided) queries, because that issue is confined to desktop where Google employs the workaround to deliver referrers scrubbed of the search query mentioned above.

Case 2: We Can Only See Google Organic Traffic at the OS Level (Adobe SiteCatalyst)

In cases where we cannot see how much traffic was recorded for specific versions of iOS, our estimates require another assumption and get a bit more complicated.  Specifically, we will need to estimate the breakdown of the iOS bucket, or in other words, the iOS 6 adoption rate. Unfortunately, this is a moving target, so even if we have a strong method of determining this figure, we will need to continue to update it as more and more iOS users move to the latest version.

As with determining the percentage of missing referrers, paid search data is likely going to be our best bet for estimating iOS 6 share of Google organic search visits.  RKG data shows that iOS 6 adoption is at 67% for the median site in December to date.  This percentage is pretty consistent across sites.

For this equation, let’s go ahead and define some variables:

iOSA = Actual iOS Google Organic Traffic

iOSR = Recorded iOS Google Organic Traffic

AR = iOS 6 Adoption Rate

MR = Percentage of iOS 6 Search Traffic without Referrer

First let’s consider what constitutes the total amount of traffic that was properly recorded for iOS Google organic:

iOSR = iOSA * AR * (1-MR)  + iOSA* (1-AR)

The piece on the right — iOSA* (1-AR) — is the traffic we see from earlier versions of iOS.  So if iOS 6 adoption (AR) is at 67%, 1-AR is 33% and analytics programs properly record 33% of actual iOS Google organic (iOSA) as Google organic.  The left side of the equation is similar, but adds in the missing referrer percentage for iOS 6 to account for a portion of that piece of the pie being labeled as direct.

The problem is we don’t know the value of iOSA.  With a little algebra, we can solve for it though:

iOSA = iOSR/(AR*(1-MR)+(1-AR))

So if we can get a value for iOSR from our analytics program, we can plug that into the equation, along with the values we previously determined for iOS 6 adoption rate and percentage of iOS 6 traffic missing referrers to get actual iOS 6 Google organic traffic.  Subtracting the recorded value from the actual value will give us the amount that was hidden.

To get recorded iOS traffic for Google organic out of the Adobe SiteCatalyst UI, we take the following steps:

1. Under the Reports navigation, click Mobile and then Operating System:

2. On the next page, click the icon just to the left of the iOS listing to bring up the Breakdown By menu:

3. Select Traffic Sources then Search Engines Natural:

4. In the filter bar, enter “Google”.

5. Download the report and sum the values.

Conclusion

As we indicated up front, iOS 6 visits being improperly attributed as direct is already having a major impact on how organic search traffic levels appear in analytics packages.  A typical site that generates 25% of its traffic from mobile is already seeing its recorded Google organic search visits running about 12% lower than the actual volume.  If iOS 6 adoption were 90%, that figure would increase to 16%.  That’s assuming mobile traffic share remains flat, which will certainly not be the case.

While Google may step in and employ a workaround to deliver a referrer for secure mobile searches, we simply cannot wait for that to happen when such a significant amount of traffic is affected.

To try these calculations for your own site, you can download this Excel spreadsheet and plug in your iOS data:

Estimates for iOS 6 Google Organic Traffic (Excel)

  • Mark Ballard
    Mark Ballard is Director of Research at RKG.
  • Comments
    20 Responses to “Estimating Google Organic Search Visits Hidden by iOS 6”
    1. AJ Kohn says:

      This is certainly troubling since it creates less confidence in the analytics numbers.

      One of the easier ways to see the difference is to simply create an Advanced Segment for iOS (Operating System) and then another specifically for iOS 6 (Operating System + Operating System Version) and apply both against Direct Traffic reports.

      https://www.evernote.com/shard/s242/sh/3ff13a00-39f2-4003-9ff1-32fa65a32de5/38bb8183e420204a186aea1e01155f0a

      The difference between the before and after is pretty dramatic. In fact, you could potentially use the pre-iOS 6 direct traffic volume as your benchmark and attribute the delta to organic (minus some seasonality.)

      In my view, this is something that must get fixed and fast.

    2. Mark Ballard Mark Ballard says:

      Thanks, AJ. That’s a great way for everyone to get a quick sense of the impact to their own analytics. I’m betting the majority of site operators out there are still trying to figure this out.

    3. Tim Kilroy says:

      Terrific thinking, here, and a very clever way to approximate the search volumes. But this is the latest in what amounts to an all out assault on organic search analytics. As an agency or internal SEO provider, it is harder and harder to prove the ROI. And as a marketer, organic search is a critical part of brand strategy. But Google is slowly choking SEO as an effort-based marketing channel by slowly turning down the trickle of info from analytics. Is Google really out to kill SEO? Seems that way to me…ugh.

    4. Mark Ballard Mark Ballard says:

      Thanks, Tim. I hear you, but it’s important to remember that, at least in this case, the hidden data is a result of a move Apple made, not Google. On Android devices we are not running into the same issue… yet.

    5. Hey, Tim, there’s no question in my mind that Google would love it if people stopped thinking about SEO and just focused on building great websites and mobile experiences. The problem is few people in the space get to work with high quality websites. Much of the black hat stuff that causes Google, Bing and users so much grief is produced by folks who know they’re trying to promote thin/scrapped garbage. Quality is hard. Folks at Google have told me that they see quality SEO as helpful to them in that it makes it easier for them to find and understand webpages. Unfortunately, the black hat folks do make their lives much more difficult and do account for a ton of the SEO work done.

      There is a war of algo updates vs black hat techniques. Is the KW suppression for logged in traffic, or the crack down on ranking report scrapers part of that war? I doubt it. Google could simply not pass any referrer data if it wanted to go there, and Hitwise/Experian panel-type reports and GWT rankings would quickly supplant the scrapped versions. Google could totally blind us, but hasn’t, and they know full well that there are other ways to get the general idea of KW rankings that they can’t block, so why would they bother.

      Panda, Penguin and the next black and white animal (Killer whale?) are aimed at the black hats, for sure, but I don’t think this is.

    6. Ted Ives says:

      Mark, thanks for doing so much heavy lifting to figure this stuff out; RKG’s willingness to share it is a big help to the industry. Nice job.

      It’s pretty clear that before long we’ll all be flying blind to some extent, what with (not provided) etc. My sense is this may force people into either of two strategies: write a lot of content and hope it sticks, or make very sure that each page is tightly focused on a single most prominent term (i.e. keyword density analysis).

      I tend to think the second way will have increasing merit because then Entrance Page visits can become a sort of proxy for organic keyword volume. Either way PPC seems like a big benefactor.

    7. As Ted said earlier, thanks for the heavy lifting here and solid post. I often here people, sometimes professionals, say that algebra was a waste of their time in school. Clearly this paints a different picture.

    Trackbacks
    Check out what others are saying...
    1. [...] With iOS 6 obscuring the true volume of Google organic search visits, it is important for us to accurately assess the full impact.  [...]

    2. [...] Looks like things are getting even worse, with iOS6 also hiding organic search details. var dd_offset_from_content = 40; var dd_top_offset_from_content = 0; [...]

    3. [...] for the search traffic you’ve worked so hard to earn, using the methodology outlined above, another one published by the Rimm Kauffman Group or one you develop on your own. And do so before this issue balloons to a point where your client [...]

    4. [...] RKG did a nice job of tracking this and showing how to estimate the hidden search traffic. But for some reason this issue doesn’t seem to be getting as much traction as it should so I wanted to demonstrate the problem and show exactly how you can fight back. Because it’s tough enough being an SEO. [...]

    5. [...] for a hunt trade you’ve worked so tough to earn, regulating a methodology summarized above, another one published by a Rimm Kauffman Group or one we rise on your own. And do so before this emanate balloons to a indicate where your [...]

    6. [...] reports in favor of URL traffic reports, and finding smart ways to shed light into new blind spots (think iOS6). Most importantly it involves education throughout the organization of what is changing and why. [...]

    7. [...] via “not provided” and the recent update of Chrome while Apple has removed more with iOS6 so in 2013 we are anticipating that good ranking data will be more important than ever in a large [...]

    8. [...] 80% of iOS6 traffic is hidden. To fix it check out this article: Estimating Google Organic Search Visits Hidden By iOS 6 [...]

    9. [...] phones and tablets. And guess what, Google just changed the game on that for paid search, while the iOS6 hidden traffic problem is still not widely known by [...]

    10. [...] Safari dentro iOS 6 (la versione più aggiornata del sistema operativo presente su iPhone e iPad) rischia di essere sempre visto come “diretto” (e non, per esempio, proveniente da ricerca [...]

    11. [...] the biggest tablet market. Finally, the percentage of mobile search is always increasing .One man did the math and estimated that sites might be losing upwards of 12% of their traffic due to this issue, a [...]

    12. [...] RKG’s method, we do not need to take into account historical data. We simply use the iOS 6 lost Google Organic [...]

    13. [...] searches being incorrectly attributed as direct visits, and we offered some guidance on how to estimate the impact for your site as Apple’s latest mobile operating system continued to make gains in overall [...]