Connect Search Console and Google Analytics

Connect with Google in one click for Search Console and Google Analytics: which account to use, how LopeBase picks the right property, and common errors.

Updated 3 min read Open Connections

Search Console and Google Analytics both connect the same way: one Google sign-in, read-only, with the property picked for you when there is an obvious match. This covers both, since the steps and the problems are the same.

Connect with Google

  1. Open the connection

    From a property's page or Connections, open Google Search Console or Google Analytics and choose Connect with Google.

    Open Connections
  2. Pick the Google account

    Use whichever Google account already has access in Search Console or Google Analytics for that site. If you manage several products with different Google accounts, make sure you are signed in to the one that owns this property's data when Google's sign-in screen appears.

  3. Grant read-only access

    Google shows exactly one scope: read Search Console data, or read Google Analytics data. As a Restricted user (Search Console) or Viewer (Analytics), LopeBase can only read; it never changes your settings.

  4. Pick the property

    LopeBase lists properties under two headings: "Matches this product" (its address matches what the property is set up with) and "Other properties on this Google account". Pick one and press Use this property.

Which Google account to use

LopeBase connects by account, not by property on Google's side, so the account you sign in with has to be one that already has access to the right Search Console property or Analytics property. If you are not sure, check in Search Console or Google Analytics directly before connecting; adding the service account there first, under a different flow, is only needed for the older key-based setup, not for Connect with Google.

Common errors

No properties listed

This means the Google account you signed in with has no verified Search Console property, or no Google Analytics property with a web stream, for that site yet. For Search Console, add a Domain property for the site's domain; if its DNS is on Cloudflare, Search Console can verify it in one step, otherwise add the TXT record it shows, then come back and check again. For Analytics, make sure the property has a web data stream on that domain.

Connected, but it's the wrong account's data

Sign out of Google (or use a private window) and connect again, choosing the correct account when Google asks which one to use. There is a direct link to connect a different account right from the page that shows no matching properties.

Google access was not granted

If you close Google's consent screen, or untick the Search Console or Analytics permission on it, nothing is connected and LopeBase says access was not granted. Start the connection again and leave the one permission it asks for checked.

The sign-in did not finish, or took too long

Both show as plain errors on the property's page. Just start the connection again; nothing from a failed attempt is saved.

Where to go next

If something goes wrong

Something else? Contact us.

Search Console or Analytics says "no properties listed"

Verify a Domain property for the site in Search Console, or add a web data stream to the Analytics property, with the Google account you are connecting. Then reconnect; LopeBase checks again each time.

It connected, but shows another site's numbers

You were signed in to the wrong Google account, or picked the wrong property from the "Other properties" list. Open the connection and connect a different account, or pick the right property from the list.

It says Google access was not granted

You likely closed Google's permission screen, or unchecked the one permission it asked for. Start the connection again and allow it.

Only a workspace admin can connect Google

That's by design: connecting any source is an admin-only action. Ask a workspace admin to connect it.