Google Search Console
Check the enabled Search Console API, exact managed OAuth scopes and property-access requirements for your task.
Last updated
Google Search Console can use Typenode's managed Google OAuth app or your own custom app. The managed route covers tasks using the API and allowed scopes below; the connected Google account must already have the required property access. Request only the scopes your task needs.
For shared Google authentication, custom app setup and registration reuse, see the Google overview.
Required API
| API | Service identifier | Managed Google app | Custom Google app |
|---|
Google Search Console API | searchconsole.googleapis.com | Enabled in Typenode's project | Enable in the project that owns your client |
|---|
OAuth scopes
These exact scopes are allowed by the managed Google app for this API:
| OAuth scope | Access |
|---|
https://www.googleapis.com/auth/webmasters.readonly | Read-only Search Console access |
|---|---|
https://www.googleapis.com/auth/webmasters | Read and write Search Console access |
Use the least access the operation requires. The current read-only Search Console Template requests
only https://www.googleapis.com/auth/webmasters.readonly. The presence of the read/write scope
does not mean every installation requests it.
Google's authorization reference defines both scopes. Check the method's authorization requirements when building another task. For example, URL Inspection accepts either scope and reports Google's indexed version of the URL, rather than running a live indexability test.
Account and property access
The person approving consent must already have access to the intended Search Console property. OAuth consent does not add them to it. Use the property's exact identifier, such as a URL-prefix property or a domain property, as returned by Google.
For a complete installation, follow the Google Search Console walkthrough.