Published on 05/10/2020 – Last Updated on 05/10/2020 by OTC
You’ll now be able to download the complete information you see in almost all Search Console reports (instead of just specific table views). We believe that this data will be much easier to read outside SC and store it for your future reference (if needed). You’ll find a section at the end of this post describing other ways to use your Search Console data outside the tool.
Enhancement reports and more
When exporting data from a report, for example AMP status, you’ll now be able to export the data behind the charts, not only the details table (as previously). This means that in addition to the list of issues and their affected pages, you’ll also see a daily breakdown of your pages, their status, and impressions received by them on Google Search results. If you are exporting data from a specific drill-down view, you can see the details describing this view in the exported file.
If you choose Google Sheets or Excel (new!) you’ll get a spreadsheet with two tabs, and if you choose to download as csv, you’ll get a zip file with two csv files.
Here is a
Performance report
When it comes to Performance data, we have two improvements:
-
You can now download the content of all tabs with one click. This means that you’ll now get the data on Queries, Pages, Countries, Devices, Search appearances and Dates, all together. The download output is the same as explained above, Google sheets or Excel spreadsheet with multiple tabs and csv files compressed in a zip file.
-
Along with the performance data, you’ll have an extra tab (or csv file) called “Filters”, which shows which filters were applied when the data was exported.
Here is a sample dataset downloaded from the Performance report.
Additional ways to use Search Console data outside the tool
Since we’re talking about exporting data, we thought we’d take the opportunity to talk about other ways you can currently use Search Console data outside the tool. You might want to do this if you have a specific use case that is important to your company, such as joining the data with another dataset, performing an advanced analysis, or visualizing the data in a different way.
There are two options, depending on the data you want and your technical level.
Search Console API
If you have a technical background, or a developer in your company can help you, you might consider using the Search Console API to view, add, or remove properties and sitemaps, and to run advanced queries for Google Search results data.
We have plenty of documentation on the subject, but here are some links that might be useful to you if you’re starting now:
-
The Overview and prerequisites guide walks you through the things you should do before writing your first client application. You’ll also find more advanced guides in the sidebar of this section, for example a guide on how to query all your search data.
-
The reference section provides details on query parameters, usage limits and errors returned by the API.
-
The API samples provides links to sample code for several programming languages, a great way to get up and running.
Google Data Studio
Google Data Studio is a dashboarding solution that helps you unify data from different data sources, explore it, and tell impactful data stories. The tool provides a Search Console connector to import various metrics and dimensions into your dashboard. This can be valuable if you’d like to see Search Console data side-by-side with data from other tools.
If you’d like to give it a try, you can use this template to visualize your data – click “use template” at the top right corner of the page to connect to your data. To learn more about how to use the report and which insights you might find in it, check this step-by-step guide. If you just want to play with it, here’s a report based on that template with sample data.
Let us know on Twitter if you have interesting use cases or comments about the new download capabilities, or about using Search Console data in general. And enjoy the enhanced data!
Posted by Sion Schori & Daniel Waisberg, Search Console team
Comments