White label
Putting your agency's brand on RankX AI. Custom domain, logo, colours and sending address, and the one place the platform domain still shows.
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, and there is one place it does not yet reach, which is stated below rather than left for a client to find.
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.
The one place the platform domain still shows
The link inside an emailed client report currently uses the platform domain rather than your custom hostname. That report is often the one page a client's stakeholder opens cold, so it is the most visible place for it to happen, and it is a known open issue rather than a design decision.
Two things follow, and both are practical:
Do not promise a client a fully white-labelled report link. Promise the report, which is genuinely yours: the branding, the narrative, the metrics and the sending address all carry your identity.
Send clients to the portal on your own domain for anything you want fully branded. The portal honours the custom hostname.
Do not hand a client an MCP credential
Related, and it is the same class of leak.
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 white label does not change
The measurement. Nothing about the numbers differs, and a client's data is exactly the data you see.
Your team's experience. White label is client-facing. Your own workspace is not rebranded, and it should not be.
The docs. These pages are RankX AI's, on RankX AI's domain. If you need 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.
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.