You cannot natively assign a different subdomain to a single page within a Webflow project using built-in Webflow settings alone. Webflow assigns domains and subdomains at the project level, not the page level.
However, there are a few possible workarounds depending on your hosting setup.
1. Understand Webflow's Domain Structure
- Custom domains (including subdomains) are mapped to an entire Webflow project.
- You cannot assign a unique subdomain (e.g., blog.yoursite.com) to just one page of a project using only Webflow’s settings.
- Webflow doesn't support per-page domain routing within one project.
2. Use Reverse Proxy as a Workaround
- A reverse proxy can route requests to a specific subdomain (e.g., blog.yoursite.com) to a particular page in your Webflow project (e.g., yoursite.com/blog).
- You’ll need to set this up using a server environment like Nginx or Cloudflare Workers.
- This method requires moderate technical skills and external hosting access.
3. Use a Custom Script on Your Domain Host
- If your domain/hosting provider supports path- or subdomain-level redirects, you may be able to technically redirect requests from a subdomain to a full-page URL.
- Example: Redirect blog.yoursite.com to yoursite.com/blog.
- However, this is just a redirect—the URL in the browser will likely change unless a proxy is used.
4. Duplicate Page in a New Webflow Project (If Clean Domain Separation is Needed)
- If you need true domain separation where the visible URL stays the subdomain, and you do not want to manage a reverse proxy, your only option is to:
- Duplicate the page into a separate Webflow project.
- Assign the subdomain (e.g., blog.yoursite.com) to this new project.
Summary
You cannot point a single Webflow page to a different subdomain using Webflow alone. If you need to preserve the subdomain in the browser address bar, use an external reverse proxy or create a separate Webflow project for that subdomain.