Can I point only one page in a Webflow project to a different subdomain without creating a new project?

You cannot natively point a single page in a Webflow project to a different subdomain using Webflow’s built-in hosting settings—you would need external configuration or a workaround.

1. Webflow Limitations

• Webflow's hosting assigns a domain or subdomain to the ENTIRE site, not individual pages.
• You cannot map a single page (e.g., /about) to a different domain or subdomain (e.g., about.example.com) from within Webflow's native controls.

2. Available Workaround: Reverse Proxy

• Use a reverse proxy setup on an external server (like NGINX or Cloudflare Workers).
• Configure that server to serve the specific Webflow page (e.g., /about) at a specific subdomain (e.g., about.example.com).
• Example:
• The main site lives at example.com, hosted on Webflow.
• You configure a reverse proxy so about.example.com fetches the /about page from Webflow and displays it on that subdomain.

3. Webflow Page Slug Is Still Required

• The page will still technically exist at example.com/about.
• The reverse proxy acts as a “masking” layer for the subdomain but doesn’t change the actual Webflow structure.

4. Custom Code Routing (Not Recommended)

• You could try using JavaScript redirects or iframe embedding, but:
• It’s less reliable for SEO and performance.
• Embedding Webflow pages in iframes often leads to design and security constraints.

5. When a New Webflow Project Is Required

• If you need true subdomain separation (e.g., a full blog at blog.example.com with its own Webflow CMS structure), you’ll need a new Webflow project.

Summary

Webflow doesn't support assigning a single page to a different subdomain natively. To achieve this, use a reverse proxy workaround or create a separate project if the use case requires CMS or design independence.