How to build Google Search Console dashboards in Metabase

Google Search Console is Google's search performance tool, reporting organic clicks, impressions, CTR, and position by query and page. Metabase is where you turn that marketing data into shared, trustworthy dashboards. This guide covers two complementary paths: a lightweight MCP + CLI route that pulls live data with the Search Console MCP (hosted) and loads a CSV into Metabase with the Metabase CLI, and a durable pipeline route that syncs Google Search Console daily stats into a database so you can build dashboards anyone can read.

How do you connect Google Search Console to Metabase?

Most teams combine both routes: use MCP and CLI uploads for a fast first pass, then move recurring marketing reporting to a warehouse-backed model.

What can you analyze from Google Search Console data in Metabase?

• Organic clicks and impressions trend — built from search performance rows and the related queries, pages, countries and devices data your sync exposes.
• Top queries by clicks and position — built from search performance rows and the related queries, pages, countries and devices data your sync exposes.
• Landing pages gaining or losing clicks — built from search performance rows and the related queries, pages, countries and devices data your sync exposes.
• Branded vs. non-branded query mix — built from search performance rows and the related queries, pages, countries and devices data your sync exposes.
• CTR by position bucket — built from search performance rows and the related queries, pages, countries and devices data your sync exposes.

Which Google Search Console dashboards should you build in Metabase?

How do you use the Search Console MCP (hosted) with the Metabase CLI?

Pair the Search Console MCP (hosted) with the Metabase CLI for fast, hands-on analysis. MCP is useful for scoped lookups and summarized exports; the Metabase CLI's upload command loads CSV data into Metabase and creates a ready-to-query table and model.

Example workflow

• Ask the MCP server for a daily summary of search performance rows for the last 90 days.
• Export the result as CSV, keeping stable IDs, channels, campaigns, and dates.
• Run mb upload csv to load it into Metabase as a table and model, then build questions and dashboards on top.

Be honest about the limits

• MCP lookups are excellent for exploration, not scheduled reporting.
• A CSV upload is a snapshot; refresh it with mb upload replace or move to the pipeline for real history.
• Daily rollups by channel and page are required for traffic and conversion trends.
• mb upload csv needs an uploads database configured under Admin → Settings → Uploads.

How do you set up Google Search Console MCP and the Metabase CLI?

{
  "mcpServers": {
    "search-console": {
      "url": "https://mcpsearchconsole.com/mcp"
    }
  }
}

Google publishes no official Search Console MCP as of mid-2026; this hosted third-party connector requests only the read-only scope. Self-hosted open-source alternatives (for example AminForou/mcp-gsc) run locally against your own service-account credentials.

# Install the Metabase CLI
npm install -g @metabase/cli

# Log in (opens your browser; requires Metabase v62+)
mb auth login --url https://your-metabase.example.com

# Load a search-performance-rows export — creates a table AND a model
mb upload csv --file google-search-console-search-performance-rows.csv --collection root

# Refresh that same table later from a new export
mb upload replace <table-id> --file google-search-console-search-performance-rows.csv

Can you generate a Google Search Console dashboard with AI?

Yes. Use the prompt below with any assistant that can run the Search Console MCP (hosted) and the Metabase CLI. It works end to end: if Google Search Console tables already exist in Metabase it analyzes those; otherwise it pulls scoped, summarized data over MCP, loads it with mb upload csv, then builds the dashboard and caveats any metric that needs missing history.

Create a polished Metabase dashboard for Google Search Console web analytics analytics.
Work end to end: get the data into Metabase if it isn't there yet, then build.

Goal: Help marketing and growth leaders understand traffic by channel, landing-page conversion, organic search performance, and the paid vs. organic mix from Google Search Console data.

Step 1 — Find or load the data:
- First, check what already exists in Metabase (search for google-search-console tables and
  models). If durable Google Search Console data is already present — synced from a warehouse
  or uploaded earlier — use it and skip to Step 2.
- If nothing is there, pull a scoped, summarized export with the Search Console MCP (hosted):
  search performance rows, plus queries, pages, countries and devices.
  Prefer daily aggregates over raw events. Write each result to a CSV,
  then load it with the Metabase CLI — run "mb upload csv --file <export>.csv" so
  each upload creates a table and a ready-to-query model. Use "mb upload replace
  <table-id> --file <export>.csv" to refresh an existing table instead of creating
  duplicates.

