Google Search Console

The Qlik Google Search Console Connector enables you to select data from your Google Search Console, such as link clicks by country or by referring page, and load it into your Qlik Sense app or QlikView document.

Tip:

The Qlik Web Connectors help you connect to different data sources and fetch data in the same way. Learn how to authenticate a data source connection and how to use tables to fetch data.

Connecting to data sources

Ways to access your data

To access your website data from Google Search Console, you need to authenticate the connector with your Google account credentials and you need to have verified your site ownership with Google Search Console.

Loading data from tables

After authenticating the connector, the following tables are available:

Table Description
ListSites Returns a list of websites and the website permission level that you have added to your Google Search Console account.
Site Returns the status of the website.
SearchAnalyticsQuery Returns a custom-built query for a single URL. You define the date range, the dimension, the filter, the aggregation type, and the row limit.

Using the SearchAnalyticsQuery table

This table returns a custom-built report for a single URL. You can use dimensions to group your data and you can filter those groupings with the Dimension Filter:

Dimensions

You can group your data by dimensions. Valid dimensions are: 

  • date
  • country
  • device
  • page
  • query

Dimension filter

You can enter a dimension filter with a JSON statement.

Example: to filter the dimension country by USA

[{'grouptype': 'and',

'filters': [{

'dimension': 'country',

'operator': 'equals',

'expression': 'usa'}

]

}]

To learn more about dimension query, see: 

Troubleshooting

The metrics totals are different between Google Search Console and the connector

Possible cause  

When viewing metrics tables in Google, long tables can sometimes become truncated to conserve space.

Proposed action  

No solution needed. To understand why you see a difference, see: 

Data is different when aggregating data by site versus by page

Possible cause  

Google uses different accounting method for aggregating data by site versus by page.

Proposed action  

No solution needed. To understand how Google aggregates data, see:

Did this information help you?

Can you tell us why it did not help you and how we can improve it?