Exact data
GA4 accounts/properties plus authorized Data API reports for dimensions, metrics and date ranges such as landing page, session source/medium, sessions, key events and purchase revenue.
Live integration · measurement
Each signed-in customer authorizes their own Google account, selects the correct GA4 property and grants SEOForge read-only reporting access. Analytics evidence informs measurement; it does not grant publishing authority.
LANDING PAGE WINDOW
/guides/migration
Organic sessions · key events · revenue
Attribution limits visible
GA4 accounts/properties plus authorized Data API reports for dimensions, metrics and date ranges such as landing page, session source/medium, sessions, key events and purchase revenue.
Google OAuth analytics read-only scope for the authorizing user; the selected property is bound to the SEOForge site.
Edit GA4 configuration, create events, alter attribution, access a property the user cannot read, or prove an SEO change caused every observed conversion.
Credential protection
Setup
Open site settings after paid onboarding
Evidence, owner and next state remain visible.
Connect a Google Analytics account
Evidence, owner and next state remain visible.
Approve read-only analytics access
Evidence, owner and next state remain visible.
Select the correct GA4 property
Evidence, owner and next state remain visible.
Run a dated baseline report
Evidence, owner and next state remain visible.
Example workflow
SEOForge defines a pre/post observation window, queries the refreshed landing page’s organic sessions and configured key events, records deployment timing and flags seasonality or attribution gaps. Search evidence and GA4 results remain distinct.
GA4 reflects the customer’s tagging, consent, attribution and event configuration. Missing tags, thresholding, sampling/API behavior and privacy controls can limit conclusions; SEOForge does not repair analytics configuration through this read-only connection.
Questions
No. Connections are customer-owned and site-scoped; the platform does not use one shared Analytics identity.
Yes, with a separately created site-bound read-only MCP token. It does not expose the OAuth credential or production tools.
Paid deployment · human authority
Choose a plan, authorize read-only access and confirm the baseline property before agents measure outcomes.