Connecting Google and PostHog
Read-only access to Search Console, Google Analytics 4, and PostHog, connected per project. All reads are free.
Three integrations give IndexZero your measured data. Reading it is always free, and the agent tools that use it are documented under Search Console and Google Analytics and PostHog.
Google Search Console
Connect
Open Search Console in the project sidebar and choose Connect. Google asks for read-only Search Console access (webmasters.readonly), plus your basic profile so the connection can be labelled.
This is a separate consent from signing in with Google. Signing in never carries these scopes, and revoking the integration never signs you out.
Pick a property
The page lists the properties the Google account can see. Choose the one for this project's site. The connection is recorded only once a property is selected.
What you get: clicks, impressions, CTR, and average position by query, page, country, device, date, and search appearance, for web, image, video, news, and Discover; striking-distance queries (positions 5 to 20); and URL inspection for up to 10 URLs at a time. Data lags Google by about three days.
Google Analytics 4
The same flow, from Analytics in the project sidebar, asking for read-only Analytics access (analytics.readonly). Pick the GA4 property for the site.
What you get: landing pages, page performance, key events, traffic acquisition, ecommerce performance, site search, and audience breakdown, filtered to organic search or all channels; a measurement-health check; and the search-opportunities report that joins Search Console with Analytics to find pages that rank but do not convert.
How Google data is handled
IndexZero's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google data is never sold, never used for advertising, never sent to AI model providers for training, and only read by a person with your explicit consent or for security and legal reasons. Refresh tokens are encrypted at rest. Disconnecting from the integration page deletes the stored tokens; you can also revoke access at myaccount.google.com/permissions. The full statement is in the privacy policy.
PostHog
PostHog has no third-party OAuth for reading data, so the connection uses a personal API key.
Create a scoped personal API key
In PostHog, create a personal API key (it starts with phx_). Scope it to a single project with two permissions: query:read and project:read. The first runs the reports; the second lets IndexZero list your projects so you can pick one from a menu.
Do not paste a project API key (phc_). That is the write-only ingest token already in your website's JavaScript, and IndexZero rejects it up front rather than failing later.
Connect
At the bottom of the Analytics page, choose your region, PostHog Cloud US or EU, or enter a custom host for a self-hosted instance. Paste the key and pick the project.
The key is sent in the request body, never a query string, and is encrypted at rest. Disconnecting deletes it.
What you get: sessions, visitors, pageviews, bounce rate, and session duration with a daily trend; entry, top, and exit pages; traffic acquisition by channel, referrer, or UTM; events; conversions for an event you name; audience by device, country, browser, or OS; and the search-opportunities join against Search Console. Organic filtering uses PostHog's own "Organic Search" channel type.