Skip to main content

Why connect Search Console

Search Console holds the one dataset that says what people actually typed to find you, and which of your pages Google decided to show them. It is the most direct signal available about the gap between what your content says and what your market is looking for. It is also, for most teams, a report someone opens quarterly. The data says a page ranks in position 14 for a query with real volume, or that impressions on a section have been declining for two months, or that a query you should own returns a page that doesn’t answer it — and then the finding sits in a slide, because acting on it means briefing, writing, reviewing and publishing a change. Connecting Search Console puts that data next to the thing that can act on it.

What Grady can do

This connection is read-only against Search Console. Gradial reads performance data; it does not submit sitemaps, request indexing, or change any Search Console setting.

Prerequisites

  • A Search Console property for each site you want Gradial to read
  • At least Restricted access to that property for the account authorizing the connection
  • Permission in your organization to connect a Google account to Gradial

Set up the connection

1

Confirm your property type

Note whether each property is a domain property (shown as sc-domain:example.com) or a URL-prefix property (shown as https://www.example.com/). Both are supported, and the distinction matters: a domain property covers every subdomain and protocol, a URL-prefix property covers only what its prefix matches.
2

Add the integration in Gradial

Go to Settings → Integrations, find Google Search Console under Analytics, and select Connect. Authorize with a Google account that has access to the properties you want to read.
3

Select the properties

Choose which Search Console properties this connection covers. You can select more than one — a multi-brand or multi-region estate usually wants several.Only the selected properties are readable. Adding a property later is a change to this integration, not a new connection.
4

Confirm

Ask Grady for a summary of organic performance over the last 28 days. If the numbers match what you see in Search Console, the connection is working.

Using it

Search Console data is most useful when the question is specific. Some starting points:
The last step in each case is the useful one: Gradial can execute the change it recommends, in your CMS, through your existing review and approval path.
Search Console covers traditional organic search. For how your brand appears in AI answer engines — a different dataset and a different set of fixes — see Generative Engine Optimization (GEO) and GEO Monitoring. Teams increasingly need both.

Who this is for


Availability

Access: Must be enabled for your organization. Contact your Gradial team to get access.