Multiple domains and landing pages in one Webflow project. Possible?

Publishing help Project settings
1

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.

1 Like
2

Hey @mick.wieland , did you ever get this set up? I’d like to do the same thing.

3

This requires a unique project and hosting for each if using Webflow hosting. Off webflow this is trivial to handle using any modern web server.

1 Like
4

@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.

5

Hey Mick :wave:t2:!

Absolutely, you can achieve what you’re looking for with a single Webflow project. Here’s how it would work:

tvshow.com (main portal)
tvshow.com/ny → tvshow-ny.com
tvshow.com/ca → tvshow-ca.com
tvshow.com/uk → tvshow-uk.com

To set this up, you’d use :cloud: Cloudflare Workers as a reverse proxy. This allows you to:

  1. Build everything in one Webflow project
  2. Maintain consistent styling across all sites
  3. 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.

We’ve got a detailed guide on how to set this up here: Step-by-step guide to having multiple Webflow projects on the same domain | BRIX Agency

:memo: 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 :rocket:!

1 Like
6

@maurosicard This is super helpful! Forgive my ignorance, but will your approach work well for SEO? I have a client who is a hospitality group, and they already have two properties with their own URLs, sitemaps, etc and pretty good SEO ranking. I am creating a site for their parent company, as well as three new properties. I want each sub-property to have its own URL and sitemap as far as Google is concerned, but using only one project in Webflow. Will this work for that? Thanks so much.

7

@das0011 , Marcos might have a different answer but I build a lot of reverse proxies, so this might help.

Yes it’s possible, but you have a number of workers to build.

  • Rewriting worker for each domain, which knows the set of pages that relate to that domain and delivers them on request ( could be a subdirectory like /property1 ).
  • Navigation work, most likely to stitch everything together
  • Corrections for your canonical and og:url
  • Many more corrections if you add Localization at some point
  • Sitemap redesign for each site.

Built correctly, your SEO will be fine. Built incorrectly… chaos.

RP’s are fantastic but when you’re making broad sweeping changes like this to your site there’s a lot of infrastructure to consider, and you want to weigh that carefully against the benefits.

You might save a little bit on hosting and you might get some benefit out of a unified CMS across all 3 sites… but the tradeoff is a large development expense, and ongoing monitoring and maintenance.