Skip to main content
Last updated on

Troubleshoot the Google Search Console connector

Beta

This feature is in Beta. To use it, a workspace admin must turn on Lakeflow Connect for Google Search Console from the Previews page. See Manage Databricks previews.

This page describes common errors you might encounter with the managed Google Search Console connector and how to resolve them.

For general troubleshooting guidance that applies to all managed ingestion pipelines, see Troubleshoot managed ingestion pipelines.

Search Analytics QPS quota exceeded​

Error message:

Google Search Console Search Analytics QPS quota exceeded. Retrying with backoff.

Cause: The pipeline sent too many requests to the Google Search Console Search Analytics API within a short time window and hit Google's per-user, per-second quota limit.

Solution:

The connector automatically retries with backoff when this error occurs. If the pipeline continues to fail, reduce the number of site URLs or tables ingested in a single pipeline, or add a longer schedule interval between pipeline runs to reduce overall API request volume.

Permission denied (403)​

Error message:

The pipeline fails with an HTTP 403 response and the error is classified as a configuration error.

Cause: The authenticated identity (service account or OAuth user) does not have sufficient permissions on one or more Google Search Console properties. This happens when the identity is not a verified owner or full-permission user on the property, or when domain-wide delegation is misconfigured.

Solution:

Verify that the service account email or OAuth user has Full permission on each site URL specified in site_urls. See Configure authentication to Google Search Console for steps to grant access in Google Search Console.

If you use a service account with domain-wide delegation, confirm that:

  • The User Email to Impersonate field in the connection uses an account that owns or has full access to the properties.
  • The https://www.googleapis.com/auth/webmasters.readonly scope is authorized in the Google Workspace Admin Console for the service account's client ID.

To update credentials, edit the connection in Catalog Explorer. See Create a Google Search Console connection.

Invalid request (400)​

Error message:

The pipeline fails with an HTTP 400 response, and the error is classified as a configuration error.

Cause: The Google Search Console Search Analytics API rejected the report request. A common cause is a custom_report object whose aggregation_type is byProperty and whose dimensions include page or whose search_types include discover or googleNews.

Solution:

For a custom_report object that uses byProperty, remove page from dimensions and remove discover and googleNews from search_types, or set aggregation_type to auto or byPage. See Custom reports.

Invalid connector option value​

Error message:

Text
Invalid connector_options option '<option-name>' for source 'google_search_console': expected array<string>. <reason>
Text
Invalid connector_options option '<option-name>' for source 'google_search_console': value '<value>' is not one of <allowed-values>.

Cause: The connector validates connector options before it sends any request to Google Search Console. A dimensions or search_types value fails validation when it:

  • Isn't a valid JSON array of strings.
  • Is an empty array.
  • Lists the same value more than one time.
  • Contains a value that the option doesn't allow.

Solution:

Set dimensions and search_types to JSON array strings that list each allowed value at most one time, for example '["country", "device"]'. For the allowed values, see Connector options. For examples, see Examples.

Access token expired (401)​

Error message:

The pipeline fails with an HTTP 401 response.

Cause: The access token used by the connection expired or was revoked.

Solution:

The connector automatically refreshes OAuth tokens when it receives a 401 response. If the error persists, the refresh token might have been revoked. Re-authenticate by editing the connection in Catalog Explorer and completing the sign-in flow again. See Create a Google Search Console connection.

For service account connections, verify the service account key JSON in the connection is valid and has not been deleted in the Google Cloud Console. Download a new key if needed and update the connection.

Transient server errors (500, 502, 503, 504)​

Error message:

The pipeline fails with an HTTP 500, 502, 503, or 504 response.

Cause: The Google Search Console API returned a transient server error. These errors are temporary and unrelated to your credentials or pipeline configuration.

Solution:

The connector automatically retries transient errors with exponential backoff. If the pipeline continues to fail after retries, check the Google Workspace Status Dashboard for any ongoing Google Search Console incidents. If no incident is reported, rerun the pipeline manually.

On this page