Google & Search Console
Connecting Google & Search Console
1. Open Connections in the left sidebar and pick the Google tab. 2. Click "Connect Google account". 3. Complete the OAuth flow. 4. Grant all requested permissions. We ask for Drive (which covers Docs and Sheets), Slides, Calendar, Blogger, YouTube, Google Business Profile, Photos and Search Console. They are requested together because a campaign can use any of them; nothing is used on a campaign that has not enabled it. Connect multiple accounts if you manage several clients or need extra Drive quota - each tool lets you select which account to use. Search Console access is included automatically: every Google account you connect appears as a GSC connection too, so indexation tracking works without a separate flow.
Why Search Console matters
GSC is Google's source of truth for indexation status, and the only one Ranking Factory uses. When connected, it reads "Indexed / Not Indexed / Soft 404" from the URL Inspection API for the pages we published on a site your connected account owns - asked about each night before any other page. A page Search Console has read as indexed stays counted as indexed in What's working on a night it cannot be reached; an answer Search Console gives no verdict for leaves the page not checked. A page no connected property covers is shown as "Not checked" - never as indexed and never as not indexed - and is left out of every indexation percentage. That includes every Google Doc, Sheet, Slides deck, Google Site and Blogger post: Google owns those hosts, so no customer's Search Console can inspect them. A page whose own address answers 404 or redirects is shown as gone, on its own line: it is not counted as not indexed, and it is in no indexation percentage. Indexation is never read from Google's search results page. Readings taken that way on or before 7 Oct 2026 are shown as not checked until Search Console reads the page, and their first-indexed dates are removed.
Multiple accounts and properties
You can connect as many Google accounts as you need. Each appears as its own row on the Connections → Google tab; expand a row to see its accessible Search Console properties and optional default property. When creating or editing a campaign, the Search Console picker lets you choose: - Account: any of your connected GSC accounts, or "Auto" (let the system match by URL host). - Property: a specific property accessible by that account, or the account's default.
Auto mode
If a campaign has no GSC selection, the indexation engine tries each connected token whose default property matches the campaign URL's host. If none match, the page is shown as not checked. Auto mode is fine for most setups but explicit selection is recommended when one Google account owns multiple variants of the same domain.
Managing permissions & troubleshooting
If you get permission errors, open Connections → Google and use the Test or Disconnect buttons on the affected row, then reconnect. No properties appear? The Google account may not have Search Console access, or the Search Console API may be disabled in the linked Google Cloud project. The Test button surfaces the exact error. "Token expired" errors mean the user revoked access in their Google account; reconnect to fix.
Use separate Google accounts for each client to keep their assets organised and isolated. Pick a property explicitly when a campaign covers a sub-path or sub-domain that another GSC property in the same account also covers.