Skip to content

Connecting Google (Search Console and GA4)

Google is WordPresto’s richest free data source. When it is connected and mapped, the project ingests real search queries, pages, clicks, impressions, average position and GA4 engagement — all persisted as project intelligence. Connecting alone is not enough; WordPresto also needs to know which Search Console site and which GA4 property belong to this project.

Open Integrations → Google and authorise the connection. WordPresto asks only for read-only scopes (Search Console and Analytics). It never calls a Google write API.

Search Console and GA4 are resolved independently, so one can be ready while the other still needs attention. WordPresto tries to auto-map the single site or property that matches your project’s domain. When it cannot:

  • Mapping required — no resource is mapped yet. Pick the correct Search Console site and GA4 property for this project.
  • Choose one — more than one resource could match. WordPresto never guesses; you select.

A GA4 property id and a Search Console site URL are different things and are never interchanged.

If Google is connected but data is not arriving, WordPresto reports the exact reason rather than failing silently:

  • Reconnect required — the token has expired or been revoked. Reconnect Google.
  • Missing scope — the read-only Search Console or Analytics scope was not granted. Reconnect and approve both.
  • Access denied — the account has no access to that resource, or the API is not enabled. A reconnect cannot fix this; use the right account or enable the API.

Integrations → Google shows the current status for each channel, so you can fix the specific cause.

Once mapped, ingestion persists Search Console queries and pages (with clicks, impressions, CTR and average position) and GA4 pages and engagement as source-labelled datapoints. These feed Visual Intelligence, the insights Emma volunteers, and the keyword and cannibalisation analysis.