Skip to main content
Search Console is the connector that turns the dashboard on. Without it, keyword performance, best-performing articles, and traffic trends have nothing to show.
We request one scope — webmasters.readonly. We can read your Search Console data and nothing else; we cannot change your property, submit sitemaps, or request indexing.

​
Before you start

You need to be a verified owner or full user of the property in Google Search Console. “Restricted” users can’t grant access to the performance data we read.

​
Step 1 — Start the connection

Project Settings → Integrations → Google Search Console → Connect. Google asks which account to use.
Google account chooser showing two accounts, continuing to seosorted

Pick the Google account that owns the Search Console property

While our own Google app finishes verification, the connection may run through Composio, our OAuth partner. In that case Google’s consent screen names Composio as the app asking for access, and the page you return through is branded SEOsorted. The access is the same read-only scope either way.
Choose the Google account that actually has the property. Signing in with the wrong account is the most common reason the property list comes back empty.
Google shows this warning for apps still going through its verification review. To continue, click Advanced, then Go to seosorted (unsafe).
Google warning page reading Google hasn't verified this app, with Advanced and Back to safety

The unverified-app warning and how to get past it

Then approve the read-only scope on the consent screen:
Google consent screen showing seosorted wants access to your Google Account

The consent screen — read-only Search Console access

​
Step 2 — Choose the property

Google sends you straight back to Choose a Search Console property.
Choose a Search Console property screen listing redbaton.digital, uxmagic.ai and seosorted.ai

Every verified property on the account; domain properties show as sc-domain:

Pick the property for this workspace and click Connect. Saving queues the first sync automatically.
We preselect a property only when it clearly matches your workspace domain, or when the account has exactly one. Otherwise nothing is selected and Connect stays disabled until you choose — a wrong pick here syncs the workspace against someone else’s site.
If you skip the picker, the card shows Setup required — choose a property and you can come back to it any time from the card’s ⋮ menu → Choose property. If the property you picked doesn’t match your project’s domain, the card shows Setup required — property doesn’t match your domain. Open ⋮ → Choose property and pick the property for this site — otherwise the workspace syncs another site’s data.
Search Console and Analytics cards showing Setup required — choose a property

Connected, still waiting for a property choice

Search Console card showing Site: seosorted.ai and Analytics showing its property

Configured — the card names the property it reads

Prefer a domain property (sc-domain:seosorted.ai) when you have one. It covers every subdomain and both http/https, so you don’t lose data to a protocol mismatch.

​
Step 3 — Sync

The first sync backfills 90 days and then runs every 24 hours. To pull fresh data on demand, click the ↻ icon next to the connector name. You’ll get a toast when it starts and another when it finishes, with the number of rows written:
The card then shows Last synced so you can tell at a glance how current the numbers are.

​
What you get

Once data lands, the dashboard fills in:
Dashboard showing impressions, clicks, traffic trend and best performing articles

The dashboard after a Search Console sync

  • Metrics — clicks, impressions, CTR and average position over 7/27/90 days
  • Best performing articles — your published articles ranked by search performance
  • Keywords — real queries you already rank for, with position tracking
  • Article traffic — per-article performance in the editor sidebar
Search Console data lags by 2–3 days at Google’s end, and a brand-new property has nothing to send. If you connected today and see zeroes, check the property directly in Search Console before assuming the connector is broken.

​
Disconnecting

Disconnecting stops all future syncs. Data already pulled stays in your workspace until you delete it.