Connect Google Search Console and GA4
Link GSC for search discovery signals and GA4 for post-click behavior—two separate consents that power the Performance tab and Learning Loop.
Overview
CntX uses Google data to compare what you planned in the brief with what actually happens after publish. The two integrations are complementary and independently authorized:
| Integration | What it tells you | Primary use in CntX |
|---|---|---|
| Google Search Console (GSC) | Impressions, clicks, CTR, average position, top queries | SEO performance on reconciled URLs; GSC Learning Loop (keyword, intent, CTR opportunities) |
| Google Analytics 4 (GA4) | Sessions, engagement, key events on page paths | Behavioral Learning Loop (intro relevance, CTA coherence, conversion hints) |
GSC answers: Are the right queries finding this URL? GA4 answers: After they click, do they engage and trigger key events?
CntX is not a GA4 or GSC dashboard. Data syncs server-side into item-level performance views and editorial insight cards—no frontend calls to Google APIs. Metrics are signals, not full marketing attribution.
When to use
Connect analytics when:
- You publish blog or resource content and want brief-vs-reality feedback on live URLs.
- Audit findings recommend connecting GSC for richer SEO recommendations.
- You need to judge whether traffic is useful (engagement, key events)—not just visible in search.
- You are optimizing titles, intent alignment, CTAs, or planning derivative content from real demand.
You can connect GSC alone first; GA4 adds depth when OAuth and property access are ready.
Before you start
- Google account with access to the Search Console property and GA4 property for the site.
- Published or crawlable URLs that match the GSC property (domain or URL prefix).
- For GA4: a property receiving page data; key events configured in GA4 if you want conversion-style signals (otherwise CntX shows indicative limits).
- Content items with reconciled published URLs for item-level Performance (unreconciled URLs block comparison).
- Company-level OAuth storage: GSC and GA4 use separate `CompanyIntegrationCredential` records—connecting GSC does not grant GA4 access.
Steps
Google Search Console
- Open Settings → Integrations → Analytics (or follow the GSC prompt from Home or Audit findings).
- Click Connect Google Search Console and complete Google OAuth.
- Select the property (domain or URL prefix) that covers your published content.
- Confirm status Connected and note the linked property name.
- Open a published content item → Performance tab → verify GSC metrics and query list load for the chosen date range (7, 28, or 90 days).
- Expand Editorial insights (Learning Loop) to see brief-vs-GSC comparison and suggested actions.
Google Analytics 4
- In the same Integrations area, click Connect Google Analytics 4—this is a separate OAuth consent from GSC.
- Select the GA4 property to link to this workspace.
- Set the default analysis period (7, 28, or 90 days).
- Confirm status Connected. Data syncs when you open Performance or after connect (auto-sync).
- Return to a published content item Performance tab; GA4 sections appear when page-path data exists for the reconciled URL.
- Review Learning Loop cards that combine GSC and GA4 limitations—e.g. visibility without engagement, sessions without key events.
Expected result
- GSC shows Connected with the correct property; Performance tab displays impressions, clicks, CTR, position, and top queries per URL when data volume allows.
- GA4 shows Connected with behavioral indicators and key-event checks on the same Performance view when synced.
- Editorial insights executive summary states Aligned, Opportunity, Needs optimization, or Insufficient data based on GSC (and GA4 when present).
- Suggested actions appear (optimize title/meta, align intent, add FAQ, review CTA, plan BOFU piece, keep monitoring)—as guidance, not auto-edits.
- Audit exports can incorporate GSC-aware findings when Search Console is connected before or after audit completion.
Tips
- Low volume warnings on GSC or GA4 mean wait before rewriting the brief—signals are indicative only.
- Property mismatch errors mean the published URL sits outside the connected GSC property—fix property selection or URL reconciliation.
- GA4 key events not configured in the client property limits conversion insights—configure events in GA4, then refresh sync.
- Use GSC for SEO iteration; use GA4 to ask whether the intro and CTA match arrival intent.
- Neither integration replaces social listening, Media Watch, or Voice of Field—those cover off-site and field signals.
- Force refresh sparingly; sync is rate-aware and also runs when opening Performance.
Next step
Connect GSC first if you only do one integration today. Publish or reconcile URLs, then open Performance → Editorial insights on a live article. Add GA4 when you want engagement and key-event checks alongside query data. Run a content audit to baseline catalog gaps before acting on Learning Loop suggestions at scale.
Ready to try this in CntX?
Open the product and apply this guide to your workspace.