You can redirect a subdomain within the same Webflow project without purchasing separate hosting, but with limitations on how subdomains are handled. Here’s how to approach it.
1. Webflow Hosting Covers One Domain Structure
- Webflow’s hosting plan covers one domain and its subdomains in a single project.
- For example, if your main domain is example.com, you can include subdomains like blog.example.com or info.example.com under the same project without buying extra hosting.
- You do not need separate hosting for subdomains, but Webflow treats it as one domain setup.
2. Use Webflow Site Settings for Redirects
- Webflow supports standard 301 redirects via Project Settings > SEO > 301 Redirects.
- You can redirect URLs like /subpage to another page, but not subdomains to subdomains or subdomains to root using this panel directly.
3. DNS-Level Control Is Required for Subdomain Redirects
- Webflow does not offer native subdomain-to-subdomain redirects via its UI.
- To redirect subdomain.example.com → example.com/page, you must configure this at your DNS provider (e.g., GoDaddy, Cloudflare).
- Create a CNAME or A record pointing the subdomain to Webflow’s servers: (a) 75.2.70.75, (b) 99.83.190.102.
- Then add the subdomain as a custom domain in the Webflow Project Settings > Hosting and create a page or redirect path as needed.
4. Handle Redirect Using Landing Pages in Webflow
- If DNS is pointing a subdomain to Webflow, you can create a landing page designed specifically for that subdomain (e.g., site.com/redirect).
- Use the Webflow 301 Redirects feature to point /redirect automatically to the desired destination.
- This method is a workaround since Webflow doesn’t support wild-card subdomain redirects.
Summary
You can redirect a subdomain within the same Webflow project without buying additional hosting, but you'll need to manage DNS and may have to use internal landing pages plus a 301 redirect. Webflow does not offer direct subdomain redirect settings, but it supports subdomains under one hosting plan.