Yes, you can host branded virtual tours on your own custom domain. The fastest route is a cloud white-label setup with DNS mapping and platform-managed SSL, while the route offering the most control is a self-hosted deployment. Either way, you will need DNS mapping, HTTPS, and a hosting or white-label setting configured on your platform. Simple Virtual Tour supports both paths.
TL;DR:
- Branded virtual tours can be hosted on a custom domain using either a cloud white-label setup or a self-hosted deployment, with DNS, HTTPS, and proper configuration required in both cases.
- Proper DNS management involves CNAME or A records, ownership verification with TXT or HTML files, and patience during DNS propagation, which can take up to 48 hours.
- Ensuring HTTPS with automatic or self-managed SSL certificates and a CDN is critical for security and performance, especially for large 360-degree images and videos.
- Self-hosting offers full control over code, certificates, and scaling but requires maintenance, while cloud white-label solutions enable faster setup with less upkeep but involve recurring fees.
- Moving a tour domain requires 301 redirects and canonical tags to preserve search rankings, with Google's Change of Address tool recommended for major domain changes.
Table of Contents
- What custom domain and white label mean for virtual tours
- Step-by-step setup: domain, DNS, and verification
- SSL, HTTPS, and CDN: keeping tours fast and secure
- Self-hosted vs cloud white-label: which fits your business
- SEO and migration: protecting your rankings when you switch domains
- How to choose: a short checklist before you commit
- How Simple Virtual Tour supports branded custom domains
- Choosing between ownership and speed
- Get your branded tours live with Simple Virtual Tour
- Sources
- FAQ
What custom domain and white label mean for virtual tours
A custom domain replaces a vendor's generic web address (like provider.com/yourtour) with your own, such as tours.yourbusiness.com. White label goes a step further: it strips away the vendor's visible branding so the experience looks like it was built entirely in-house.
When you set both up correctly, several elements shift:
- Tour URL: your domain or subdomain replaces the platform's default link.
- Visual branding: your logo, favicon, and interface colors replace the vendor's defaults.
- Metadata: page titles, descriptions, and social preview tags reflect your business, not the platform.
The payoff is trust and consistency. Clients touring a property or exhibit expect a seamless brand experience, and a custom domain also means the SEO value of every tour belongs to your business, not a third-party subdomain.
Step-by-step setup: domain, DNS, and verification
Connecting a custom domain to a virtual tour host follows a predictable sequence, though the exact screens vary by provider.
- Confirm DNS access and choose your hostname structure, such as tour.example.com versus tours.example.com.
- Check the platform's requirement: most ask for a CNAME record pointing your hostname to their service, though some enterprise setups use A records pointing to a fixed IP address.
- Verify ownership by adding a TXT record or uploading an HTML verification file, then confirm it inside your provider's dashboard.
- Add the domain in your tour platform's settings, then add or confirm the matching DNS records at your registrar.
- Wait for propagation. Changes can take anywhere from a few minutes to up to 48 hours depending on your record's TTL. Use
dig,nslookup, or an online DNS checker to confirm the change has spread. - Troubleshoot common mistakes: a CNAME pointed at the wrong target, a leftover A record conflicting with a new CNAME, or a TTL set too high to see changes quickly.
Pro Tip: Lower your TTL to 300 seconds a day before making DNS changes, then raise it again once everything resolves correctly. This shrinks your waiting window if something needs a quick fix.
Once DNS resolves and ownership is verified, your platform should activate the mapping automatically and begin serving your branded tour on the new address.
SSL, HTTPS, and CDN: keeping tours fast and secure
Modern browsers block or flag mixed content, so any tour served without HTTPS risks a broken embed or a security warning that undermines trust before a visitor even reaches your first panorama.
If you use a cloud platform, certificate management is usually automatic. Most SaaS virtual tour hosts issue certificates through Let's Encrypt or a similar managed certificate authority, renewing them without any action on your part. Self-hosted deployments put that responsibility on you: you will provision and renew your own certificate, typically through the same free authorities or a paid certificate from your hosting provider.
A content delivery network matters just as much for performance. 360° images and embedded video are large, and an edge-cached CDN keeps load times reasonable no matter where your visitor is located. Review your hosting requirements for CDN and bandwidth guidance before launch.
A CDN meaningfully improves load times for 360° imagery and interactive assets, and even small latency reductions noticeably improve the viewing experience for visitors moving between scenes.
Before you consider the setup finished, confirm a few basics:
- Auto-renewal is enabled for your certificate.
- HSTS is enforced so browsers always request the secure version of your domain.
- You have tested the domain with an SSL testing tool to catch configuration gaps.
Self-hosted vs cloud white-label: which fits your business
The right deployment model depends on how much control you need versus how quickly you want to launch.
Self-hosting gives you full ownership: you hold the source code, pay once rather than monthly, and control your own TLS certificates and CDN configuration. The tradeoff is maintenance. You are responsible for server updates, security patches, and uptime, which suits teams with existing DevOps capacity.
Cloud or SaaS white-label setups trade that control for speed. Certificates and CDN are managed for you, setup can take a single afternoon, and there is no server to maintain. The tradeoff is a recurring fee and less flexibility at the server level.
A few signals point you toward one or the other:
- In-house technical staff: favors self-hosting, since someone can manage servers and renewals.
- Need for source-code ownership or resale rights: favors self-hosting, particularly for agencies white-labeling tours for their own clients.
- Fast time to market with minimal maintenance: favors a cloud white-label plan.
- Unclear future traffic or SLA needs: favors starting cloud-hosted, since scaling is handled by the provider.
SEO and migration: protecting your rankings when you switch domains
Moving a virtual tour to a new domain without a plan can quietly erase months of search visibility. Two actions protect that visibility: server-side 301 redirects from every old tour URL to its new equivalent, and a canonical tag confirming which version search engines should index.
If you are moving an entire domain, not just individual pages, file a Change of Address request in Google Search Console once your redirects are live. This requires verified ownership of both the old and new domain properties in Search Console, and it does not automatically cover subdomains unless you include them explicitly.
Change of Address forwards site signals for 180 days and requires domain-level verification. It does not move path-level properties or unlisted subdomains on its own.
After the move, watch Search Console's crawl reports, index coverage, and traffic trends for two to six months. Review our virtual tour SEO guidance for additional steps on preserving visibility during a migration.
How to choose: a short checklist before you commit
Before signing up for any platform or vendor, run through a short list of technical questions. This will surface gaps before they become live-site problems.
- Does the platform allow full custom URL control, not just a branded subdomain of their own domain?
- Is SSL provisioning automatic, or will you need to manage certificates yourself?
- Is there an export or self-host option if you later want to leave the platform?
- Does the provider include CDN delivery for large 360° assets?
- Can you integrate your own analytics and manage multiple white-label accounts if you resell tours?
Pro Tip: Ask any vendor directly about their export format, certificate renewal process, and CDN provider by name. A vague answer to any of these three questions is worth treating as a warning sign.
Watch for red flags: no HTTPS support, no clear DNS instructions, or an inability to change basic metadata like your favicon or page title. Any of these suggests the platform was not built with white-label branding in mind.
How Simple Virtual Tour supports branded custom domains
Simple Virtual Tour offers both cloud-hosted and self-hosted deployment models, giving you a choice between managed convenience and full source-code ownership. Both models support custom branding, unlimited tours, and integrations like e-commerce and live session hosting.
The setup path follows the same structure outlined above: verify your domain, add the required DNS records, enable SSL, then publish your branded tour under your own address. Full technical detail lives in the hosting requirements guide.
Choosing between ownership and speed
If your organization plans to keep its virtual tours for years, values exportability, or wants to resell white-label tours under its own name, self-hosting is worth the added maintenance. It puts the source code and your data fully in your hands.
If you need something live this week and don't want to manage certificates or a CDN, a cloud white-label plan gets you there faster with less upkeep. Simple Virtual Tour's dual deployment model means you are not locked into one path from day one.
— Andrea
Get your branded tours live with Simple Virtual Tour
Whether you want a managed cloud plan or a self-hosted setup with full source-code ownership, Simple Virtual Tour supports custom domains, white-label branding, and unlimited tours under either model.
Plans range from the Free Forever tier through XS, S, and larger tiers, and the self-hosted CORE package is available as a one-time purchase. Compare deployment options and get started today to see which fits your setup.
FAQ
Can I use a custom domain with any virtual tour platform?
Not always. Some platforms restrict you to their subdomain, so confirm custom domain support and white-label branding before committing to a provider.
How long does DNS propagation take for a new tour domain?
Propagation typically completes within minutes but can take up to 48 hours depending on your DNS record's TTL setting. Checking with a DNS lookup tool confirms when the change has fully spread.
Do I need an SSL certificate if my platform already has one?
Yes, your custom domain needs its own valid certificate even if the underlying platform is already secured. Cloud platforms usually issue this automatically, while self-hosted setups require you to provision and renew it yourself.
What happens to my search rankings if I switch domains?
Rankings can dip temporarily during a move, which is why 301 redirects and Google's Change of Address tool are essential before and after the switch. Monitoring Search Console for a few months afterward helps you catch and fix any indexing issues quickly.
Does Simple Virtual Tour support both cloud and self-hosted custom domains?
Yes, Simple Virtual Tour offers both cloud-hosted and self-hosted deployment, letting you choose managed convenience or full control over your domain and server setup. Both options support custom branding and unlimited tours.