Help & Guides

Step-by-step guides for every tool, recipe, and setting

Connected AccountsGoogle & Search Console

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 (Drive, Docs, Sheets, Calendar, Blogger, Photos, Search Console). Connect multiple accounts to create diverse link networks - 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. When connected, Ranking Factory uses the URL Inspection API for accurate "Indexed / Not Indexed / Soft 404" results instead of less reliable scraping.

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 it falls back to scraping. 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.