What is SEO analytics, and how do you build it in Metabase?
SEO analytics turns keyword positions, backlinks, authority scores, and search clicks into shared metrics about whether organic visibility is compounding — and what it's worth. In Metabase, build it by syncing dated snapshots from your SEO tools into a SQL database, modeling clean position, backlink, and SERP layers next to measured Search Console data, and shipping dashboards that put organic growth beside the revenue it drives.
TL;DR — Two kinds of numbers, kept apart: modeled vendor estimates (positions, volumes, authority) and measured Search Console clicks. Snapshot everything with dates — SEO APIs serve current state, so the warehouse only trends what you've stored. Fix the keyword set before trending anything.
What does SEO analytics measure?
- Is keyword visibility growing, and on which keyword groups?
- Is domain authority compounding faster than competitors'?
- Which pages and queries are winning or losing position?
- What share of the market's search demand do we capture?
- Are backlinks accumulating — and staying?
- What does each position bucket earn in clicks, and is that changing?
- Is technical health improving crawl to crawl?
Which tools feed SEO analytics?
| Tool | Best for | Getting data into Metabase |
|---|---|---|
| Ahrefs | Domain Rating and referring-domain trends; Keyword position distribution over time | Ahrefs API v3, pipeline, or Ahrefs MCP server for exploration |
| Semrush | Organic keywords and estimated traffic trend; Position-tracking visibility by campaign | Semrush API, pipeline, or Semrush MCP server for exploration |
| Similarweb | Market traffic share vs. named competitors; Visits and engagement benchmarks by month | Similarweb Web Traffic & Batch APIs, pipeline, or Similarweb MCP server for exploration |
| SE Ranking | Daily rank tracking by project and search engine; Keywords in top 3 / top 10 over time | SE Ranking API, pipeline, or SE Ranking MCP server for exploration |
| DataForSEO | Rank tracking from raw SERP snapshots; SERP-feature presence by keyword set | DataForSEO API v3, pipeline, or DataForSEO MCP server for exploration |
| Google Search Console | Measured clicks, impressions, CTR, position | BigQuery bulk export, connector, or API |
| Google Analytics 4 | Sessions and conversions after the click | Native BigQuery export or connector |
What shared data models should you build?
Build clean models on top of raw snapshot tables so each dashboard uses the same definitions.
seo_keyword_positions— one row per keyword per domain per snapshot date, with position, search volume, and URLkeyword_metrics— one row per keyword, with volume, difficulty, and the keyword group it belongs toauthority_daily— one row per domain per day, with the vendor's authority score, referring domains, and backlinksbacklink_changes— one row per gained or lost referring domain per dayserp_snapshots— one row per keyword per result per crawl, with domain and SERP-feature typeaudit_snapshots— one row per site audit run, with health score and issue countsgsc_performance_daily— measured clicks, impressions, CTR, and position by query and pagekeyword_groups— the reference table that fixes keyword sets, brands, and topics for every trend card
Which SEO metrics matter most?
- Keywords in top 10 — the visibility count that survives averaging.
- Average position — volume-weighted, over a fixed keyword set.
- Domain rating — the off-page trend, within one vendor's scale.
- Referring domains — unique linking domains at each snapshot.
- Backlink velocity — net new referring domains per week.
- Share of voice — your weighted slice of tracked-keyword visibility.
- Organic CTR — what each position bucket earns, from measured GSC data.
- Organic clicks & impressions — the measured outcome everything above should explain.
How do you connect tools to Metabase?
- MCP + CLI — use MCP for a scoped, summarized live export, then
mb upload csvfor quick analysis. - Warehouse-backed pipeline — schedule scripts against each tool's API (managed connectors are rare here) and land dated snapshots.
- Modeled layer — map each source into shared position, backlink, and SERP models, keeping vendor-specific extension tables separate.
Which dashboards should you build first?
- Organic visibility overview — position buckets, weighted position, estimated traffic.
- Keyword rank tracking — daily positions, movers, striking distance.
- Backlink growth— referring domains, velocity, authority.
- Competitor share of voice — weighted visibility share across rivals.
- Technical SEO health — audit scores and issue trends.
- Organic search performance — the measured GSC side of the same story.
Common mistakes
Trending metrics over a changing keyword set.→ Every average and count moves when the set grows. Fix the tracked set in a reference table, version it, and stamp trend cards with the version.
Presenting modeled estimates as measurements.→ Vendor volumes and traffic estimates are models. Keep them in separate columns from Search Console data and label both on every card.
Waiting to sync until someone asks for the trend.→ SEO APIs serve snapshots, not history. Schedule daily position pulls and weekly backlink pulls from the day tracking starts.
Reporting authority scores without outcomes.→ DR going up while clicks stay flat is a vanity trend. Pair every authority card with measured clicks or conversions from the same period.
Ignoring SERP-layout effects on CTR.→ Features and AI Overviews depress CTR at stable positions. Track organic CTR by position bucket so layout changes don't read as ranking losses.
Related
Integrations
Analytics
Terms
FAQ
What is SEO analytics?
SEO analytics is the practice of turning search-visibility signals — tracked keyword positions, backlink growth, authority scores, SERP features, and measured clicks — into governed, shareable metrics. Where SEO tool UIs answer "how does this keyword rank today?", SEO analytics answers "is visibility compounding, is authority growing faster than competitors', and what is that worth in traffic?" In Metabase, you build it by syncing dated snapshots from tools like Ahrefs, Semrush, and SE Ranking into a SQL warehouse next to Search Console data.
What is the difference between SEO analytics and my SEO tool's reports?
Three things: history, joins, and governance. Tool reports show current state plus whatever history the vendor keeps, inside one tool's numbers. A warehouse keeps every snapshot forever, joins vendor data to measured Search Console clicks and to revenue, and puts one agreed definition of each metric in front of everyone — instead of five tools disagreeing in five tabs.
Which metrics should an SEO dashboard track?
Start with visibility: keywords in top 10 and volume-weighted average position over a fixed keyword set. Add authority — domain rating, referring domains, and backlink velocity — then share of voice for the competitive view, and organic CTR plus organic clicks and impressions for measured outcomes.
Which tools feed SEO analytics in Metabase?
Five vendor guides in this cluster: Ahrefs (backlinks and authority), Semrush (visibility and position tracking), Similarweb (market traffic estimates), SE Ranking (rank tracking and audits), and DataForSEO (raw SERP data at scale) — plus the measured pair, Google Search Console and GA4. See the SEO integrations overview for connection routes.
Do I need all five SEO tools?
No. One suite (Ahrefs, Semrush, or SE Ranking) plus Search Console covers visibility, authority, and measured performance. Add Similarweb when leadership asks market-share questions, and DataForSEO when tracked-keyword counts grow into the thousands and per-query pricing beats subscription tiers. The shared model means dashboards survive tool switches.
How do I connect SEO data to revenue?
Through the URL and the funnel. Search Console clicks land on pages; analytics tools record what sessions on those pages convert; your database records what conversions are worth. Join on normalized URL and UTM data, and the dashboard chain becomes: visibility (vendor data) → clicks (GSC) → conversions (GA4 or Plausible) → revenue (your own tables). Each hop is a join you own, with an attribution caveat you state once.
Can I build SEO dashboards without a data warehouse?
For a first pass, yes: pull a summarized export through a tool's MCP server and load it with the Metabase CLI (
mb upload csv) — each upload becomes a queryable table and model. That works for audits and spot-checks. Trends need scheduled snapshots in a database: rankings change daily and vendor APIs serve current state, so history only exists if you store it. Every integration guide documents both routes.How does SEO analytics relate to marketing analytics?
SEO analytics is the organic half of the acquisition story. Marketing analytics covers paid channels, attribution, and funnel economics; SEO analytics covers the visibility engine that fills the organic side of the paid vs. organic mix. They share the warehouse, the URL join keys, and the conversion tables — build them together.