This post discusses the increase of "(not provided)" as a search term shown within Google Analytics Organic Keyword Report (which shows what keywords users searched for to get to a website). For more information on what "(not provided)" is check out http://www.notprovidedcount.com/what-is-not-provided/
Everyone in the search world knew it was coming, but I think we all thought we might have had a few more months before Google pulled the plug on our precious keyword visit data.
Initially affecting purely logged in users only a small fraction of website visits had the dreaded (Not Provided) keyword, fast-forward almost 100 weeks and its a very different story. Google has now moved to redirect all traffic through secure search, meaning very soon Google organic keywords will hit 100% "Not Provided".
Why Google, Why?
There is, as with anything Google does, speculation and rumours around the web about why this move has happened and how they are evil, doing this for profit, hating on webmasters etc.
However Google's official statement via SearchEngineLand is as follows:
We want to provide SSL protection to as many users as we can, in as many regions as we can — we added non-signed-in Chrome omnibox searches earlier this year, and more recently other users who aren’t signed in. We’re going to continue expanding our use of SSL in our services because we believe it’s a good thing for users….
The motivation here is not to drive the ads side — it’s for our search users.
Whether or not you believe Google's claim, that this is all for search users, does not matter. Common opinion and voice will not change anything. Not Provided will hit 100% and we, as search marketers, need to adapt.
Now that the Not Provided percentage is so high it does make our jobs harder, KPIs will need to change, organic traffic can no longer be separated by brand/non-brand keywords, understanding if keywords are worth targeting is more of a challenge, etc.
But not all is lost, there are methods to help understand which keywords users are searching for. They just got a little bit trickier:
- Google Webmaster Tools is now more essential than ever - use the Search Queries interface to discover keywords users are searching for.
- Use Landing Pages rather than keywords to understand what content users are looking at - if you see a spike on a page about Wedding Dresses its pretty likely you gained some ground for some keywords related to that page!
- Run comprehensive ranking reports - I would argue the importance of a ranking report has increased significantly following this change. I'm not talking about tracking a handful of keywords - track hundreds, or thousands, and look for trends - if you see Wedding Dress related keywords increase in rank and the Wedding Dress pages' traffic increases then that's a pretty strong correlation.
- Run some Adwords - whilst not always practical, running even a short term adwords campaign will allow you to observe keywords that have a high number of impressions and running with phrase, broad and broad-match modifier match types will allow you to uncover the long tail. Use exact match to analyse a specific keyword you’re working on to try to pre-empt how it will perform.
Whilst this change does take us all out of our comfort zones with analysing SEO performance, all is not lost. As with all things SEO – we just have to adapt.
Auditing your Google Analytics account for query parameters can be tedious but helps keep page reports clear of unwanted row duplication. We talk about the effects of collecting unwanted queries on your reporting and how to fix it. We’ve also built a free tool to make the process easier.
When a form has been successfully submitted to HubSpot, HubSpot propagates an event that we can listen to and use to trigger marketing tags within Google Tag Manager. Below we create a Custom HTML Tag that listens for a form success, trigger a dataLayer event which can then be used to trigger a marketing tag to push this data into Google Analytics.
Service Provider and Network Domain dimensions are no more. Let’s get Service Provider data back online. We’ll show you how to re-enable ISP data using Google Tag Manager and an IP Lookup Service.
Track when users leave your site to visit your social media pages. Understand when your content is driving positive move to your social assets.
The use of social sharing widgets is commonplace. But who’s actually tracking interactions with these? Let’s make a count of how many people are clicking these buttons and record a social share rate to see how many readers amplify content on social media.
Anybody who uses DoubleClick Floodlight knows the slow process of implementing a new tag for each activity for a campaign interaction or conversion. If you’re using Google Tag Manager to add a tag, trigger and maybe some new variables for every new Floodlight – it won’t take long for your container to overfill with almost identical tags. While there’s nothing wrong with this style of implementation, there is another way.