Your client logs into their WordPress admin and sees your agency’s brand — not a stack of third-party plugin logos, upsell banners, and vendor support links. That is the goal of white-labelling: making the tools disappear so the client experiences a coherent, agency-branded product. It is part craft, part business positioning (a white-labelled site justifies your retainer in a way a visibly-third-party-plugin site does not), and part legal nuance, because the GPL that governs WordPress plugins shapes what you can and cannot do. This covers all three.
It is the agency-delivery article of our developer’s guide, paired with multisite licensing.
The two layers of white-labelling
White-labelling happens at two distinct layers, and conflating them causes confusion. The first is wp-admin rebranding: the general WordPress admin experience — the login screen, the admin logo, the menu, the “Howdy” greeting, the footer “developed by” — which you control through admin-customisation plugins or theme/mu-plugin code, independent of any single plugin. The second is plugin-level white-labelling: hiding or rebranding a specific plugin’s own branding, menus, and upsells inside the admin. The first makes the whole admin yours; the second makes a particular plugin invisible or rebranded within it. A fully white-labelled client site usually needs both — a branded admin shell, plus the individual plugins set to not shout their own names.
wp-admin rebranding
The admin-shell layer is well-trodden. You can replace the login logo and link, swap the admin bar logo, customise the admin colour scheme to the client’s brand, change the footer text, and hide or rename menu items the client does not need. This is done with a dedicated white-label/admin-branding plugin (several exist) or with custom mu-plugin code hooking the relevant WordPress filters. The effect is that the client’s admin feels like a bespoke system rather than generic WordPress with plugins bolted on — which is exactly the perception an agency wants to create. This layer is plugin-agnostic; it brands the environment, not any one tool.
Plugin-level white-labelling as a feature
The second layer depends on the plugin offering it. A plugin built for agency use will include a white-label mode — settings to hide its own branding, suppress upsell notices, rebrand its admin menu, and present its features under a neutral or agency name. Not all plugins offer this, and where they do it is typically a higher-tier (Pro Plus or Agency) feature, because it is specifically an agency need. FotoGrids includes white-label capability in its Agency tier, letting you present the gallery features in the client’s admin without the FotoGrids branding fronting it. When choosing tools for agency delivery, plugin-level white-label support is a real selection criterion — a plugin without it cannot be fully hidden no matter how well you brand the admin shell around it.
Do this now. Audit a client site through the client’s eyes: log in as they would and note every third-party brand, upsell banner, and “developed by X” you see. That list is your white-labelling to-do. Handle the admin shell (login, logo, menus, footer) with an admin-branding approach, and for each plugin showing its own branding, check whether it offers a white-label mode — the ones that do can be hidden, the ones that do not are a flag for whether to keep them in your agency stack.
The GPL constraint
Here is the legal nuance that white-labelling guides often skip, and it matters. WordPress plugins are licensed under the GPL, which grants broad freedoms — you can modify, rebrand the user-facing experience, and use the code — but it also carries obligations, principally around redistribution: the GPL’s freedoms travel with the code, so you cannot, for example, strip a plugin’s licence or claim its code as exclusively your own proprietary work when redistributing it. White-labelling the experience for a client (rebranding what they see in their admin) is well within normal practice; what you cannot do is misrepresent authorship or violate the plugin’s specific licence terms when redistributing. The practical line: brand the client’s experience freely, but respect the plugin’s licence and do not claim to have authored code you did not. For anything beyond standard experience-rebranding — especially redistributing a modified plugin — check the specific plugin’s licence terms, as commercial plugins layer their own terms on top of the GPL.
Tip. “White-label” in marketing does not override a plugin’s licence. Rebranding what the client sees in their admin is fine; redistributing a commercial plugin as your own, or stripping its licence, is not — the GPL’s freedoms and the plugin’s own commercial terms both apply. When in doubt about redistribution specifically, read the plugin’s licence terms rather than assuming “white-label mode” grants more than it does.
What to white-label and what to leave
A judgment point: not everything should be hidden. Hide the vendor branding, the upsell banners, and the marketing notices — these clutter the client experience and serve the vendor, not the client. But think carefully before hiding support and update channels. If you white-label so thoroughly that the client cannot tell what is powering their site, you also cut off their (and a future developer’s) ability to get plugin support or understand the stack if you part ways. A common agency approach is to white-label the client-facing experience while keeping a private record of the real stack, and ensuring updates still flow (you do not want a white-labelled plugin silently going un-updated because its update channel was hidden). White-label the marketing noise; preserve the maintenance plumbing.
The agency hand-off
White-labelling is really about the hand-off: the client gets a branded, coherent site that feels like a bespoke product, while you retain the update path and the knowledge of what is underneath. Done well, it makes your agency the perceived author of a coherent system, which is good for retention and referrals, without pretending the underlying tools do not exist (which would break maintenance). The combination — branded experience for the client, intact plumbing for you, licence terms respected — is the professional standard. It is also why agency-tier plugin features (white-label mode, multisite licensing, a clean hook surface for customisation) exist: they are the toolkit for delivering many client sites that each feel bespoke without rebuilding the gallery layer each time.
Key takeaways
- White-labelling has two layers: rebrand the wp-admin shell, and hide/rebrand each plugin’s own branding.
- Plugin-level white-label is a feature (often Agency-tier) — a real selection criterion for agency stacks.
- The GPL lets you rebrand the experience but not misrepresent authorship or violate licence terms when redistributing.
- White-label the marketing noise, preserve the update/support plumbing — do not hide the site from its own maintenance.
What does white-labelling a WordPress plugin involve?
Two layers: rebranding the general wp-admin experience (login logo, admin bar, menus, footer) so the whole admin feels like your agency’s, and hiding or rebranding a specific plugin’s own branding, menus, and upsells. A fully white-labelled client site usually needs both — a branded admin shell plus individual plugins set not to display their own names.
Is white-labelling a GPL plugin legal?
Rebranding the client-facing experience is well within normal practice — the GPL grants broad freedom to modify and use the code. What you cannot do is misrepresent authorship or strip a plugin’s licence when redistributing, since GPL freedoms travel with the code and commercial plugins add their own terms. For redistribution specifically, read the plugin’s licence rather than assuming ‘white-label’ grants more than it does.
Should I hide everything when white-labelling a client site?
Hide the vendor branding, upsell banners, and marketing notices, but preserve the update and support plumbing. If you white-label so thoroughly that updates stop flowing or no one can get plugin support, you have created a maintenance problem. White-label the marketing noise while keeping a private record of the real stack and ensuring updates still reach the site.