Requirements
Google Search Console requires an active account and OAuth client credentials, granted by signing in with your account to connect — both are set up on its own site.[3]
Get your Google Search Console credentials
You’ll be redirected to sign in and approve access — your password is never shared with WEXTL.
- Client IDtextRequired
OAuth 2.0 Client ID from Google Cloud Console → Credentials → your OAuth client. Enable the Search Console API on the project.
[1] - Client SecretpasswordRequired
Client Secret shown next to the same OAuth client ID above in Credentials.
[1] - Additional Scopesarray
Optional. Extra Google OAuth scopes to request on top of the default ones, one full scope URL per item (for example https://www.googleapis.com/auth/drive). Duplicates of the default scopes are ignored. Use this with your own Client ID, and enable the same scopes on its OAuth consent screen.
[1]
Connect Google Search Console in WEXTL
- Log in to your WEXTL account, add the Google Search Console node module to your workflow, and click Create new credential.
- Optional: In the Credential name field, enter a name for the credential.
- Enter the authentication credentials you copied from your Google Search Console account, or follow the on-screen instructions to create the credential.
- If prompted, authenticate your account and confirm access.
- If you want to make changes to your credential in the future, follow the steps in Manage credentials →

Notes
Credentials are org-scoped; share them with teammates from the Credentials picker on any of its nodes.For detailed information on connecting an application, see Connect an application →
Google Search Console node modules
The list below is a reference of every Google Search Console node module the integration supports. You will be able to pick any of them on the workflow canvas while building automations.
Browse every Google Search Console node module below — each one opens to show its input parameters, outputs, and connection requirements.
| Field | Type |
|---|---|
Site URLRequired | choice |
| Field | Type |
|---|---|
Site URLRequired | choice |
| Field | Type |
|---|---|
Site URLRequired | choice |
| Field | Type |
|---|---|
Site URLRequired | choice |
Start DateRequired | date |
End DateRequired | date |
Dimensions | array |
Dimension | choice |
Type | choice |
Dimension Filter Groups | array |
Group Type | choice |
Filters | array |
Aggregation Type | choice |
Data State | choice |
Row Limit | number |
Start Row | number |
| Field | Type |
|---|---|
Rows | array |
Keys | array |
Clicks | number |
Impressions | number |
CTR | number |
Position | number |
Response Aggregation Type | text |
Metadata | object |
First Incomplete Date | text |
First Incomplete Hour | text |
| Field | Type |
|---|---|
Site URLRequired | choice |
Templates
Look for Google Search Console templates in the WEXTL template library.
Browse templates →Explore alternative apps
- Akeneo[2]Product information management (PIM) for enriching and distributing catalog data.
- BrandwatchConsumer intelligence and social listening platform for brand monitoring, insights, and research.
- AWeberEmail marketing — lists, subscribers, campaigns, and broadcasts.
- beehiivPublish newsletters and manage subscribers in beehiiv.
- BrandfetchLook up company logos, colors, fonts, and firmographic data with Brandfetch.
References
- WEXTL® Google Search Console Source Code connector implementation.
- Our users use cases and automations.
- Official API Documentation for Google Search Console.
- WEXTL® visual workflow builder data.
Last updated: Jul 24, 2026 18:11
