Fix: Search Console properties won't load

When Reach says it could not load your properties, your Google account is usually still connected but Search Console isn't returning the list. There are three common causes, each with a clear fix.

1. The Search Console API is switched off

If Reach shows "Turn on the Search Console API," your Google account is connected but the Search Console API is disabled for it, so Google won't share your properties.

1. Open the Search Console API page in the Google Cloud console (Reach links straight to it).
2. Click Enable.
3. Return to the Reach hub and refresh the page, then pick your property.

2. Your OAuth consent screen is still in Testing

If Reach signs you out after about a week, your Google Cloud OAuth consent screen is likely still in Testing mode. In Testing, Google expires the access it granted after seven days, which drops the connection.

Publish the OAuth consent screen to Production in the Google Cloud console so the access no longer expires on that short cycle, then reconnect once.

3. The connection expired or was revoked

If Reach shows "Reconnect Google to keep reading your data," Google signed Reach out of your Search Console. This happens when the access Google granted expires or someone revoked it.

1. Click Reconnect on the Reach hub.
2. Approve read-only access again on Google's consent screen.
3. Reach picks up right where it left off.