Can white label SEO tools use a custom domain?

Yes. A white label SEO platform can use your own custom domain when it supports domain mapping. This allows clients to access branded dashboards, reports, login pages and other platform areas through a domain or subdomain that you control, rather than the underlying provider’s web address.

The usual arrangement is to create a dedicated subdomain, such as portal.yourcompany.co.uk, reports.yourcompany.co.uk or seo.yourcompany.co.uk. You then point that subdomain to the platform using a DNS record, commonly a CNAME record. Some platforms can also map an entire domain, although a subdomain is often easier to manage because it keeps your main website and its DNS configuration separate.

Custom domain support is a platform feature rather than an automatic part of every white label package. Before setting it up, check that your subscription includes domain mapping and confirm which DNS record the platform requires. The provider may also need to verify that you control the domain before enabling it.

Once the DNS record has been added, the platform normally associates the domain with your white label account. It should then configure an SSL certificate so the address loads securely using HTTPS. This is important for login pages and client dashboards because browsers may warn users when a platform is not secured correctly. Do not assume that pointing the DNS record alone completes the setup; the domain may still need to be added and activated within the platform’s administration settings.

A typical setup involves the following:

• Choose whether to use a subdomain or a separate domain for the platform.
• Confirm the required DNS record and target with the platform documentation or support team.
• Add the record through your domain registrar or DNS hosting provider.
• Enter the domain in the white label settings and complete any ownership verification.
• Wait for the DNS change and SSL configuration to complete.
• Test the login page, dashboard, reports and client-facing emails using the new address.

Your main website does not usually need to be hosted on the same system. DNS simply directs the chosen domain or subdomain to the white label platform, while your main domain can continue to point to your existing website. Take care not to replace records that support your website, email service or other applications. If your organisation manages DNS centrally, the person responsible for your domain may need to make the change.

The branded domain normally covers the visible platform address, but white labelling can have other elements that need checking. Review the logo, colour scheme, page titles, browser icon, login wording, report branding and support contact details. If the platform sends emails, establish whether those messages use your domain as the sender address or continue to use a separate service address. Email authentication records, such as SPF, DKIM and DMARC, may be required when messages are sent on your behalf. These settings are separate from the DNS record used to route the platform.

It is also worth checking how client permissions work with a custom domain. The domain changes the address clients use; it does not by itself create separate client accounts or restrict access to particular campaigns. User roles, workspaces, campaign permissions and report visibility must still be configured within the platform. Test the experience from a client-level account as well as an administrator account to make sure that users see only the information intended for them.

Some limitations depend on the platform’s architecture. A custom domain may apply to the dashboard but not to every generated report, scheduled email, mobile interface or externally shared page. Certain features may continue to use a platform-managed address, particularly where they rely on a separate reporting, tracking or file-delivery service. Ask for a feature-specific explanation if consistent branding across all client touchpoints is important to your workflow.

Before making a domain live, test it in a private browser window and on different devices. Check that HTTPS works, login and password-reset links use the correct address, reports open without redirects to an unbranded domain, and browser warnings do not appear. Also decide what should happen to any previous platform URL. If the provider supports redirects, use them carefully and update saved bookmarks, client documentation and internal procedures.

A custom domain is therefore a practical part of a white label SEO setup, but the quality of the result depends on domain mapping, SSL, email configuration, user permissions and the scope of the platform’s branding controls. If the option is not visible in your account, confirm whether it requires activation, a particular plan or a support-led configuration before changing your DNS records.