Connect a website to Google Search Console

Authorize Google and match a verified property to a TechDash website.

Last checked 20 August 2026

Connecting Search Console lets TechDash import high-click pages and use Google data in scheduled checks. The connection is optional and read-only. TechDash cannot edit your Search Console property, submit URLs, or request indexing.

Before you connect

You need a Google account with access to a matching, verified Search Console property. TechDash accepts Search Console's owner, full-user, and restricted-user permission levels.

The most predictable match is either:

A root URL-prefix property for the website's protocol and hostname, such as https://www.example.com/
A Domain property for the website's registrable domain, such as sc-domain:example.com

TechDash does not create or verify a property. If you still need one, add and verify it in Search Console before starting.

Connect the website

Open Websites in TechDash.
Select the website you want to connect.
Select Connect to Google Search Console beside the website name.
Your default browser opens Google's authorization page. Choose the Google account that can access the matching property.
Review and approve the requested Search Console access.
Wait for the browser message TechDash is connected. You can close this tab and return to the app.
Return to TechDash. The Connected to Search Console dialog shows the property TechDash matched.
Select OK.

After a successful connection, Connect to Google Search Console is replaced by a green Search Console badge. In Monitored Pages, the Import from GSC action also becomes available.

What happens during authorization

TechDash opens Google in your normal browser instead of an embedded sign-in window. It requests the webmasters.readonly scope, which permits reading Search Console properties, performance data, and URL Inspection data.

The desktop app creates a temporary callback listener on 127.0.0.1 using a random local port. Google returns the authorization result to that loopback address. The flow uses PKCE and a random state value to protect the authorization code. The callback is local to your computer and closes after it receives the result.

TechDash stores the matched property, permission level, access token, refresh token, and connection time in its local database. Tokens are encrypted with the local TechDash vault. The refresh token allows scheduled work to continue after the short-lived access token expires.

What becomes eligible

Once connected:

Import from GSC can request top pages from the previous 28 dates, ending yesterday.
Search Analytics checks can collect page, query, and search appearance rows from a rolling 7-day range each UTC day. The related queue is still labelled Search Console weekly.
Daily URL Inspection work can collect Google's stored fetch, crawler, canonical, and last-crawl evidence for enabled monitored URLs.

These tasks still depend on TechDash running, a usable license, an internet connection, Google access, and available API quota. Connecting does not immediately create incidents. The first Search Analytics run stores a baseline for the next daily rolling comparison.

If TechDash cannot connect

Read the exact message in Couldn’t connect Search Console. A completed Google sign-in can still fail if the account has no property that matches TechDash's rules. A firewall or endpoint security tool can also prevent the browser from returning to the local callback.

Do not start another connection while the Google browser flow is still open. Finish or cancel the current flow, then retry once. If the browser says the connection succeeded but TechDash remains unchanged, return to the app and allow the connection dialog to finish.