Google Search Console
Features | Details |
Release Status | Released |
Source API Version | v3 |
Table Selection | Yes |
Column Selection | Yes |
Edit Integration | Yes |
Replication Type Selection | No |
Authentication Parameters | Google Search console email Google Search Console password Google search console site url |
Replication Type | Key Based Incremental Full based replication |
Replication Key | NA Date |
Suggested Replication Frequency | 24 hrs |
Tables/APIs Supported | ​ |
sites | sitemaps |
searchanalytics | ​ |
Purpose: Lists the user's Search Console sites.
Click here to be taken to the Google Search Console API Documentation for Sites API
Replication: Full Replication
Replication Key: NA
Name | Target Datatype |
siteUrl | STRING |
permissionLevel | STRING |
Purpose:Lists the sitemaps-entries submitted for the site.
Click here to be taken to the Google Search Console API Documentation for Sitemaps API
Source API Documentation
Replication: Full Replication
Replication Key: NA
Fields
Name | Target Datatype |
path | STRING |
isPending | BOOLEAN |
isSitemapsIndex | BOOLEAN |
type | STRING |
lastDownloaded | STRING |
warnings | STRING |
errors | STRING |
contents | RECORD |
Please note that sites and sitemap tables are loaded fully everytime a replication job runs. It is recommended to create separate integrations for sites and sitemap tables and not combine them with SearchAnalytics tables.
Purpose: Query your search traffic data with filters and parameters that you define. The method returns zero or more rows grouped by the row keys (dimensions) that you define. You must define a date range of one or more days.
Users can create multiple tables with different dimensions to extract aggregated data from Google Search Console.
Go to Step 3 to see how to configure SearchAnalytics table.
Replication: Key based Replication
Replication Key: lastRunDate
Fields
Name | Target Datatype |
keys | STRING |
clicks | NUMERIC |
impresssions | NUMERIC |
ctr | NUMERIC |
position | NUMERIC |
​
This parameter is highly sensitive. http://sarasanalytics.com and sarasanalytics.com may take you to the same page, but they are considered as different by the Google Search Console APIs
Submit the integration once you are satisfied with the selections made.
Integrations would be in Pending state initially and will be moved to Active state as soon as the first job loads data successfully in to the configured warehouse
Users would be able to edit/pause/re-activate/delete integration anytime
Users can view job status and process logs from the integration details page by clicking on the integration name from the active list
Click here to be taken to the Google Search Console API Documentation.
​