{"id":4115,"date":"2020-05-12T10:15:39","date_gmt":"2020-05-12T10:15:39","guid":{"rendered":"https:\/\/chef-dev.creativegeek.co.il\/?p=4115"},"modified":"2022-10-27T16:19:08","modified_gmt":"2022-10-27T13:19:08","slug":"using-google-analytics-and-search-console-data-to-identify-low-hanging-fruit-queries","status":"publish","type":"post","link":"https:\/\/trackingchef.com\/google-analytics\/using-google-analytics-and-search-console-data-to-identify-low-hanging-fruit-queries\/","title":{"rendered":"Using Google Analytics and Search Console data to identify \u201clow-hanging fruit\u201d queries"},"content":{"rendered":"\n
One of my favorite tactics when performing an SEO audit (routine or a fresh start) is extracting existing data from Google\u2019s tools. It\u2019s free, it\u2019s somewhat accurate<\/a> and it\u2019s easy to analyze.<\/p>\n\n\n\n This usually gets me both some quick wins and a general sense of direction for my in depth keyword research.<\/p>\n\n\n\n Note that this tactic is only relevant for sites that have a substantial Organic impact so that their numbers are something you can work with. Usually around 5K Organic monthly sessions should be sufficient for this.<\/p><\/blockquote>\n\n\n\n I\u2019ve started practicing this once Google upgraded the good ol\u2019 Webmaster Tools to the Search Console<\/a>. One of their key changes was a revamp to the Search Queries report, which also changed its name to the Search Analytics report.<\/p>\n\n\n\n One of the main criticism of the old report was the partial and inaccurate data it provided. While the new report still provides only a limited set of data, I have been able to better correlate it with actual traffic and Keyword Planner data.<\/p>\n\n\n\n Note that the data from the Search Analytics report is limited to no more than last 90 days<\/p><\/blockquote>\n\n\n\n This report is accessible in your site\u2019s Search Console under \u2018Search Traffic -> Search Analytics\u2019.<\/p>\n\n\n\n In this report you can see a breakdown of actual search activity broken by several metrics and dimension.<\/p>\n\n\n\n The main dimensions are Queries and Pages, but you can also filter the data by Country, Device (Desktop, Table & Mobile), Search Type (Web, Image, Video) and Date . Metrics span Clicks, Impressions, CTR and Average Position.<\/p>\n\n\n\n In the report we can use the dimensions in conjunction. For example, clicking a specific query and then switching to the Pages tab will show all the pages that ranked for it. Similarly, clicking on specific page in the Pages tab and then switching back to the Queries tab will show all the keywords that page ranked for.<\/p>\n\n\n\n Note that the rankings provided by Google aren\u2019t entirely accurate. They can give the general trend but are in no way a reliable tool for tracking rankings.<\/p><\/blockquote>\n\n\n\n So we\u2019ve covered over the Search Analytics report, but how does Google Analytics fit in all this you ask?<\/p>\n\n\n\n Google Analytics (GA) has an option to connect your Search Console data to it. This is a nice function that brings up the same data as a built in report in GA. These reports sit under \u201cAcquisition \u2014 Search Console\u201d.<\/p>\n\n\n\n But these report are actually kinda crappy. They can only report on a single Dimension from the Search Analytics data while joining unimportant secondary dimensions (can only be useful in a global setting but otherwise rather pointless).<\/p>\n\n\n\n Where do they come in handy? They allow you to export far more query data compared to the Search Console report (999 rows limit).<\/p>\n\n\n\n If your site has plenty of content and has been running for a while, you can expect it to easily exceed that number. Using this export you can easily pull out the top 5,000 queries your site ranks for.<\/p>\n\n\n\n You can even pull 10K using the Google Analytics Spreadsheet Add-on<\/a>.<\/p><\/blockquote>\n\n\n\n Now this is something you can play with \u263a<\/p>\n\n\n\nSearch Analytics Report<\/h1>\n\n\n\n
<\/figure>\n\n\n\n
Ideas for querying<\/h2>\n\n\n\n
Google Analytics<\/h1>\n\n\n\n
<\/figure>\n\n\n\n
Ideas for querying<\/h2>\n\n\n\n