Google Search Console connector
This feature is in Beta. Workspace admins can control access to this feature from the Previews page. See Manage 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 Databricks.
Feature availability
Feature | Availability |
|---|---|
UI-based pipeline authoring |
|
API-based pipeline authoring |
|
Declarative Automation Bundles |
|
Incremental ingestion |
|
Unity Catalog governance |
|
Orchestration using Databricks Workflows |
|
API-based column selection and deselection |
|
API-based row filtering |
|
SCD Type 2 |
|
Automated schema evolution: New and deleted columns |
|
Automated schema evolution: Data type changes |
|
Automated schema evolution: Column renames |
Requires a full refresh. |
Authentication methods
Authentication method | Availability |
|---|---|
OAuth 2.0 user-to-machine (U2M) (Recommended) |
|
OAuth 2.0 machine-to-machine (M2M) (Service Account) |
|
Basic authentication (username/password) |
|
Basic authentication (API key) |
|
Ingest from Google Search Console in 3 steps
Before starting, review the Databricks user persona, supported interfaces, ingestion frequency, and common patterns.
- Configure Google Search Console for ingestion (Admins): Set up Google Search Console to authenticate with Databricks.
- Create a Unity Catalog connection (Admins): Create a connection in Catalog Explorer to store credentials for Databricks to authenticate with Google Search Console.
- Create an ingestion pipeline (Admins or non-admins): Select any supported interface and create a pipeline from an existing connection.