White label
Putting your agency's brand on RankX AI. Custom domain, logo, colours and sending address, and how emailed report links follow your own domain.
White label puts your agency's brand on what your clients see: a custom domain, your logo and favicon, your colours, and email sent from your own address with per-client template overrides.
It covers the client-facing surfaces, from the client portal to the link inside an emailed client report.
What you can brand
| Surface | What you control |
|---|---|
| Domain | A custom hostname for the client-facing experience |
| Logo and favicon | Yours, on the portal and in reports |
| Colours | Your palette |
| Email sending | Your own sending address |
| Email templates | Per-client overrides on top of your agency defaults |
White label is an agency-track feature, and the custom domain is on every agency plan: Agency Starter, Agency Pro and Agency Scale all carry it. No direct plan does, which is a track decision rather than a tier one, because white label exists only if you have clients to show it to. See plans and limits.
Where white label lives
Under Agency Admin, not under Settings. That is deliberate: white label and the client dimension both exist only if you run clients, so neither appears in the settings shell at all, which keeps a Direct account from being shown a section that would ask a question it has no answer to.
Report links follow your custom domain
The link inside an emailed client report uses your custom hostname once that hostname is verified, white label is switched on and its certificate is active. Until all three are true, the link uses the platform domain, which opens the same branded report, so a client never receives a link that does not work.
Two things follow, and both are practical:
Finish the custom domain before the first scheduled report. A client report is often the one page a client's stakeholder opens cold, so it is worth having the hostname verified and its certificate active before that report goes out. The branding, the narrative, the metrics and the sending address carry your identity either way.
Send clients to the portal on your own domain for everything else. The portal honours the custom hostname.
Do not hand a client an MCP credential
It is the same principle applied to assistants.
A client-scoped MCP token is an agency-side credential. The endpoint host, the server name and the Agent Skills all identify RankX AI, so giving one to a white-label end client shows them the platform you have white-labelled.
Client-scoped tokens exist so that your own tooling can be limited to one client's data, not so a client can connect their own assistant. See MCP authentication.
Your own sending address means client reports and notifications arrive from you rather than from RankX AI, which is usually the highest-value part of white label because it is the surface a client sees most often.
Setting it up needs domain authentication, which is a DNS change on your side. See email sending.
Per-client template overrides sit on top of your agency defaults, so a client with particular requirements can have its own wording without forking every template.
What stays the same under white label
The measurement. The numbers are identical, and a client's data is exactly the data you see.
Your team's experience. White label is client-facing, so your own workspace keeps the standard interface.
The docs. These pages are RankX AI's, on RankX AI's domain. For client-facing help material under your own brand, write it against these rather than linking clients here.
Where to go next
- The client portal, the main branded surface.
- Client reports, the second.
- Email sending, for the sending address.
Last updated
Per-client credit budgets
A ceiling on the shared agency wallet, not a sub-wallet. Why the wallet can be full while a client is stopped, and what uncapped and zero each mean.
Client reports
Scheduled monthly reports with a written narrative, delivered by email with a share link. What the narrative costs, and why it degrades rather than blocking.