If you're the developer at an agency, white-label software eventually lands on your desk. Someone in sales promised clients "our own platform," and now you have to make a vendor's product look like yours without leaking anything.
SEO software is a good case study because the market is crowded and "white label" means wildly different things depending on the vendor.
Three levels of rebranding
Level What's rebranded What becomes your problem
- Branded reports Logo, colors, maybe sender email on PDFs/dashboards Very little
- Branded client portal Live data behind a login on your domain Auth, permissions, email deliverability, DNS
- Full platform resale The whole product on your domain Support, roles, data isolation, uptime expectations
Most vendors document at least Level 1. Fewer do Level 2 cleanly. Level 3 changes your business model: you're selling software access, not just reports.
Where the vendor's brand leaks
Before signing, walk through every surface a client can touch and check whose brand appears:
Login page
Browser tab title and favicon
URL (custom domain or subdomain via CNAME?)
TLS certificate (issued for your domain, or a vendor wildcard?)
Transactional emails: sender address, reply-to, footer, unsubscribe link
Password reset flow
PDF metadata and embedded fonts
Shared dashboard links
Error pages and 404s
Help/support links inside the UI
Several vendors gate custom domains to higher plans. Never assume the entry tier includes them.
The "promise test"
Tag every feature on the vendor's list as client-visible, operator-visible, or both.
Operator-only features (bulk editing, internal dashboards, admin settings) might make your team faster, but they don't change what the client sees. If the sales promise was "clients get their own branded platform," only client-visible features count toward it.
Test tenant isolation yourself
Don't take "client access controls" on faith. In a trial:
Create two client workspaces, A and B, with distinguishable test data.
Invite a client-view user to A only.
Log in as that user and try to reach B's data: navigation, search, direct URL manipulation (swap IDs in the path or query string), shared report links, exports.
Check whether a shared dashboard link for A is guessable or enumerable.
Revoke the user and confirm sessions and shared links stop working.
If step 3 finds anything, stop the evaluation.
Model cost by billing unit, not headline price
Vendors bill on different units, which makes list prices misleading:
true_cost_per_client =
(base_subscription + add_ons + seats + reports + usage + setup_and_ops_time)
÷ active_client_sites
Using list prices checked in October 2026:
Billing model Example 5 clients 10 clients 20 clients
Per client AgencyAnalytics at $20/client/mo (annual) $100 $200 $400
Per report add-on Semrush Pro Reports at $20/report/mo, plus subscription $100 + sub $200 + sub $400 + sub
Platform add-on SE Ranking Agency Pack from $69/mo (annual), plus base plan flat, but base-plan limits may force an upgrade
Base + usage WebCEO: base fee + domain fee + project and scan charges varies with usage
That's list-price arithmetic, not a quote. Run it at your next year's client count, not today's.
Exit plan
The part everyone skips. Before signing, confirm:
Can you export raw data (not just PDFs) in a usable format?
Is there an API, and is it on your plan?
What happens to client-facing URLs if you cancel? Do you control the DNS record?
How long is data retained after cancellation?
Owning the domain and the CNAME means you can point it somewhere else later. That's leverage.
Reporting vs execution
One last distinction. Reporting and portal products brand the work; they don't produce it. If the agency's real bottleneck is research, content, and publishing, that's a separate tool, and the client-facing layer sits on top of it.
The full comparison of 10 platforms (white-label level, billing unit, and honest limitations for each) is here: https://keytomic.com/blog/best-white-label-seo-software-for-agencies
Top comments (0)