Fix Google authorization and property access problems

Resolve cancelled OAuth, unavailable callback, missing scope, and unmatched property issues.

Last checked 20 August 2026

Use the message in Couldn’t connect Search Console to separate a browser authorization problem from a property matching problem. A successful Google sign-in does not guarantee that TechDash can find a supported property.

Google sign-in was cancelled

This appears when you deny access, close the authorization flow before it returns, or Google returns access_denied.

  1. Return to TechDash and close Couldn’t connect Search Console.
  2. Select Connect to Google Search Console again.
  3. Keep the Google page open until you approve access or intentionally cancel.
  4. Authorize the read-only Search Console permission.
  5. Wait for TechDash is connected. You can close this tab and return to the app.

If your organization blocks unapproved OAuth apps, ask the Google Workspace administrator whether TechDash is permitted. Repeated attempts cannot override an administrator policy.

The local callback did not complete

TechDash starts a temporary listener on 127.0.0.1 and asks your normal browser to return the authorization code to a random local port. The callback does not require an inbound internet connection, but local firewall, browser, VPN, or endpoint security rules can still block it.

Symptoms include a browser error after Google approval, TechDash continuing to show Connecting…, or the sign-in timing out.

Try these checks:

  1. Make sure TechDash remains open throughout authorization.
  2. Do not copy the callback URL to another computer or mobile device. It points to the computer running TechDash.
  3. Allow your browser to open http://127.0.0.1 for this one-time callback.
  4. Temporarily test without a proxy or VPN that rewrites local addresses.
  5. Check whether endpoint security blocks local listeners or random loopback ports.
  6. Cancel the incomplete attempt before starting one new attempt.

The callback page is plain local HTTP by design. OAuth protects the authorization code with PKCE and validates a random state value.

Google sign-in succeeded, but no property matched

When the account has no active Search Console properties, TechDash tells you to add either a root URL-prefix property for the displayed origin or a Domain property for the displayed registrable domain.

When properties exist but none match:

  • Confirm you authorized the Google account visible in Search Console's property selector.
  • Confirm the account is an owner, full user, or restricted user for the property.
  • For a URL-prefix property, match the website protocol. http:// and https:// are different.
  • Use a root URL-prefix property. TechDash does not select a property limited to /shop/ or another path.
  • A www and non-www root property can match one another in TechDash, but unrelated subdomains cannot.
  • For a Domain property, use the registrable domain requested in the error.

TechDash lists properties but does not create them, verify ownership, or ask another owner to grant access.

The token request failed

After the callback, TechDash exchanges the authorization code with Google. Network filtering, a Google service error, or an invalid OAuth response can stop this step. Keep the exact error text. Retry once on a stable connection. If it repeats, confirm that accounts.google.com, oauth2.googleapis.com, and Google APIs are permitted by your network policy.

Access stopped after a successful connection

Access tokens expire quickly, so TechDash normally uses the saved refresh token to obtain another one. Refresh can fail if the Google user revoked TechDash, the token expired or was invalidated, or the user's property permission changed.

The app can report Google account needs reconnecting. or This Google account cannot access that Search Console property. However, the current connected UI shows a Search Console badge and has no reconnect button. Keep the error and contact TechDash support for connection-management guidance. Do not delete the website as a shortcut unless you accept losing its local records.

Rate-limit and daily-quota messages during imports or scheduled work are different. They do not mean OAuth failed and do not open SEO incidents.

Sources

Related articles