Google Search Console logo

SEO integration

Google Search Console reporting & dashboards

Turn Search Console data into governed SEO reporting you can trust and combine.

What you can do with Search Console in Maven

Maven connects Google Search Console and models organic search into governed SEO metrics. Track clicks, impressions, CTR, and average position by query, page, device, and country, watch ranking movement over time, and report organic search beside paid and the rest of your acquisition mix.

What you can measure

32 Google Search Console metrics you can use consistently

Maven keeps Search Console numbers consistent across dashboards, reports, and answers so the team is not debating which spreadsheet is right.

Organic Avg Position

Impression-weighted average organic ranking position at query grain (lower is better)

Organic Clicks

Search Console organic clicks at query grain

Country Avg Position

Impression-weighted average organic position by country (lower is better)

Country Organic Clicks

Organic clicks split by country

Country Organic CTR

Organic click-through rate by country

Country Organic Impressions

Organic impressions split by country

Search CTR

Organic click-through rate for the selected search_scope (query by default)

Device Avg Position

Impression-weighted average organic position by device (lower is better)

Device Organic Clicks

Organic clicks split by device

Show all 32 metrics

Device Organic CTR

Organic click-through rate by device

Device Organic Impressions

Organic impressions split by device

Organic Impressions

Search Console organic impressions at query grain

Bing Inbound Link Count

Bing's latest inbound-link count snapshot at landing-page grain; null for Google Search Console rows.

Page Avg Position

Impression-weighted average organic ranking position at page grain (lower is better)

Page Organic Clicks

Search Console organic clicks at landing-page grain

Page Organic CTR

Organic click-through rate at page grain

Page Organic Impressions

Search Console organic impressions at landing-page grain

Organic CTR

Organic click-through rate at query grain

Query-Page Avg Position

Impression-weighted average organic ranking position at exact query-to-page grain (lower is better)

Query-Page Organic Clicks

Search Console organic clicks at exact query-to-page grain

Query-Page Organic CTR

Organic click-through rate at exact query-to-page grain

Query-Page Organic Impressions

Search Console organic impressions at exact query-to-page grain

Ranking Pages

Distinct pages ranking across the selected query scope, merged from re-aggregatable sketches

Ranking Queries

Distinct queries a page ranks for

Avg Anonymized Click Share

Mean share of page-hour clicks whose query Google withheld

Avg Match Probability

Mean posterior probability across matched organic sessions

Organic Conversion Value

Conversion value recorded on organic sessions

Organic Conversions

Conversions recorded on organic sessions

Converting Organic Sessions

Organic sessions that produced at least one conversion

Query Match Rate

Share of organic sessions that could be matched to a search query

Matched Sessions

Organic sessions assigned a search query at any confidence tier

Organic Sessions

Google-organic sessions considered for query matching

Report templates

Search Console reports for the next client review

Use Search Console reporting templates to see what needs attention, what can be trusted, and which optional fields need cleanup before the next review.

Maven report template

Search Migration Recovery

Track the MavenData-to-MetricMaven transfer by hostname, exact query-to-page overlap, organic sessions, conversions, and migration-control evidence.

Domain migrationGSC + GA4Exact overlap

GSC is required. GA4 hostname sessions and conversions appear when the refreshed landing-page hostname report is available. URL Inspection, indexed counts, Google-selected canonicals, and crawl failures remain separately sourced operating evidence.

Connection and sync

What Maven pulls from Search Console

You connect Google Search Console by signing in to it and approving access, so nobody shares a password. The first Google Search Console sync pulls the most recent 30 days so the workspace fills quickly. A follow-up backfill then adds older history, up to 480 days in total. After that, each scheduled sync re-reads the last 3 days, so late changes are picked up.

Gsc query performance

Search query metrics — daily history plus unified rolling hourly rows.

Fields: hour, hour label, query, clicks, impressions, CTR, position, data grain, data state, source timezone

Gsc page performance

Page-level search metrics — daily history plus unified rolling hourly rows.

Fields: hour, hour label, page, clicks, impressions, CTR, position, data grain, data state, source timezone

Gsc country performance

Search performance by country — daily history plus unified rolling hourly rows.

Fields: hour, hour label, country, clicks, impressions, CTR, position, data grain, data state, source timezone

Gsc device performance

Search performance by device type — daily history plus unified rolling hourly rows.

Fields: hour, hour label, device, clicks, impressions, CTR, position, data grain, data state, source timezone

Gsc query page performance

Query-to-page mapping with metrics — daily history plus unified rolling hourly rows.

Fields: hour, hour label, query, page, clicks, impressions, CTR, position, data grain, data state, and 1 more

Gsc hourly page performance

Hourly page-level search metrics over GSC's rolling ~10-day hourly window (hour is Pacific Time; date is the PT calendar date derived from it).

Fields: hour, page, clicks, impressions, CTR, position

Gsc hourly query page performance

Hourly query-to-page search metrics split by device and country over GSC's rolling ~10-day hourly window (device/country are null when the API rejects the five-dimension combination and the extractor falls back to query+page).

Fields: hour, query, page, device, country, clicks, impressions, CTR, position

How it works

Connect Google Search Console to a client’s workspace

No SQL or warehouse setup. Connect the source, then build the client’s report by asking Claude or ChatGPT.

Step 1

Connect Google Search Console

In the client’s workspace, open Sources, add Google Search Console and choose the account to sync. If you don’t have access to the account, send the client a connect link where the platform supports one.

Step 2

Maven syncs and models the data

Maven pulls the client’s Google Search Console data (7 objects) and models it into documented tables. No SQL, warehouse or pipeline setup.

Step 3

Report, ask and automate

Build the client’s report or deck by asking Claude or ChatGPT through the MCP, set alerts on what matters, and publish to the client’s portal once you approve it.

Works well with

Report Search Console alongside the rest of your stack

FAQ

Google Search Console reporting questions

What Google Search Console metrics can I report on in Maven?

Maven exposes 32 governed Google Search Console metrics, including Organic Avg Position, Organic Clicks, Country Avg Position, Country Organic Clicks, Country Organic CTR and Country Organic Impressions — each defined once so it means the same thing in every report.

What can I break Google Search Console performance down by?

You can break Google Search Console metrics down by Search Scope, Search query, Query intent, Ranking position, Is Cannibalized, Word Count, Query type and Page, and more.

Can I combine Google Search Console with other data sources?

Yes. Google Search Console sits in the same client workspace as sources like Google Analytics 4, Google Ads and Shopify, so one report or question can use them together.

How often does Google Search Console data sync to Maven?

Maven syncs Google Search Console automatically: a fast first source pull after connecting, then scheduled refreshes that keep reports current. The last successful sync time is always visible, so you know the source data is fresh before it feeds a trusted reporting workflow.

Can Maven report SEO and paid search together?

Yes. Search Console organic metrics live in the same governed layer as Google Ads, so you can report organic and paid search side by side and see total search visibility.

Is my Google Search Console data secure with Maven?

Yes. Maven connects to Google Search Console over its official OAuth flow — no password sharing — stores access tokens encrypted, and pulls read-only reporting data into a governed warehouse you control.

Start your 14-day trial

Set up your first client, build their report by asking Claude or ChatGPT, and publish it to their portal.

  • Free for 14 days, no credit card
  • Your first client workspace and portal
  • Every report template, ready to clone
Start a 14-day trial

Nothing is charged unless you subscribe.

Prefer a walkthrough? Book a demo on one of your own clients.