What access does Renta request?

Renta requests read-only access to your Search Console data (the **webmasters.readonly** scope): the list of your verified sites and their search performance statistics. Your credentials are encrypted in transit and at rest and never stored in Renta's application database. You can revoke access from your Google Account settings at any time.

When do I need to re-authorize?

Only when your Google authorization changes, for example after you change your Google account password or revoke the app's access. Open the source and click **Re-authorize**. The connection refreshes in place, so every pipeline built on that source keeps running.

How much history can I load?

The start date can be at most 90 days in the past. To build a longer history, keep the pipeline running on a schedule: each run adds new days to your warehouse table, and the accumulated history is not limited.

Can I sync several websites?

Yes. Each pipeline exports data for one site, so create a separate pipeline for every site you want to sync. All pipelines can share the same Google Search Console connection.

Google Search Console

Renta allows you to sync Google Search Console data to your data warehouse: daily search performance metrics (clicks, impressions, CTR, average position) broken down by query, page, country, and device.

Authentication

Renta uses OAuth to authenticate with Google. You will be redirected to Google to grant Renta read-only access to your Search Console data.

Your credentials are encrypted in transit and at rest, and never stored in Renta's application database. You stay in control and can revoke access from your Google Account settings at any time.

Connect Google Search Console source

Follow these steps to add Google Search Console as a source in Renta using OAuth authentication.

Go to the CatalogStep 1

Navigate to the Connections > Catalog section in the left sidebar.
Open the Advertising category and click the Google Search Console card.

Google Search Console card in the Advertising category of the Renta catalog

Authorize connectionStep 2

Click Log in to your Google Search Console account. You will be redirected to Google to grant access.

Authorize Google Search Console connection page in Renta

Allow access on GoogleStep 3

On the Google consent screen, review the requested permissions and click Continue. After that you are redirected back to Renta.

Google consent screen asking to grant Renta access to the account

Name the connection and saveStep 4

Finish the setup:

Source name.
Specify a name for this data source. This is used exclusively in the Renta interface.
Access granted.
Verify that the account is connected successfully.

Click Save to finish.

If your Google authorization later changes (for example, after a password change), click Re-authorize on this source. The connection refreshes in place and every pipeline built on it keeps running.

Set up your Google Search Console connection with source name and access granted

Source createdStep 5

The new source appears in the Sources list with the Active status. You can now use it in pipelines.

Sources list with the new Google Search Console source

Create a pipeline

Once the source is connected, create a pipeline to sync your search performance data into your destination.

Create a Google Search Console pipeline

Link your Google Search Console source to a destination and configure the pipeline.

Select Google Search Console as the sourceStep 1

In the left sidebar, click New pipeline. On the Source step, select Google Search Console under Already connected and click Next step.

Select a source step with Google Search Console under Already connected

Select your Google Search Console connectionStep 2

Choose the Google Search Console connection you created earlier and click Next step.

Select a destinationStep 3

On the Destination step, select your destination (for example, Google BigQuery) and click Next step.

Select a destination step with Google BigQuery

Select the destination connectionStep 4

Choose the destination connection you want to load data into and click Next step.

Select your Google BigQuery connection step

Pipeline configuration

On the final step, choose which site to export data from and how Renta loads it.

Report configuration

Point the pipeline at the site and report type.

Google Search Console website and report type selection

Websites.
Select the Search Console site to retrieve statistics from. The list contains the sites available to the connected Google account.
Report Type.
Select Search Analytics. This is the search performance report, the same data you see in the Performance section of Search Console.

Parameters

Select the fields to include in your destination table. Your dataset schema is defined by the parameters you choose here, and each row in the table is one combination of the selected dimensions for one day.

Parameter	Description
Date	The date of the search activity.
Country	Three-letter code (ISO 3166-1 alpha-3) of the country the search originated from, such as USA or DEU.
Device Type	The device used in the search: DESKTOP, MOBILE, or TABLET.
Search Query	The search term entered by users in Google Search.
Page URL	The page of your site shown in the search results (full canonical URL).
Clicks	The number of times the search result was clicked.
Impressions	The number of times the search result was shown in Google Search.
Click-Through Rate	Clicks divided by impressions.
Average Position	The average position of the search result in Google Search.

When the Search Query parameter is selected, Google omits anonymized (rare) queries from the response, so totals can be lower than in reports without the query dimension.

Search type and data state

Choose which search surface the statistics cover and whether to include fresh data.

Search Type Select the type of search data to export.

Search type	Description
Web	Default search results from the combined (All) tab in Google Search. Does not include Discover or Google News results.
Discover	Results shown in the Google Discover feed, personalized content suggestions.
Google News	Results from news.google.com and the Google News app on Android and iOS. Does not include results from the News tab in Google Search.
News	Search results from the News tab in Google Search.
Image	Search results from the Image tab in Google Search.
Video	Video search results, typically from the Videos tab in Google Search.

Data state Choose whether to include data that Google has not finalized yet.

Data state	Description
All	Includes fresh (non-finalized) data alongside finalized data. Fresh values for recent days can still change before Google finalizes them.
Final	Includes only finalized data. Finalization usually takes Google a few days, so the most recent days are absent.

Integration name A display name for this pipeline. Edit it to match your preferences.
Table name The destination table name. Renta suggests a default such as google_search_console_{id}, and you can enter your own.

Date range

Set the historical period to load and the window that is reloaded on every run.

Date start.
The first date of the extraction period. It can be at most 90 days in the past.
Date end.
The last date of the extraction period. Leave it as Today to keep collecting new data on every run.
Overwrite Period.
The lookback window that is reloaded on every run. Renta deletes and re-inserts the data for that window, so values that Google finalized after the initial load are captured. The default is Last 5 days.

Schedule

Choose how often the pipeline runs.

Schedule type	Description
Manual	The pipeline runs only when triggered manually through the interface or via API.
Daily	The pipeline runs once a day at the specified update time.
Interval	The pipeline runs at specified time intervals.
Cron Expression	The pipeline runs on a schedule defined by a cron expression.

For Daily schedules, set the Update time (the exact time each run starts), then click Create pipeline.

Update time selection and the Create pipeline button

Renta also supports API triggers and integration with external orchestrators such as Apache Airflow, Dagster, and Prefect. See the full scheduling documentation for details.

Sync strategy

The table below describes how Renta synchronizes the Google Search Console report.

Strategy	Supported report types	Description
Incremental	Search Analytics	Renta loads data day by day, filtering by the report date, and partitions tables by date. On every run the Overwrite Period window (by default the last 5 days) is deleted and re-inserted, so values that Google finalized after the initial load replace the fresh ones. Within each day, Renta requests desktop, mobile, and tablet data separately and paginates in 10,000-row batches to retrieve the complete dataset.

Limits

Historical period.
The start date can be at most 90 days in the past, and a run fails if a date in its window is older than 90 days. To build a longer history, keep the pipeline running on a schedule: the data accumulated in your warehouse is not limited.
Data freshness.
Google finalizes search performance data with a delay of a few days. With Data state set to All, recent days contain fresh values that can still change. The Overwrite Period reload replaces them with finalized values on later runs.

Frequently asked questions

Ready to get started?

Build your data pipeline today or get a personalized demo. Start free!

Need help?

Get expert support to ensure your project succeeds. We're here to help!

Feature requests?

Help shape our product! Share your ideas for new features and integrations.