Clicky

X

Subscribe to our newsletter

Get the State of Digital Newsletter
Join an elite group of marketers receiving the best content in their mailbox
* = required field
Daily Updates

Yet Another Way to Reclaim Your (not provided) Data

18 April 2012 BY

32 Flares Twitter 1 Facebook 2 Google+ 29 LinkedIn 0 Buffer 0 Email -- StumbleUpon 0 Pin It Share 0 Filament.io 32 Flares ×

Since Google started rolling out its SSL search for logged-in users, SEOs have been scrambling to find ways to reclaim some of the lost data. Our industry relies heavily on keyword data gathered by web analytics software. For someone such as myself, who thrives on web analytics data, seeing the accuracy and usefulness of analytics data eroded further causes an almost physical pain.

There have been many very good approaches with custom reports and advanced segments to gain some measure of insight in to the (not provided) traffic. There’s a very good post by Rachael Gerson on SEER Interactive which talks about looking at the landing pages where (not provided) keywords arrived on, and David Harry has a thorough examination of (not provided) on Search News Central.

Today I will add a new approach to (not provided), which I hope will further help undo the damage SSL search has done – and continues to do – to our keyword reports.

All the following is based on Google Analytics, and I sincerely recommend you create a new profile for these filters and segments so that your standard reporting is unaffected.

To start with, we need to implement a filter in Google Analytics that’s been around for a while. This filter extracts the actual rank of a keyword when a user clicks on it on a Google SERP, and attaches it to the site’s organic keyword report in Google Analytics.

First explained by André Scholten on Yoast.com, it’s also been thoroughly detailed by Bryan Casson on YouMoz. Below I’ve included a screenshot from Bryan’s YouMoz post, but I won’t repeat all the details here as I’d merely be duplicating the work done by André and Bryan.

So please read the posts linked above to see how it is done, and be sure to implement both the keyword extraction filter and the ranking display filter in the right order on your Google Analytics profile (i.e. first the rank extraction filter, then the display filter).

Next you wait a little while for Google Analytics to start populating this new profile with the filtered data, and soon you’ll be able to see ranking data of keywords in your organic search reports:

keyword-positions

Now it’s just a matter of looking at all keywords for a given rank – including the (not provided) keywords, combined with the keyword’s landing page. Filter the report for a given rank, and sort it by landing page, and you get some mighty useful information:

not-provided-landingpage1
not-provided-landingpage1
not-provided-landingpage1
not-provided-landingpage1

If the (not provided) keyword has the same rank and leads to the same landing page, chances are it’s the exact same keyword.

Of course for some popular landing pages, the keywords and (not provided) ranking data are not quite as easily correlated:

not-provided-landingpage-list

Still, by using these Google Analytics filters and comparing (not provided) traffic to the keyword ranking data and landing pages information that is available, you can make pretty accurate educated guesses about which keywords are contained within your (not provided) black hole. You can rejig and combine this data in any way you want to extract maximum value from it, and hopefully recover some of the lost accuracy in your SEO reporting.

If you like this sort of custom analytics reporting, be sure to check out the new Custom Report Sharing for Google Analytics website, which contains an ever-growing list of awesome custom reports, filters, and segments for your web analytics pleasure.

AUTHORED BY:
h

Barry Adams is one of the editors of State of Digital and is an award-winning SEO consultant based in Belfast, delivering specialised SEO services to clients across Europe.
32 Flares Twitter 1 Facebook 2 Google+ 29 LinkedIn 0 Buffer 0 Email -- StumbleUpon 0 Pin It Share 0 Filament.io 32 Flares ×

Nice job, you found it!

Now, go try out the 12th one:

Use Google Translate to bypass a paywall...

Ran into a page you can't read because it is blocked or paywalled? Here's a quick trick (doesn't always work, but often does!):

Type the page into Google translate (replace the example with the page you want):

http://translate.google.com/translate?sl=ja&tl=en&u=http://example.com/

How about that!?

Like this 12th trick? Tell others they need to look for this trick on our page: http://www.stateofdigital.com/search-hacks-marketers/

Or Tweet: Found the secret 12th one!