Daylytix pulls live data from Google Search Console during every audit — giving you click trends, top queries, crawl stats, and CTR opportunity analysis right inside your report. There are two ways to connect: OAuth (quickest, for personal use) and a Service Account JSON (recommended for agencies running audits on client sites).

Which method should I use?

Method Best for Setup time
OAuth login Auditing sites in your own GSC account ~1 minute
Service Account JSON Agencies with multiple client properties; automated scheduled audits ~10 minutes

Method 1 — OAuth Login

OAuth lets Daylytix request read-only access to Search Console on your behalf using your Google account. No credentials are stored — only the access token is saved.

1

Open Settings

In the Daylytix dashboard, click the Settings icon in the left sidebar, then navigate to the Integrations tab.

2

Click "Connect GSC"

Under the Google Search Console section, click the blue Connect GSC button. You will be redirected to Google's OAuth consent screen.

3

Log in and grant permissions

Select the Google account that owns or has access to your GSC properties. Grant Daylytix read-only access to Search Console data when prompted. No write permissions are requested.

4

Return to Daylytix

You will be automatically redirected back to the Integrations page. A green checkmark will confirm the connection. Daylytix now has access to all GSC properties in that Google account.

✓
Data is fetched automatically. Once connected, GSC data for the matching domain is fetched automatically every time you run an audit. You do not need to reconnect between audits.

Method 2 — Service Account JSON

A Google Cloud service account acts like a robot user with its own email address. You share your GSC property with that email, and Daylytix authenticates as that account during audits. This method works across multiple client properties without requiring OAuth tokens per user.

Step 1 — Create a Service Account in Google Cloud

1

Open Google Cloud Console

Go to console.cloud.google.com and create a new project (or select an existing one). Name it something recognizable like Daylytix SEO.

2

Enable the Search Console API

In the left menu, go to APIs & Services > Library. Search for Google Search Console API and click Enable.

3

Create a Service Account

Go to IAM & Admin > Service Accounts and click Create Service Account. Give it a name such as daylytix-gsc. You do not need to assign any Cloud IAM roles — click through to finish.

4

Download the JSON key

Click on your new service account, go to the Keys tab, click Add Key > Create new key, choose JSON, and download the file. Keep this file secure — it grants access to your GSC data.

Step 2 — Add the service account email to GSC

1

Copy the service account email

In Google Cloud Console, your service account email looks like: daylytix-gsc@your-project.iam.gserviceaccount.com. Copy it exactly.

2

Open Google Search Console

Go to search.google.com/search-console, select the property you want to audit, then click Settings > Users and permissions.

3

Add the service account as a user

Click Add user, paste the service account email, and set the permission to Full (not Restricted). Owner permission is not required, but Full is necessary for Daylytix to query the Search Analytics API.

⚠
Important: The service account must be added to each GSC property you want Daylytix to read. If you manage 10 client sites, add the service account email to all 10 properties.

Step 3 — Upload the JSON to Daylytix

1

Go to Settings > Integrations

In Daylytix, open Settings and click the Integrations tab.

2

Upload the JSON file

Under Google Search Console > Service Account, click Upload JSON Key and select the file you downloaded from Google Cloud. Daylytix stores the credentials securely in your local config.

3

Test the connection

Click Test GSC. Daylytix will attempt to list your GSC properties. If successful, you will see a list of verified properties. If you see an error, check that the service account email was added to GSC and the Search Console API is enabled.

What data is fetched from GSC?

Once connected, the following GSC data is fetched automatically for the audited domain during each audit run:

  • Top queries — keyword, clicks, impressions, CTR, and average position for the last 28 days
  • Crawl statistics — pages crawled per day, bytes downloaded, response time
  • Index coverage — valid, error, excluded, and warning page counts
  • CTR opportunity analysis — pages with high impressions but low CTR, ranked by potential
  • Position distribution — keyword counts ranked in top 3, top 10, and top 20

Troubleshooting

Domain URL format must match exactly

⚠
URL format mismatch is the most common connection issue. The URL you enter in Daylytix when starting an audit must match the GSC property exactly — including the protocol and subdomain.

For example, if your GSC property is https://www.example.com, entering https://example.com (without www) will return no GSC data. These are treated as separate properties in GSC.
Daylytix audit URL GSC property Result
https://www.example.com https://www.example.com ✓ Match — GSC data loaded
https://example.com https://www.example.com ✗ No match — no GSC data
http://www.example.com https://www.example.com ✗ No match — protocol differs
Domain property: sc-domain:example.com sc-domain:example.com ✓ Match — works for Domain properties

Other common errors

  • "Permission denied" — the service account email has not been added to the GSC property, or permission level is set to Restricted instead of Full.
  • "API not enabled" — the Google Search Console API has not been enabled in your Google Cloud project.
  • "No data returned" — the property has fewer than 28 days of data, or the site has very low traffic.
  • OAuth token expired — click Reconnect GSC in Settings to refresh the OAuth token. Tokens expire after a period of inactivity.
ℹ
GSC data covers the last 28 days only. This is a limitation of the Google Search Console API and applies to all third-party tools. Historical data beyond 28 days is not available via the API.