How to white-label WordPress sites
You can white-label a WordPress site manually by replacing the front-end identity, restyling the login screen, adding admin CSS, and hiding unnecessary menus. For several client sites, a central branding plugin is faster and easier to maintain.
- 01Decide what to white-label
- 02Brand the public-facing site
- 03Customise the login screen
- 04Style and simplify the dashboard
- 05Keep custom code update-safe
- 06Use a central branding tool
What you need
- Administrator access to the WordPress site
- A logo, favicon, brand colours, and client support details
- A full backup or staging copy
- A MainWP dashboard and connected sites if using the bulk route
Decide what to white-label
List the areas clients will see: the public site, login screen, admin toolbar, dashboard, menus, footer text, update notices, and email messages. White-labeling the appearance is different from removing WordPress fingerprints from page source, URLs, HTTP headers, or plugin screens.
Do not hide menus as a substitute for permissions. A removed menu can still leave a user able to reach a screen directly, so use appropriate roles and capabilities as well.
Brand the public-facing site
For a classic theme, open Appearance and use the Customizer if it is available. Set the site title, tagline, logo, site icon, colours, and any supported header or footer options. WordPress stores the logo under Site Identity in the Customizer.
For a block theme, use Appearance > Editor. The Site Editor provides Identity settings for the site title, tagline, logo, and site icon, while Styles controls the wider colour and typography system. Add small visual adjustments through Additional CSS rather than editing the parent theme directly.
Customise the login screen
Replace the default login logo with your own artwork and change its destination and accessible text. A developer can add the logo styles and assets through the login_enqueue_scripts hook, change the logo link with login_headerurl, and change its descriptive text with login_headertext.
Keep the login branding readable and test it at /wp-login.php, after a failed login, after logging out, and in a private browser window. A common Friday problem is styling only the normal login view while the lost-password or recovery screens still show the default branding.
Style and simplify the dashboard
Add admin-only CSS for your colours, logo area, toolbar, dashboard welcome panel, and other client-facing elements. Load that CSS with admin_enqueue_scripts, and limit it to the screens that need it rather than loading one large stylesheet everywhere.
Remove menus that clients do not need with remove_menu_page() and remove_submenu_page() on the admin_menu hook. Keep access control separate: menu removal changes what is displayed, not what a user is authorised to access. Plugin and theme screens may still contain their own vendor branding.
Keep custom code update-safe
Put custom PHP in a small site-specific plugin or another location that is not overwritten by theme updates. If the changes belong to the theme, use a child theme instead of editing the parent theme. WordPress documents child themes as the safer place for modifications that must survive parent-theme updates.
Keep a record of every hidden menu, custom stylesheet, logo asset, and user role change. After updating WordPress, the theme, or a major plugin, check the login page, dashboard, editor, media library, forms, and client user accounts. CSS selectors and plugin screens can change without warning.
Use a central branding tool
For one site, the manual route is often fine and avoids adding another plugin. For an agency managing several sites, MainWP Branding is the faster route: it centralises logos, colours, custom CSS, hidden WordPress credits, and bulk branding changes from the MainWP dashboard.
Apply the branding to one staging or low-risk site first, then check the login screen, dashboard, user roles, plugin notices, mobile layout, and client workflows before applying the same settings across all managed sites.
Let MainWP Branding do it
Centralizes logos, colors, CSS, and hidden credits across managed sites; ideal for agencies needing consistent client-facing branding.
Sources
- developer.wordpress.org /reference/functions/remove_submenu_page/?utm_source=openai
- wordpress.org /documentation/article/customizer/?utm_source=openai
- developer.wordpress.org /reference/hooks/login_enqueue_scripts/?utm_source=openai
- developer.wordpress.org /reference/hooks/admin_enqueue_scripts/?utm_source=openai
- developer.wordpress.org /themes/advanced-topics/child-themes/?utm_source=openai
Questions
- Can WordPress be completely white-labeled without a plugin?
- No, not completely through normal WordPress settings. You can manually brand the public site, login screen, and parts of the dashboard with theme settings, CSS, and PHP hooks, but plugin screens, update notices, URLs, and some core interfaces may still expose WordPress or vendor branding. A plugin is mainly useful for consistency and repeatability across sites.
- Should I edit the WordPress core files to remove branding?
- No, do not edit WordPress core files. Core updates will overwrite those changes and can create maintenance or security problems. Use the Customizer or Site Editor for front-end changes, a child theme for theme-specific work, and a site-specific plugin for admin CSS and PHP customisations that should survive theme updates.
- Does hiding an admin menu stop a client accessing that feature?
- No, hiding a menu does not provide access control. WordPress documentation notes that a removed menu item may still be reachable directly, so assign an appropriate role or capability as well as hiding unnecessary navigation. Test with a real client-level account rather than testing only as an administrator.
- Why does my white-label login logo disappear after an update?
- The login logo can disappear when a theme, login plugin, cache, or CSS selector changes. Load login styles through WordPress’s login asset hook rather than editing the login page directly, clear browser and page caches, and test the normal login, logout, password reset, and recovery screens. The login page has its own asset-loading process separate from the main admin area.
- What is the quickest way to white-label several WordPress sites?
- Use a central branding tool connected to your managed sites. MainWP Branding is suited to this job because it brings logos, colours, custom CSS, hidden credits, and bulk branding changes into the MainWP dashboard. Still test one site first, because themes and plugins can introduce their own admin screens and branding.