Fixing a failed Google connection
Most failed Google connections come down to account access. Check that first, then try reconnecting.
You tried to connect Google Search Console or Google Analytics 4 and the connection failed or the property you expected did not appear.
Most common cause: the Google account does not have access
Vyera can only show properties the Google account you signed in with can already access. If your usual work account is not the one with access to the property, sign out of Google and reconnect using the correct account.
Other causes, by how often they happen
Note
These are ordered by frequency. Work through them in order rather than jumping to the last one.
- Your access to the property is below the level required. See Search Console permissions required for what is needed.
- The authorisation was cancelled or timed out partway through. Start the connection again from Integrations rather than retrying from a stale screen.
- Your organisation restricts which third-party apps can be authorised on Google Workspace. Ask whoever manages this to allow Vyera before trying again.
- The property was recently added, removed, or renamed on the Google side, so it has not appeared yet.
If none of this fixes it
Send the integration you were trying to connect and the Google account you used to the team using the request option below.
Was this useful?
Related articles
- Connect Google Search Console
Connect Search Console to add your own search visibility data alongside your competitor data.
- Connect Google Analytics 4
Connect Google Analytics 4 to add your own traffic data alongside your competitor data.
- Available integrations
Vyera integrates with Slack, Google Search Console and Google Analytics 4.
- I cannot connect Google
This is usually an account access or permission issue. See the full walkthrough for the fix.
Still stuck?
Send this to the team and we will pick it up.