You cannot host multiple client websites on subdomains under a single Webflow hosting plan. Webflow requires separate site hosting for each project, but you can still use subdomains with limitations.
1. Webflow Hosting Is Per-Site
- Each Webflow project requires its own site plan (e.g., Basic, CMS, Business) to be published on a custom domain or subdomain.
- You cannot use one hosting plan to support multiple Webflow projects across subdomains like client1.youragency.com, client2.youragency.com without buying separate hosting for each.
2. Subdomains Are Allowed Per Project
- You can assign a subdomain (e.g., client1.youragency.com) to individual Webflow projects by:
- Adding the subdomain under Project Settings > Hosting.
- Pointing your DNS to Webflow’s A records: (a) 75.2.70.75 and (b) 99.83.190.102.
- Each subdomain still needs its own Webflow hosting plan.
3. Client Billing Helps Offset Costs
- Client Billing in Webflow lets clients pay directly for their site’s hosting.
- You can set billing rates and automate charges per hosted site without having to cover costs yourself.
- This model lets you work with many clients on Webflow, each with their own subdomain and billing.
4. Alternative Approach: Use a Webflow CMS with User Accounts (Workaround)
- If your clients only require basic site pages or dashboard-type content, you could:
- Use one Webflow CMS site.
- Create separate CMS collections for each client.
- Show/hide content with gated access via tools like Memberstack or Outseta.
- This won't work if clients need completely separate domains or advanced individual site functionality.
Summary
You can host different client websites on subdomains within Webflow, but each requires its own hosting plan. Webflow's per-site hosting model doesn’t allow multiple client sites under one plan like some traditional hosts. For cost management, use Client Billing to delegate hosting expenses to each client.