Step one
Connect
A Google OAuth flow connects Search Console and GA4. The connect flow is live and verified end to end against real accounts.
Analytics
A reusable deep-analysis framework for search and engagement data, built on the premise that there is far more in this data than anybody actually extracts from it.
Live
Clients only
Search Console and GA4
What It Is
Analytics is a full standalone application with its own auth and its own backend. It connects to Google Search Console and GA4 and runs a repeatable analysis framework across whatever it finds there: multiple visualizations, drill-downs, and funnel breakdowns that go from a site-level movement down to the query, the page and the step where it happened.
Where a Search Console BigQuery bulk export exists, it prefers that feed over the Search Console API, because the export is the full data rather than the sampled and capped version the API hands back.
It is built to account for a lot of different data situations, because every client arrives with a different setup: different property structures, different GA4 configurations, different amounts of history. That is the design principle rather than an implementation detail, and it is most of the work.
The Problem It Solves
The premise is simple. There is far more insight sitting in SEO and engagement performance data than anyone actually extracts from it, and the reason is that extracting it is slow and gets rebuilt from scratch every time.
Standard dashboards answer what happened. Sessions fell, clicks rose, this page lost positions. That is the easy half. The half that matters is what it means and what should change, and that answer needs a repeatable analysis, not another chart.
Every consultant rebuilds that analysis per client, in a spreadsheet, and throws it away at the end of the engagement. This is that analysis, built once, aimed at whatever data it is pointed at.
Where It Gets Used
It carries the analysis layer of an engagement from the first week onward.
- Onboarding. Running the same deep-dive framework against a new client's Search Console and GA4 data on day one, instead of building bespoke analysis before I know anything.
- Drilling down. Going from a site-level trend into the query, the page and the funnel step that actually moved it.
- Working from full data. Reading a BigQuery bulk export rather than the API's sampled, capped rows, wherever the client has that export switched on.
- Feeding a deliverable. Producing the analysis layer that sits underneath an audit or an ongoing engagement, so the findings arrive with their evidence attached.
How It Works
Connect, ingest, analyze, explore. The value is in the third step.
Step two
Ingest
Where the Search Console BigQuery bulk export is available it reads that, because it is complete. Where it is not, it falls back to the Search Console API and works within its limits.
Step three
Analyze
The same framework runs against every property. Being repeatable is the whole point: the analysis is comparable between clients and between quarters because it was not improvised for either.
Step four
Explore
Visualizations, drill-downs and funnel breakdowns sit on top of the analysis, so a number in a summary can be opened until it names a query and a page.
One thing to expect during the connect flow: the Google OAuth consent screen is published but unverified. That is a deliberate trade. It caps the app at one hundred users and shows an unverified-app warning during connect, in exchange for refresh tokens that do not expire every week. If you are connecting an account, expect that screen and continue past it.
Who It Is For
Me and my clients. Scope is well under one hundred users by design, and there is no public signup.
If you are reading this as a prospect, read it as evidence of how far the analysis goes rather than as something to buy. The output shows up inside an engagement, and the deliverables it feeds are specified separately.
- Not a public product. Accounts are provisioned by me, and the app is capped at one hundred users by the OAuth configuration.
- Search Console and GA4 only. Those are the native integrations today. Data living anywhere else is not read yet.
Status And Access
Live and in use, but not something you can sign up for.
Status and access
- Status
- Live since September 2026, deployed and verified end to end
- Address
- analytics.jakelabate.com
- Sign-in
- Accounts are provisioned by me. There is no public signup.
- Connect flow
- Google OAuth against Search Console and GA4, working against real bulk export data.
- Scale
- Jake plus clients, capped at one hundred users.
- Can you use it today
- Only as a client. The page is here so you can see what it does.
The Stack
The same shape as AuditBuilder, sharing its auth and its Supabase project.
Stack
- Front end
- React, Vite and TypeScript.
- Hosting
- Cloudflare Workers, on a custom domain.
- Backend
- Supabase, in its own Postgres schema inside the project AuditBuilder uses.
- Auth
- Shared auth schema across both apps, plus a Google OAuth connect flow for data access.
- Data sources
- Google Search Console, preferring the BigQuery bulk export, and GA4.
- Repository
- JakeLabate/analytics, private.