---
title: "Google Search Console"
slug: "google-search-console"
description: "Automate data extraction in Dataddo using the Google Search Console API and connect to any destination. Get fresh data securely from Google Search Console."
updated: 2024-04-10T18:08:55Z
published: 2024-04-10T18:08:56Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dataddo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Google Search Console

**Google Search Console** is a free web service that allows website owners and webmasters to monitor and manage how their site appears in Google search results. It provides valuable insights into search performance, indexing status, and helps identify and resolve issues that might affect a website's visibility in Google's search engine.

Refer to our website for [the list of metrics and attributes available in Dataddo](https://www.dataddo.com/connector/google_search_console).

Refer to Google's official documentation to see [all available endpoints from the Google Search Console API](https://developers.google.com/webmaster-tools).

## Authorize Connection to Google Search Console

To authorize this service, use **OAuth 2.0** to share specific data with an application while keeping usernames, passwords, and other information private.

1. On the **Authorizers page**, click on [Authorize New Service](https://app.dataddo.com/service/new) and select your service.
2. Follow the prompts to grant Dataddo the necessary permissions to access and retrieve your data.
3. **[Optional]** Once your authorizer is created, click on it to **change the label** for easier identification.

Ensure that the account you're granting access to is a **Site Owner** or a **Site Full User**.

For more information, see our article on [***authorizers***](https://docs.dataddo.com/docs/authorized-services).

## How to Create a Google Search Console Source

1. On the **Sources** page, click on the [**Create Source**](https://app.dataddo.com/sources/new) button.
2. Select the connector from the list and name your ***data source***.
3. On the **Dataset** step, select your **dataset**.
          **DATADDO TIP**

          

If you're unsure which dataset to select, use the search bar to look for datasets with the desired attributes or metrics.
4. On the **Account** step select your ***authorizer*** from the drop-down menu.
          **Didn't find your authorizer?**

          

Click on **Add new Account** at the bottom of the drop-down and follow the on-screen prompts. You can also go to the **Authorizers** tab and click on [**Add New Service**](https://app.dataddo.com/service/new).
5. On the **Attributes and Metrics** step, select the **metrics and attributes** you want to extract.  

![Create a source using a custom-schema connector.](https://cdn.document360.io/084ed225-3f99-4644-a2da-39ca0cd5ef45/Images/Documentation/Create%20Source%20-%20Custom-Schema%20Connector.png)
6. On the **Metadata** step, select which [**metadata fields**](/docs/metadata-inclusion) such as extraction time to add to your data.
7. On the **Snapshot** step:
  1. Configure your [**sync frequency**](/docs/extraction#extraction-frequency) or click **Show advanced settings** to set the exact synchronization time.
          **DATADDO TIP**

          

To **load historical data**, refer to the [**Data Backfilling**](https://docs.dataddo.com/docs/data-backfilling) article.
  2. [Optional] Enable the **Allow Empty Data Extractions** toggle to allow the extraction when no data is available.
8. In the top-right corner, click **Test Data** button to preview extracted data. **Adjust the date range** for specific time frame.
9. Click on **Save** and **congratulations, your new data source is ready!**

---

## Limitations

### Historical Data Limitations

The Google Search Console API allows you to extract data up to **16 months** back.

## Troubleshooting

### Data Preview Unavailable

No data preview when you click on **Test Data** might be caused by an issue with your ***source*** configuration. The most common causes are:

- **Date range**: Try a smaller date range. You can load the rest of your data afterward via [manual data load](https://docs.dataddo.com/docs/data-backfilling).
- **Insufficient permissions**: Please make sure your authorized account has at least admin-level permissions.

### Aggregated Data by Property vs. by Page

When you aggregate data in Google Search Console, you have the option to do it either **by property (all domains inside one URL)** or by **page**.

**Aggregation by Property** When you aggregate by property, all domains inside a specific URL will be combined under one entry. E.g. `dataddo.com/connectors` and `dataddo.com/platform` will both be counted under `dataddo.com`.

**Aggregation by Page** When aggregating by page, each unique URL will be counted once, even if they are pointing to the **same page**.

While the numbers will match those in your GSC UI, aggregated **totals** by property and page will not match which may appear as data discrepancy.

| Metric | Aggregation by Property | Aggregation by Page |
| --- | --- | --- |
| **CTR** | 100% (clicks for the whole site ) | 33% (per URL if you have three pages) |
| **Impressions** | 1 per property | 1 per page |
| **Average position** | 1 (highest position from the site in the results) | 2 (for each URL (1 + 2 + 3) / 3 = 2) |

For more detailed information, please see [Google's official documentation](https://support.google.com/webmasters/answer/7576553).

### Aggregated Data Discrepancies

If you aggregate your impressions or clicks data by countries or devices, the data will not have any discrepancies.

| Metrics combination | Number of rows per day |
| --- | --- |
| Date + country | Around 200 rows per day |
| Date + device | Around 3 rows per day |
| Date + country + device | **[number of countries*number of devices]** amount of rows, aka around 600 rows |

However, if you aggregate values by **query** and/or **page**, there will potentially be an **infinite** number of rows due to the very large or infinite number of search queries. Due to [data sampling](/docs/data-sampling), as much data as possible will be shown but it won't be **all data (all search queries)**.

This means that while impressions or clicks **per** query will be the same, the aggregated values for data in your GSC and data extracted by Dataddo will be **different**. (Trends should be the same.) The exact same thing applies for the **page** dimension.

**Solution** To avoid data discrepancies, use only **date**, **country**, or **device** dimensions or their combination for totals. Also when selecting your dimensions, for less data discrepancies, use as few as possible.

### Cannot Retrieve Fresh Data

Google takes between 24 – 72 hours to process data which is why it’s possible to get data only from 3 days ago or older. For Google Search Console specifically, [change your date range expression](/docs/setting-date-range) to **4d4 or older**.

## Related Articles

Now that you have successfully created a ***data source***, see how you can connect your data to a dashboarding app or a data storage.

**Sending Data to Dashboarding Apps**

- [Simple Data Integration to Dashboards](https://docs.dataddo.com/docs/simple-data-integration-to-dashboards)
- [Data Backfilling to Dashboarding Apps](https://docs.dataddo.com/docs/data-backfilling-to-dashboarding-apps)

**Sending Data to Data Storages**

- [Batch Ingestion to Data Warehouses](https://docs.dataddo.com/docs/ingestion-to-data-warehouses)
- [Data Backfilling to Storages](https://docs.dataddo.com/docs/data-backfilling-to-storages)

**Other Resources**

- [Troubleshooting](https://docs.dataddo.com/docs/troubleshooting)
- [Extraction Logs](https://docs.dataddo.com/docs/extraction-logs)
- [Data Duplication](https://docs.dataddo.com/docs/data-duplication)

Authorizers act as credentials for external services (e.g. Facebook or Google). To enable Dataddo to access and retrieve your data, you need to grant access to accounts that possess admin-level permissions or higher within these services.

Data sampling involves analyzing a subset of all available data to derive insights and understandings that are representative of the entire dataset. This makes the analysis more manageable and efficient.