Webflow does not natively support full URL path forwarding when redirecting from a subdomain (e.g., blog.domain.com
) to the root domain (domain.com
). However, there are alternative methods to achieve this behavior using third-party tools or external hosting.
1. Use a Reverse Proxy (e.g., Cloudflare Workers or NGINX)
- Cloudflare Workers can intercept requests at the edge and rewrite the full URL path to the correct root domain path.
- Example: A request to
blog.domain.com/posts/123
can be programmatically redirected to domain.com/posts/123
. - Requires a Cloudflare account and some basic JavaScript knowledge.
2. Use an External Hosting Provider for the Subdomain
- You can configure your subdomain (
blog.domain.com
) to point to a small VPS or a platform like Vercel or Netlify. - There, you can set up 301 redirects using server configuration or rewrite rules.
- This approach allows full control of path forwarding—not restricted to just root-level redirects.
3. Use .htaccess (Not Applicable Directly on Webflow)
- If you're using Webflow for the root domain and a separate Apache server for the subdomain, adding a
.htaccess
rule on the subdomain's server can handle full path forwarding. - This is ideal for legacy subdomains that existed before using Webflow.
4. Manually Create Redirects in Webflow
- If only a few paths need redirection, use 301 redirects in Webflow:
- Go to Project Settings > Hosting > 301 Redirects
- Enter a redirect like
/old-path
→ /new-path
- This method does not scale well if you have hundreds of dynamic URLs.
Summary
Webflow does not support full path forwarding between subdomains and root domains by default. To implement this function, use Cloudflare Workers, external hosts like Netlify/Vercel, or configure redirects on another server that handles the subdomain. These methods ensure that path-level URL forwarding works as expected.