DataSag guides · Updated 27 October 2026

Connect Google Search Console to DataSag

To view Google Search performance in DataSag, open your project, choose Search performance, connect Google Search Console, select a property, and sync the report. You can use a read-only service account or Google sign-in when available. Website analytics tracking alone does not provide Google search-query data.

Prepare the right property

Use the Search Console property that covers the public website you want to measure. A domain property and a URL-prefix property can cover different sets of addresses. Check the selected protocol and hostname before you compare its results with your website analytics.

You need access to the property before DataSag can read its reports. Creating a DataSag project does not verify ownership in Google. If the site is new to Search Console, complete Google verification first. An empty property can also mean Google has no reportable activity yet.

For an organization, decide who owns the connection and who can remove access. Keep service account keys out of website source code, public repositories, support messages, and browser-side configuration. The DataSag connection form is separate from your public tracking snippet.

Connect with a service account

DataSag includes a service account path in the Search performance connection settings. This path uses a JSON key rather than your Google password. Enable the Search Console API in the Google Cloud project associated with the account.

  1. Create a Google Cloud service account and download its JSON key.
  2. In Search Console, open Settings, then Users and permissions.
  3. Add the service account email to the intended property with Restricted access as described in the DataSag setup.
  4. Open your DataSag project and choose Search performance.
  5. Select Google Search Console and paste the JSON key into the connection form.
  6. Save the key, choose the property from the returned list, and save the property selection.

Use Google sign-in when available

If the connection settings show Connect with Google sign-in instead, you can authorize access through that route. Select a Google account with access to the correct Search Console property. After authorization returns you to DataSag, choose and save the property.

If no properties appear, verify that the account or service account has access to the intended property. A successful connection does not guarantee that every property you manage is visible to those credentials. Recheck access in Google before repeatedly creating new DataSag connections.

Sync and interpret the report

Choose Sync search data after the property is saved. DataSag requests a 28-day window of finalized web-search data and leaves out the most recent three days. The report also compares page clicks with the preceding 28-day period.

The summary shows clicks, impressions, click-through rate, and average position. Queries and Pages list returned rows. Pages losing clicks highlights declines among the returned page data. Search Console dates use Pacific time, so daily totals may differ from a report using another timezone.

DataSag requests up to 1,000 rows for each dimension and shows the top 50 query and page rows in the interface. Google can omit anonymized queries. Treat the displayed query table as observed search demand, rather than a complete list of all searches that involved your website.

Investigate a decline before rewriting a page

Open the page that lost clicks. Confirm that it still returns a successful response, has the intended canonical address, and contains the expected content. Check whether a release changed the page title, removed an internal link, or moved the answer behind a client interaction.

Compare impressions and clicks together. Fewer impressions and fewer clicks call for a different investigation from steady impressions with fewer clicks. Look at the underlying Search Console report when you need country, device, or other dimensions beyond the DataSag summary.

Do not join an individual search query to a named visitor. Search reporting and browser visits are separate datasets. Use page-level patterns to choose what to investigate next, then inspect the actual page and the customer task.

Keep a useful history

Save a report before a substantial content release and record the changed URLs. Sync again after enough finalized data is available for a useful comparison. Saved reports remain available after you disconnect a provider, while removing report history is a separate action.

If a sync fails, read the error and check permissions or reconnect as directed. A failed request is not an empty search result. Preserve the last successful report so you can distinguish an access problem from a change in search demand.

Sources

Continue with a practical guide

Install analytics on your platform or explore DataSag search and AI visibility.