I’m in talks with a potential client who wants a ‘family’ of websites that I will build in Webflow. They have five domains that represent five different TV shows they produce. ie: tvshow-ny.com, tvshow-ca.com, tvshow-uk.com, etc.
I would like to build ONE site in Webflow for ease of management. I would have the home page be a portal site, then site folders representing each domain. ie: A subfolder named “NY” for tvshow-ny.com.
My question: Can I build and host ONE webflow site with folder subdirectories, then have each domain point to those respective folders? The domains need to show up in the browser as masked domains. ie: tvshow-ny.com, not tvshow.com or tvshow.com
The styling across all these sites needs to be identical so I would rather manage ONE Webflow project with subdirectories representing each domain, instead of trying to manage identical styling across 5 separate Webflow projects.
Is this possible with Webflow?
These sites aren’t built yet so I don’t have a read-only link to share yet.
@Keven to expand a bit on Jeff’s solution, you have three options with varying tradeoffs.
If you’re hosting on Webflow to make use of the CMS, Logic, Memberships, Commerce, etc, you can either do redirect at your DNS provider ( e.g. cloudflare ) from your domain to your sub-folder, or you can research and build a reverse proxy setup.
The former approach will show your redirected folder-level URL, while the latter will show the domain- however the reverse proxy is significantly more complex to setup.
If you’re building your site on Webflow and then exporting it to host elsewhere, you can customize domain routing however you like using that server’s in-built capabilities, e.g. using an .htaccess file.
To set this up, you’d use Cloudflare Workers as a reverse proxy. This allows you to:
Build everything in one Webflow project
Maintain consistent styling across all sites
Have each domain show up as its own site (not as a subfolder, even they technically are just a subfolder under the same Webflow project)
The Cloudflare Worker will handle the routing, so when someone visits tvshow-ny[.]com, they’ll see the content from tvshow[.]com/ny, but their browser will still show tvshow-ny[.]com.
Quick note: As others suggested, doing a 301 redirect from the domains to the /subfolders isn’t a good approach here. Users would still see they’re on a /subfolder/, which isn’t great for consistency or branding.
Let me know if you need any clarification or have more questions. Happy to help you get this set up !