Google Search Console connector

Important

This feature is in Beta. Workspace admins can control access to this feature from the Previews page. See Manage Azure Databricks previews.

The managed Google Search Console connector in Lakeflow Connect ingests search performance data, site metadata, and sitemap information from Google Search Console into Azure Databricks.

Feature availability

Feature	Availability
UI-based pipeline authoring	Not supported
API-based pipeline authoring	Supported
Declarative Automation Bundles	Supported
Incremental ingestion	Supported
Unity Catalog governance	Supported
Orchestration using Databricks Workflows	Supported
API-based column selection and deselection	Supported
API-based row filtering	Not supported
SCD Type 2	Supported
Automated schema evolution: New and deleted columns	Supported
Automated schema evolution: Data type changes	Not supported
Automated schema evolution: Column renames	Not supported Requires a full refresh.

Authentication methods

Authentication method	Availability
OAuth 2.0 user-to-machine (U2M) (Recommended)	Supported
OAuth 2.0 machine-to-machine (M2M) (Service Account)	Supported
Basic authentication (username/password)	Not supported
Basic authentication (API key)	Not supported

Ingest from Google Search Console in 3 steps

Note

Before starting, review the Azure Databricks user persona, supported interfaces, ingestion frequency, and common patterns.

1. Configure Google Search Console for ingestion (Admins): Set up Google Search Console to authenticate with Azure Databricks.
2. Create a Unity Catalog connection (Admins): Create a connection in Catalog Explorer to store credentials for Azure Databricks to authenticate with Google Search Console.
3. Create an ingestion pipeline (Admins or non-admins): Select any supported interface and create a pipeline from an existing connection.