Client portal done right: what clients actually want to see

The client portal trap

Every agency tool promises a client portal. Most portals are useless. Clients open them twice — once when you send the link, once when they get billed. Then never again.

After shipping portals for hundreds of agency workspaces, here''s what I''ve learned clients actually want.

The 3 things clients always want to see

1. The score (one number, at the top)

Not 47 KPIs. One number. Clients don''t want a dashboard, they want a verdict. "Your site scored 74 this month, up from 68. Here''s what moved it."

2. What shipped (specifically)

"Three fixes shipped this month. Here''s each one with a before/after." That''s the section clients read three times. If you don''t have this, your portal is a graph collection.

3. What''s next (tangible, not vague)

Not "we''ll keep optimizing SEO." Something like: "Next 30 days: rewrite pricing H1 (ETA week 2), add structured data to 5 collection pages (ETA week 3), launch blog post on X (ETA week 4)."

If those three sections are clear, you''ve built a portal that clients reference between your calls. That''s the renewal engine.

The 3 things clients don''t want (but every portal shows)

1. Keyword position charts with 500 rows

Clients can''t interpret keyword tables. They don''t know if position 11 for "men''s waterproof running shoes size 10.5 wide" matters. They trust you to know.

Show the top 10, in plain-language grouping ("Product-intent queries: 8 up, 2 down"). The details belong in YOUR workspace, not the client view.

2. Raw GA4 reports

GA4 is famously unreadable even for marketers. Embedding it in a client portal doesn''t make it readable. Extract the 3 numbers the client cares about (traffic, conversions, revenue) and present them as a human sentence: "Organic traffic up 12% this month. Trial signups from organic up 8%. Revenue tracking pending GA4 ecomm verification."

3. Competitor keyword gaps with 100 rows

Clients don''t need 100 keyword gaps. They need 3 themes: "Competitor X is ranking for waterproof gear content. Here''s what we''re shipping to match + exceed."

The portal structure that works

1. Hero: One score, big. Trend arrow vs last month.
2. Shipped this month: 3-5 items with before/after.
3. In progress: 2-3 items with expected ship date.
4. Next up: 3 items with brief rationale.
5. Relevant wins: 2-3 specific improvements (a query that jumped, a conversion that bumped).
6. Ask-me-anything: a direct reply-to email or booking link to you.

Notice what''s missing: data tables, chart galleries, KPI dumps, quarterly trend graphs. All of that is your workspace. The portal is the storytelling surface.

The download-PDF question

Clients still ask for PDFs. Your portal should have a "Download report" button that produces a PDF that looks exactly like the portal. Not a different template. Not a different data set. The same view, saved.

This is harder than it sounds — most tools have a pretty web view and an ugly PDF export that doesn''t match. Fixly''s client portals render the PDF from the same HTML the client sees, via headless Chromium, so they''re pixel-identical.

The one feature most portals get wrong

White-label without losing the audit-backed credibility.

If your portal is fully white-labeled (hide Fixly), your client doesn''t know what tool is powering it — which is the point. But if the tool ever goes down or has a bug, they blame YOU.

The right middle ground: white-label on by default, but keep a small "Powered by" footer that clients can discover if they want to verify the source of the data. This protects your agency brand without creating a black-box trust problem.

The client behavior to watch

If clients open the portal more than once a week, you''ve built something they trust. If they only open it when invoiced, you''ve built a bill.

Track the open count. It''s a retention indicator.

The actual move

Ship a portal that has: one score, three shipped items, three next items. That''s it. Iterate from there based on what clients actually ask for. Don''t try to build a dashboard — build a story.

See how Fixly renders client portals when you create one from an audit.