Understand the saved Search Console connection

Learn what the current app stores and how connection changes are handled.

Last checked 20 August 2026

After connection, TechDash replaces Connect to Google Search Console with a green Search Console badge beside the website name. The badge means a property and refresh token are saved for that TechDash website. It does not prove that Google access is still valid at this moment.

What TechDash stores

The local Search Console record contains:

  • The TechDash website ID
  • An encrypted access token
  • An encrypted refresh token
  • The access-token expiry time
  • The exact matched Search Console property
  • The permission level returned by Google
  • The connection time

TechDash stores this record in its local database. The token values are encrypted through the TechDash secret vault before they are written. Scheduled Search Analytics and URL Inspection work reads the record locally and sends requests directly to Google.

An access token is short-lived. When it has expired, TechDash uses the refresh token to ask Google for another access token and saves the replacement. This normally happens without customer action.

What the badge does and does not mean

The Search Console badge is based on the presence of a saved property and refresh token. TechDash does not call Google merely to render the badge.

The badge can therefore remain visible when:

  • The Google user revoked TechDash access
  • The refresh token was invalidated or expired
  • An owner removed the user's property permission
  • The property itself is no longer available to that user
  • A network policy blocks Google API access

The next import or scheduled request discovers the problem. Depending on the failure, customer-facing errors can include Google account needs reconnecting. or This Google account cannot access that Search Console property.

Current connection-management limits

The shipped website UI does not provide a button to:

  • Disconnect Search Console
  • Reconnect the existing Google account
  • Choose a different Google account
  • Change the saved property
  • View the property after the original success dialog closes

Do not infer those actions from the initial connection flow. Connect to Google Search Console is available only while the website is not marked as connected.

If authorization stops working, keep the exact error and contact TechDash support. The error may identify whether access, permission, quota, or a temporary Google failure is involved. A quota or rate-limit message does not require a new connection.

Deleting a website

Deleting the TechDash website removes the saved Search Console record. It also removes that website's:

  • Monitored URLs and check history
  • Custom checks
  • Sitewide results and incidents
  • Search Console metrics and inspections
  • Local Search Console quota records
  • Lookup records and saved assets

This is a destructive website deletion, not a supported disconnect workflow. Do not delete a website solely to change its Search Console property unless you intend to remove all of those local records and rebuild the website in TechDash.

Deleting the TechDash website removes local tokens, but the current code does not call Google's token-revocation endpoint. If you also want to revoke Google's grant, use your Google Account's third-party access controls.

Protecting and troubleshooting the connection

  • Keep the computer account and TechDash data directory protected.
  • Do not share database or support bundles without following TechDash support guidance.
  • Preserve the exact matched property shown in Connected to Search Console when documenting setup.
  • Treat Search Console as a saved-connection indicator, not a live health check.
  • Investigate authorization and permission messages before investigating site SEO.
  • Wait through rate limits and daily allowance messages instead of trying to reconnect.

Google recommends encrypting desktop-app tokens at rest, using PKCE, and handling refresh-token invalidation. TechDash uses PKCE and encrypted local token storage, but current UI limitations mean a failed saved connection can require support.

Sources

Related articles