Google Search Console

Google CloudOAuth 2.0Connection test available

The Search Console API provides access to both Search Console data (verified users only) and to public information on an URL basis (anyone) (Google OAuth2).

OCNORA ships 10 typed Google Search Console operations. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.

Before you connect Google Search Console

Authentication
OAuth 2.0
Credential
{"client_id", "client_secret", "refresh_token"}
Connection test
Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.

What you can do with Google Search Console

Operations, grouped by what they do to your data.

A sample Google Search Console workflow

  1. 1
    A core trigger
    Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Search Console trigger is needed.
  2. 2
    Get Sitesearch_console.get_site
    Retrieves information about specific site.
  3. 3
    Add Sitesearch_console.add_site
    Adds a property to the account — the first step of onboarding a new domain. The property still has to be verified before it reports any data.

An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.

Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.

Google Search Console questions

How does OCNORA authenticate with Google Search Console?
With a stored OAuth 2.0 credential, shaped {"client_id", "client_secret", "refresh_token"}. A connection test can check it when you add it.
What can I automate with Google Search Console?
10 typed operations, each with a reference page listing its config fields and the shapes it emits.
What if the Google Search Console operation I need is not listed?
Where Google Search Console has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
Are there templates that use Google Search Console?
Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
How are Google Search Console calls controlled?
Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.

See your first Google Search Console workflow run.

Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.