Reference → Google Search Console

Google Search Console

How Google Search Console connects into SGEN — search performance and indexing visibility.

Google Search Console (GSC) connects into SGEN as the search-performance and indexing-visibility layer. Once configured, GSC data feeds into the platform so operators see search impressions, clicks, average position, and indexing state inside the SGEN administrative surface. This page is the Reference definition of the GSC integration — what it covers, where the data appears, and what the dependency posture looks like.

What is this for?

Read this page when you want the structural definition of the GSC integration in SGEN — what role it plays in the platform's search-performance layer, where the data lands, and what the operator should expect when the connection is healthy versus unhealthy.

Good use cases

  • You are scoping SEO work for an SGEN site and need to know how GSC fits.
  • You are explaining to a stakeholder how SGEN handles connected search-performance data.
  • You hit a "search impressions are stale" question and want the model laid out.
  • You are designing internal SOPs around SEO handoff.

What NOT to use this for

  • Step-by-step GSC setup procedures — open the relevant Guide.
  • GSC product documentation — Google's documentation, not here.
  • Per-customer SEO audit work — out of scope.
  • Per-release shipped behavior change — open What's New or Changelog.

How this connects to other features

Definition

GSC in SGEN is a connected search-performance service. The platform pulls GSC data into the SGEN administrative surface so operators see search impressions, click-through, average position, and indexing state inside SGEN rather than only in the GSC web app.

The defining property is direction. GSC is a one-way ingest — search-performance data flows from Google into the SGEN surfaces that consume it. SGEN does not push data back to GSC.

Purpose

The purpose of this page is to define the GSC integration as a Reference layer. It explains the connection model, where the data appears, what the dependency posture looks like, and how the integration pairs with the admin SEO module.

Scope

This page covers the GSC integration at the Reference level.

The page covers:

  • The connection role of GSC in the SGEN search-performance layer.
  • Where GSC data appears in the admin.
  • The dependency posture (healthy vs unhealthy).
  • The boundary against GSC product documentation.
The page does not cover:
  • Per-step setup procedures — Guides.
  • GSC product detail — Google documentation.
  • Custom URL inspection workflows beyond platform defaults — out of scope.

Connection model

GSC connects into SGEN through the platform's standard integration surface. The connection is per-site (each SGEN site can be paired with its own GSC property).

Per-site property

Each SGEN site can be paired with a GSC property. The pairing happens in the per-site settings; the data flows through the GSC property and into the per-site SGEN search-performance surface.

Synchronized data

Search impressions, click-through count, click-through rate, average position, indexed-page count, indexing-state signals.

Site · SEO · Search performance

Last 28 days

14,287

Impressions

+12% vs prev

892

Clicks

+8% vs prev

6.2%

CTR

-0.4pp vs prev

14.1

Avg position

+0.6 vs prev

Top queries
sgen platform overview1,247 imp · 92 clicks
multi-site cms892 imp · 68 clicks
website builder agencies614 imp · 41 clicks

Where GSC data appears

GSC data lands in two SG-Admin surfaces.

SEO module

The SEO module inside the admin shows the per-site search-performance view — top queries, impression and click trends, indexing state, position changes.

Analytics module

The Analytics module surfaces search-performance signals alongside the GA4 site-analytics view, so operators see search and on-site behavior in the same context.

Dependency posture

GSC in SGEN depends on the GSC property being verified and the connection between the property and the SGEN site staying valid.

Healthy connection

Search-performance data flows at the GSC publish cadence (typically a 1-2 day delay from Google's side). Operators see fresh data in the SEO module within that cadence.

Unhealthy connection

Data stops refreshing. The SEO module shows stale data; the connection panel surfaces the unhealthy state with a status indicator and a reconnect prompt.

Constraints and boundaries

GSC is a Reference area for the connected search-performance service. It is not a substitute for GSC product documentation or for SEO audit work.

Use this Reference for:

  • Understanding the GSC connection role in SGEN.
  • Confirming where search-performance data surfaces.
  • Diagnosing connection-health questions at the structural level.
Do not use this Reference for:
  • GSC product configuration — Google's documentation.
  • SEO audit work — out of scope.
  • Step-by-step setup — Guides.

Public boundary

This page is intentionally public-safe. It does not expose GSC credentials, exact API surfaces, or protected operational identifiers.

Examples

Example 1 — Operator reviews search performance

The operator opens the admin → SEO and reviews the last 28 days of GSC data. The Reference frames what to expect; the operational surface delivers it.

Example 2 — Stakeholder asks "what is our search position trending toward?"

The platform lead opens this page, then opens the admin → SEO with the stakeholder. The Reference grounds the conversation in the platform's GSC view rather than requiring the stakeholder to learn the GSC web app.

Example 3 — Connection goes unhealthy after a property change

A property-side change breaks the connection. SG-Admin SEO module shows stale data. The operator opens this page, confirms the unhealthy-connection symptom matches, and reconnects via the connection panel.

Documentation guidance

Use this page as the structural definition for the GSC integration. Procedural detail belongs in Guides; per-release behavior change belongs in What's New or Changelog.

Reading order

Open this page when scoping search performance or troubleshooting search-data-staleness questions. Pair with SG-Admin SEO Reference for the per-site surface.

Related reading

Vocabulary cross-reference

  • GSC property is the Google-side configuration that defines a search-measurement scope for a site.
  • Verification is the GSC-side process that confirms ownership before data flows.
  • Search performance covers impressions, clicks, CTR, and average position.
  • Indexing state is the GSC-reported status of how Google sees the site's pages.
  • Publish cadence is the GSC-side delay (typically 1-2 days) between event and data availability.

Maintenance discipline

When the GSC integration changes across releases (new data surface, new connection panel, new measurement detail), update this Reference and log the change in Changelog. The page stays valuable because the connection model stays small.

On this page