Step 2 — Inspect before querying:
Do not assume exact table or column names. Inspect available fields, channels,
campaigns, dates, and whether daily history exists before creating trend or
pacing cards.

Important:
- Build on whatever data is present; don't claim Metabase connects natively to
  Google Search Console — it reads a database or CLI-uploaded tables.
- Never try to load raw event or click streams into Metabase; use daily
  aggregates, campaign-grain stats, and entity tables.
- Only compute rates (CTR, conversion rate, ROAS, CAC) when both numerator and
  denominator exist — and state the attribution model when reporting conversions.
- Exclude test campaigns and internal traffic from headline cards, and keep
  currency consistent when spend spans accounts.
- A single CSV is a point-in-time snapshot: only build trend cards if there is a
  usable date column or multiple periods have been uploaded.

Dashboard title: Google Search Console Web Analytics Overview

Sections:
1. Executive summary: Sessions last 30 days; Conversion rate; Key events;
   Organic clicks; Paid vs. organic share.
2. Traffic: Sessions by channel by week; top landing pages; engagement rate.
3. Conversion: Conversion rate by channel; landing-page conversion table.
4. Organic: Clicks and impressions by week; top queries; branded vs. non-branded.
5. Mix: Paid vs. organic sessions and conversions over time.

Filters: Date range, Channel, Campaign, Country, Device, Segment.

Output: Build the dashboard if you have permission; otherwise provide the exact
questions, SQL, model definitions, and layout. Include caveats for any metric
that cannot be calculated from the available data.

How do you sync Google Search Console data into a database or warehouse?

For dashboards that need history and reliability, land Google Search Console daily stats and entities in a database first, then connect Metabase to that database.

Connector options

• Managed ETL — use a connector when one covers the objects you need.
• Custom pipeline — use the Search Console API for control over grain, fields, and refresh cadence.
• MCP + CSV — use this for quick exploration and one-off slices.

Sync query and page performance with the Airbyte Google Search Console source or Fivetran's connector, or use Search Console's native bulk export to BigQuery — and start early, because the API only serves a rolling 16-month window.

Notes

• Decide the rollup grain first (daily per campaign/channel is the workhorse) — it drives warehouse cost and every trend card.
• Land raw entity tables first, then build clean Metabase models on top.
• Normalize channel, source, medium, campaign, landing-page, date, sessions, and conversions fields.

How should you model Google Search Console data in Metabase?

Core tables

Modeling advice

• Build a clean traffic_rollups model with common columns across tools, so multi-channel dashboards don't fork definitions.
• Separate entity tables (campaigns, audiences, pages) from daily time-series rollups.
• Exclude test campaigns and internal traffic from headline metrics; keep channel and campaign as explicit columns.
• Use stable IDs for campaign, channel, and user joins; display names change.

Which Google Search Console metrics should you track in Metabase?

What SQL powers Google Search Console dashboards in Metabase?

These assume a cleaned analytical model in a warehouse (PostgreSQL dialect). Adjust table and column names to match your pipeline.

SELECT
  channel_group,
  date_trunc('week', session_date) AS week,
  SUM(sessions) AS sessions,
  SUM(key_events) AS conversions,
  ROUND(100.0 * SUM(key_events) / NULLIF(SUM(sessions), 0), 2)
    AS conversion_rate_pct
FROM traffic_rollups
GROUP BY 1, 2
ORDER BY 2, sessions DESC;

SELECT
  landing_page,
  SUM(sessions) AS sessions,
  SUM(key_events) AS conversions,
  ROUND(100.0 * SUM(key_events) / NULLIF(SUM(sessions), 0), 2)
    AS conversion_rate_pct
FROM traffic_rollups
WHERE session_date >= CURRENT_DATE - INTERVAL '30 days'
GROUP BY landing_page
HAVING SUM(sessions) >= 100
ORDER BY conversions DESC
LIMIT 20;

SELECT
  date_trunc('week', stat_date) AS week,
  SUM(clicks) AS clicks,
  SUM(impressions) AS impressions,
  ROUND(100.0 * SUM(clicks) / NULLIF(SUM(impressions), 0), 2) AS ctr_pct,
  ROUND(AVG(position), 1) AS avg_position
FROM gsc_performance_daily
GROUP BY 1
ORDER BY 1;

What are common mistakes when analyzing Google Search Console in Metabase?

Related

Related analytics

Related dashboards

Related integrations

FAQ