Multi-client SEO reporting

Every client's organic performance, in one dashboard.

One dashboard per client, with organic metrics and keyword rank history in the same place — and CSV or PDF reports on demand. Live Search Console, GA4 and Semrush sync is the next build; this demo runs on a sample dataset.

No account needed — the sign-in page opens the demo dashboard in one click.

Organic traffic
12,460+4.2%
Avg. position
14.8+1.6
Top-3 keywords
24+9
CTR
3.7%−0.2

Sample figures from the demo dataset — not a connected account.

What it does

Unified organic metrics

Search Console, GA4 and Semrush share one normalized metric shape behind a single client switcher — traffic, clicks, impressions, CTR and average position for one client, in one place.

Keyword ranking trends

Time-series rank history for tracked keywords with the biggest movers, so you can see which rankings gained and which slipped over 7, 30 or 90 days.

CSV and PDF exports

The same numbers behind the dashboard, on demand. CSV is spreadsheet-safe (UTF-8 BOM, formula-injection guarded); the PDF embeds a Unicode font so non-Latin client names and keywords survive.

Isolation enforced in the database

Three roles, one tenant gate, and row-level security in Postgres deciding visibility — covered by integration tests that run against a live database, not a mock.

How it works

01

Every client is its own tenant

A client is a row with its own source set and role assignments. The app never asks 'is this account mine?' in application code — Postgres answers that.

02

A daily sweep, per client

A 2 AM cron enqueues one sync job for every active client, and a completed run revalidates the dashboard cache. Fetching live from the source APIs is the piece being built next.

03

Read it, then hand it over

Clients and staff sign in to current numbers and rank history, then export the same figures as CSV or PDF — built from the same code path, so the report can't disagree with the screen.

Built for agencies that report

Role-based access keeps each client seeing only their own numbers, enforced by row-level security in Postgres. Dashboards read from a cache rather than a vendor API, so page speed never depends on someone else's uptime.

Get started free