Google Search Console
Connect GSC to see real clicks next to every change — and Google's indexing verdicts.
SeoSwift tells you what changed; Google Search Console knows what it cost or earned. Connect the two and every change gets traffic context — available on all paid plans (Standard and up).
Connecting
- 1Open the site's Settings tab and find the Google Search Console section.
- 2Click connect and sign in with the Google account that has access to the site's GSC property.
- 3That's it — we auto-match your verified GSC property (domain properties preferred, since they cover www and non-www) and start the first sync.
Data syncs daily at 06:00 UTC. Note that Google finalises Search Console data with a lag of about three days — so "latest" always means "latest Google will vouch for", not this morning.
What it unlocks
- Traffic-weighted changelog context — changelog rows show real click data, so a title change on a page earning 4,000 clicks a month reads very differently from one on a page earning 4.
- Top Pages at Risk — the Health tab ranks pages where an SEO issue and real traffic collide, so you fix what actually matters first.
- Clicks momentum — your dashboard site cards show whether clicks are trending up or down over the recent period.
- CTR-drop alerts — we compare a page's click-through rate before and after a title or description change and email you when it dropped. Each change needs about two weeks of after-data before we judge it. See Changes & Alerts.
- The Indexation tab — see below.
The Indexation tab
The Indexation tab has two layers. The first is ours and needs no GSC connection: a deterministic census of the latest crawl — every page bucketed as indexable, noindexed, canonicalised elsewhere, redirected, or erroring, plus the count of URLs your robots.txt kept us out of. It covers every crawled page and adds up, every time.
The second layer is Google's: with GSC connected we ask Google's URL Inspection API for its verdict on your pages. Google caps how many inspections a property gets per day, so we spend that budget as a rolling sample — a batch of pages each day, verdicts labelled with how fresh they are. Over days, coverage builds. We'd rather show you an honestly-labelled sample than pretend to a full census Google doesn't offer anyone.
Privacy & disconnecting
- We request a read-only Search Console scope — we can read your GSC data, never change it.
- Your Google tokens are encrypted at rest on our servers.
- Disconnect any time from the same Settings section — stored tokens and cached GSC data are deleted immediately.
Why is my GSC data a few days behind?
That's Google's reporting lag, not a sync problem — Search Console data is finalised roughly three days in arrears, for everyone.Still stuck? Email hello@seoswift.io — a human reads it.