NB: This feature is available to all paying monthly or annual subscribers on any package.
There appears to have been a general move amongst SEOs to move their client reporting to Google Data Studio over the past couple of years, so we’ve made the decision to follow this trend by retiring our own internal reporting section and simply add Google Big Query to the Integrations section of the platform, as this is the first step which will allow you to pull data from there into Google Data Studio and then you will have the ability to quickly generate visualisations in your reports like these 👇🏻
So the simple steps to get this up and running are as follows:
Setting up a Big Query project is a quick and painless process. Big Query also has a free tier (overage pricing beyond the limits of the free tier is based on the queries you run and the amount of data you store – at the time of writing, the first 1TB of data processed with BigQuery each month is free – but please check Google’s latest pricing for Google Big Query).
If you haven’t used Big Query before, you can follow the above links from the above BQ documentation page or you can go directly to this URL: https://console.cloud.google.com/bigquery.
Then you’ll simply need to setup a new project.
NB: you only need to setup one Big Query project – all your individual projects will show up as ‘data sets’ underneath that project – as indicated here: 👇🏻
In order for the Authoritas platform to be able to access your Big Query project, we will need something called a service account, together with a key file. You should only need to create only one each of these!
(a) Login to your Google Console
(b) Create a Service Account
Google Cloud Platform > IAM (Identity & Access Management) & Admin > Service Account
IAM > Create Service Account
(c) Create a key file
Click on the Settings link in the header and then the Integrations module from the left-hand side Navigation…
…and then you’ll see this Integrations screen ☝️:
Underneath ‘Google Big Query’, click on the ‘Authorise Now’ button and a dialog window will appear. You can then either upload the JSON file you created in Step 2(c) and hit ‘Save’ or you can select one or more Authoritas projects to send across to Big Query.
If you click on ‘Select Projects’ like so…
Configure Big Query Integration > Select Projects
…it will default to selecting just the project you have selected in the platform, but you can choose here to synchronise your Authoritas account with your Big Query project for any number of Authoritas projects (there is currently no limit on the amount of data you send across, but you may want to check the Big Query costs for storing and querying your datasets first, if you are planning on sending across a lot of data).
To proceed, you will also need to upload the JSON file you created in Step 2(c). Once you’ve followed these steps, we’ll start to send the following data from Authoritas to your Big Query project:
The above data will show up in the following tables:
NB: The syncing works from Authoritas => Big Query. If you make changes in the Authoritas platform, such as renaming your Authoritas project, this won’t be reflected automatically in Big Query. Similarly, if you stop pushing the data over to Big Query from Authoritas for any reason, the dataset will still be present in your Big Query project until you manually delete it from the Big Query console.
Customers with current Big Query integrations:
If our Engineering team has already got a custom Big Query integration up and running for you, we would recommend that you still follow the above steps to create a new service key for a new instance. We will then send all the above data over to that instance and you can compare the data in both Big Query projects, until you are happy that the standard format of data is fulfilling your reporting needs; if anything is missing from the standard integration detailed above that you are currently seeing in your custom integration, please let us know (product@authoritas.com) and we will endeavour to include this data in the standard integration too.
We continue to make improvements to these templates and have just released an updated version 1.1 of our standard monthly SEO report template which includes a lot more filtering options and visualisations – like the one below 👇🏻:
To use the template, simply open it up and click the '3 dot' menu on the top right-hand side and click 'Make a copy'.
Then all you need to do to change the data sources to the same named data sources in your own Big Query project.
N/B: you will need to do this with every data source listed.
This step-by-step video takes you through how to switch data sources in Data Studio.
That’s it! Your report should now be populated with data from your own Big Query project.
What you can do now is, of course, entirely up to you. You may, for instance, want to remove to replace some of the sample widgets or tables or whole pages; you may want to add your own visualisations, make use of community visualisations or add some perceptive insights or commentaries to the report. Google Data Studio is a very flexible way of creating SEO reports. Combine that with the power of Google Big Query and we hope you agree that it makes for a powerful way to generate client reports for your SEO campaigns. Hopefully, you will agree that this reporting solution provides the following key benefits:
The rollout of SGE will create unprecedented risks to your hard earned organic traffic, as well as new opportunities to succeed.
You need to be ready. The only question is, whether you want to be ready now or later?
Check out the latest version of our comprehensive SEO report. Version 1.1. contains two new reports that will help you report on SEO performance overall and at tag group level and discover opportunities to rank for valuable Universal SERP features.
It’s crucial that from the outset you’re meeting with your stakeholders and getting an understanding of their business objectives and KPIs before creating the SEO dashboard. This often means speaking to individual teams who have a stake in SEO activity, and finding out their projects, resources and priorities so that you can build these into your dashboard.
