Google Integrations

Two of your four ModelScore components — Brand Demand and Authority Transfer — are calculated from Google data. Brand Demand pulls branded search volume from Google Search Console. Authority Transfer pulls organic traffic quality from Google Analytics 4. Without these connections, those components return null and your ModelScore is calculated from the other two components only (AI Citation and Technical Readiness).

This article covers how to connect each integration, what they unlock, and what to do if they break.

What each integration powers

Google Search Console (GSC): – Branded search impressions and clicks – Branded search share (what % of your impressions are from queries that include your brand name) – This is your Brand Demand component (25% of ModelScore)

Google Analytics 4 (GA4): – Organic traffic volume – Organic traffic quality (engaged sessions, conversions if configured) – This is your Authority Transfer component (20% of ModelScore)

If your stack runs on Adobe Analytics rather than GA4, see API Keys (BYOK) for the Adobe path. CiteMetrix can use either; GA4 is consulted first if both are configured.

Connecting Google Search Console

Prerequisite: You need to be a verified owner or user of the Search Console property for the domain you want to track. If you’ve never set up GSC for your domain, do that first at search.google.com/search-console before continuing here.

Connect:

1. In the dashboard, navigate to Settings → Integrations
2. Click Connect Google Search Console
3. You’ll be redirected to Google’s OAuth consent screen
4. Sign in with the Google account that owns/has-access-to the Search Console property
5. Grant the permissions Google asks for (read-only access to your Search Console data)
6. You’ll be redirected back to CiteMetrix with a list of properties your Google account can access
7. Pick the property that matches the domain you’re tracking (often https://yourdomain.com/ or sc-domain:yourdomain.com)
8. Click Save

You’re connected. Brand Demand will populate on the next ModelScore calculation, typically within a few hours of the next scheduled scan.

What CiteMetrix actually pulls from GSC: the last 28 days of search performance data, broken into branded queries (queries that contain your brand name or close variants) and non-branded queries. We pull aggregate metrics — total impressions, total clicks, average position. No individual user data. The OAuth scope is read-only and limited to Search Console; it does not grant access to Gmail, Drive, or anything else in your Google account.

Connecting Google Analytics 4

Prerequisite: You need GA4 set up for your domain with at least 30 days of data. (CiteMetrix’s Authority Transfer score works best with 30+ days; with less data it’ll still calculate but the trend won’t be meaningful yet.)

Connect:

1. Settings → Integrations → Connect Google Analytics 4
2. Sign in with the Google account that has GA4 access
3. Grant read-only permissions to GA4 data
4. Pick your GA4 property from the list (you’ll see all properties your account can access)
5. Pick the data stream (web), if you have multiple
6. Save

What CiteMetrix pulls: organic-channel sessions, engaged sessions, and conversions if you’ve configured them. We use the GA4 Reporting API with read-only scope. No user-level data; just aggregated metrics over a 30-day rolling window.

Multi-domain operators

If you have multiple domains (Pro/Agency plans), each domain has its own GSC and GA4 connection. The connection lives at the per-domain level, not the account level. A few consequences:

• You can connect different Google accounts to different domains. Useful when you manage Client A’s properties through one Google account and Client B’s through another.
• A single Google account can be connected to multiple of your domains, as long as that account has access to each Search Console property and GA4 property. Most agency operators do this — one agency Google account, connected across all client domains.
• Disconnecting one domain’s integration doesn’t affect the others.

Troubleshooting

“No data” appearing in Brand Demand or Authority Transfer for a connected domain.

1. Confirm the connection in Settings → Integrations shows a green “Connected” status
2. Click the Test Connection button — this fires a sample API call and reports any auth issues
3. If the test fails, the OAuth token may have expired. Reconnect by clicking Disconnect and then Connect again.
4. If the test passes but data is missing, the connected property may not have data yet (especially common with new GA4 setups).

“Property mismatch” warning.

This appears when the connected GSC or GA4 property doesn’t match the domain you’re tracking in CiteMetrix. Common cause: you connected a property for acmewidgets.com to a CiteMetrix domain registered as acme-widgets.com (note the hyphen). Disconnect, confirm your domain spelling, reconnect with the correct property.

“Insufficient permissions.”

The Google account you connected with doesn’t have access to the property you’re trying to use. Either: – Use a different Google account that has access – Have an admin grant the connected Google account access to the GSC property or GA4 property

Connection breaks after a Google account password change.

Some Google security events (password change, 2FA setup, account recovery) invalidate existing OAuth tokens. Reconnect to refresh.

Permissions and security

CiteMetrix requests the minimum Google API scopes needed:

• For GSC: webmasters.readonly — read-only access to Search Console data
• For GA4: analytics.readonly — read-only access to Analytics data

We do not request access to Gmail, Drive, Calendar, or any other Google service. The scopes shown on the OAuth consent screen reflect this — you should see only Search Console / Analytics in the permission list.

OAuth tokens are stored encrypted in your user record. We do not access your Google account beyond the API calls needed to populate your ModelScore. Tokens can be revoked at any time: – From your Google account: myaccount.google.com/permissions — find CiteMetrix in the list and click Remove – From CiteMetrix: Settings → Integrations → Disconnect

Either revocation breaks the connection cleanly; data already pulled into your ModelScore stays, but no further data is pulled until you reconnect.

Disconnecting

If you ever need to disconnect (changing Google accounts, ending a client engagement, troubleshooting):

1. Settings → Integrations
2. Click Disconnect next to GSC or GA4
3. Confirm

Disconnecting removes the OAuth token from your CiteMetrix account but doesn’t delete historical data. Brand Demand and Authority Transfer for the period you were connected stay in your history. New ModelScore calculations from this point forward will exclude these components (and the score will redistribute among the connected components, as documented in Understanding Your ModelScore).

Why these integrations matter

It’s tempting to think of GSC and GA4 as “nice to have” since CiteMetrix’s core feature (AI citation tracking) doesn’t need them. But Brand Demand and Authority Transfer catch movements that AI Citation alone can’t see:

• A drop in branded search (Brand Demand) often precedes a drop in AI citation by weeks or months. AI’s training and retrieval pipelines weight content from sites with high branded search volume — if your branded demand is falling, your AI visibility is on borrowed time.
• Organic traffic quality (Authority Transfer) reflects whether the citations you’re getting actually drive engagement. AI mentioning you matters less if nobody clicks through; engagement data is the receipt.

Connecting both is a 5-minute job that meaningfully improves your dashboard’s signal quality. We strongly recommend it for every account.

Next steps

• If you haven’t connected GSC and GA4, do it now — Settings → Integrations
• After connecting, wait a day for the next scheduled scan to populate the new components, then check your ModelScore breakdown to confirm both are showing data
• If Adobe Analytics is your preferred platform, see API Keys (BYOK) for the Adobe configuration path