Can You Host Your Brand Community on Your Own Domain with a White-Label Setup?
Many brands want their community experience to live directly within their own digital ecosystem rather than under a third-party domain. A white-label subdomain setup allows you to host your community under your brand’s domain while still leveraging the capabilities of the Genuin platform.
This guide explains how to configure a Subdomain White-Label Solution, including DNS setup, CNAME configuration, and the SEO advantages of hosting your community under your own domain.
Introduction
The Subdomain White-Label Solution enables brands to host their community under their own domain while the infrastructure continues to run on Genuin.
Instead of directing users to a default platform URL, you can map your brand’s domain to your community environment.
For example:
| Default Community URL | White-Label Community URL |
|---|---|
| sephora.begenuin.com | community.sephora.com |
This creates a seamless brand experience where users interact with the community as part of your brand’s website.
Prerequisites
Before configuring the white-label setup, ensure the following:
- Genuin has already created your community instance
- You have received your community subdomain URL from Genuin (example: sephora.begenuin.com)
- You have access to your domain DNS provider
Once these prerequisites are met, you can proceed with configuring DNS records.
How the White-Label Mapping Works
The white-label setup uses a CNAME record in your DNS configuration.
The mapping typically looks like this:
| Field | Value |
|---|---|
| Host / Name | community |
| Points To | sephora.begenuin.com |
This means: community.sephora.com > sephora.begenuin.com
Users will see your brand domain, while traffic is routed to the Genuin community infrastructure.
Steps to Configure the White-Label Subdomain
Follow these steps to map your brand community domain.
Step 1: Log in to Your DNS Provider
Access the control panel of the DNS provider where your domain is hosted.
Common DNS providers include:
- GoDaddy
- Namecheap
- Bluehost
- HostGator
- Google Domains
- AWS Route 53
- Cloudflare
- DreamHost
Once logged in, locate the DNS management section.
Step 2: Open DNS Management
Navigate to the section where DNS records can be modified.
This section may be labeled:
- DNS Management
- DNS Settings
- Manage DNS
- Zone Editor
The exact name varies depending on your provider.
Step 3: Locate the CNAME Record Option
Within DNS management, look for the option to add or edit a CNAME record.
Different providers may refer to it as:
- CNAME Record
- Alias
- Canonical Name
Step 4: Add a New CNAME Record
Create a new CNAME record with the following configuration:
| Field | Example Value |
|---|---|
| Name / Host | community |
| Points To / Value | sephora.begenuin.com |
This configuration maps the brand subdomain to the Genuin community environment.
Step 5: Save the DNS Changes
After entering the required details:
- Click Save, Apply, or Update
- Confirm the changes
Your DNS provider will then update the domain configuration.
Example DNS Setup Across Common Providers
Below are quick references for configuring CNAME records across popular DNS providers.
GoDaddy
- Sign in to the GoDaddy Domain Control Center
- Select your domain to open the Domain Settings page
- Scroll to Additional Settings
- Select Manage DNS
- Add or edit the CNAME record
- Enter the details provided by Genuin and save
Namecheap
- Log in to your Namecheap account
- Go to Domain List
- Click Manage next to your domain
- Open the Advanced DNS tab
- Locate Host Records
- Add a CNAME Record with the required values
- Save the changes
Bluehost
- Log in to the Bluehost control panel
- Navigate to Domains
- Select the domain you want to configure
- Open the DNS Zone Editor
- Scroll to the CNAME section
- Add the record and save
HostGator
- Log in to your HostGator cPanel
- Go to Domains > Zone Editor
- Select Manage next to your domain
- Click +CNAME Record
- Enter the required details and save
Google Domains
- Sign in to Google Domains
- Select your domain
- Click DNS from the left menu
- Scroll to Custom Resource Records
- Add the CNAME record and save
AWS Route 53
- Open the AWS Management Console
- Navigate to Route 53
- Select Hosted Zones
- Choose your domain
- Click Create Record
- Add the CNAME configuration provided by Genuin
Cloudflare
- Log in to your Cloudflare dashboard
- Select your domain
- Navigate to the DNS tab
- Click Add Record
- Choose CNAME
- Enter the host and target domain
DreamHost
- Log in to the DreamHost web panel
- Navigate to Domains > Manage Domains
- Select the domain you want to edit
- Click DNS
- Add the new CNAME record using the values provided by Genuin
DNS Propagation Time
After saving your DNS configuration, the changes must propagate across the internet.
Typical propagation times include:
| Time Range | Details |
|---|---|
| Few Minutes | For some DNS providers |
| Up to Several Hours | Depending on global DNS updates |
During this time, some users may still be redirected to the previous destination.
Verifying the Configuration
Once propagation is complete, verify the setup.
Open a browser and visit your mapped domain.
Example: community.sephora.com
If configured correctly, the domain will resolve to your Genuin community instance.
Benefits of the White-Label Subdomain Solution
Hosting your community under your own domain provides several strategic advantages.
1. Stronger Brand Identity
Instead of sending users to a third-party platform URL, your community becomes part of your brand ecosystem.
Example: community.ted.com , feels like a natural extension of your website.
This improves brand trust and user experience.
2. Seamless User Experience
Users remain within your brand environment while interacting with community content.
This ensures:
- Consistent branding
- Familiar navigation
- Better engagement
3. Improved SEO and Discoverability
One of the most significant advantages of the white-label solution is improved search engine visibility.
When community content is hosted under your brand domain:
- All content contributes to your website’s domain authority
- Search engines see community pages as part of your primary site
- Content has a better chance of ranking in search results
This can lead to:
- Higher search engine rankings
- Increased organic traffic
- Greater discoverability of community discussions and content
How White-Label Setup Improves Google Indexing
Search engines like Google prioritize websites with strong authority and relevant content.
When your community resides under your own domain:
- Community posts contribute to your site’s overall SEO strength
- Google indexes the content as part of your brand domain
- Internal linking between your website and community improves crawlability
This consolidated structure improves the chances of ranking higher in Search Engine Results Pages (SERPs).
Final Thoughts
The Subdomain White-Label Solution enables brands to host their communities under their own domain while leveraging the capabilities of the Genuin platform.
By configuring a simple CNAME DNS mapping, you can:
- Deliver a fully branded community experience
- Maintain consistent user journeys
- Improve search visibility and indexing
- Strengthen your digital ecosystem
For brands investing in long-term community engagement, this approach ensures that your community becomes a natural and valuable extension of your brand’s online presence.