Add the subdomain to the hosting tab of project settings (note that a site plan is required)
setup a new redirect with the old path being /pagename and the new redirect to the page on the Webflow site you want to redirect to, that being for example /about or whatever other page you want.
If the page name in the old wordpress site has the same page slug like /about in the old site and /about in the new site project in Webflow, you do not need to create a redirect, it is automatic.
Hi @dreweastmead, the A Record is only needed for the root domain, the research subdomain is setup on a cname record only pointed at proxy-ssl.webflow.com.
When setting the WWW domain as the default domain in Webflow the research subdomain will redirect to the WWW domain automatically.
It looks like many people want to route that example 3 subdomain to a subfolder in a new domain, not to the root. Without access to Htacces in Webflow, doing a Subdomain to Subdirectory 301 Redirect isn’t possible.
However, a workaround outside of webflow appears possible.
Meaning don’t add your “blog.mysite.com” domain to webflow, host it elsewhere and do the redirects there making them match the new blog posts in Webflow.
Google “Subdomain to Subdirectory 301 Redirect” and you’ll see lots of ways to do this. I may give it a shot myself though more cumbersome than having it all nice and tidy in Webflow.
If anyone has any other ideas, would love to hear them.
If I disconnect blog.mysite.com from project 2 and connect it to project 1 as a custom domain, while keeping the root domain as default, wouldn’t that work?
Yeah this is kind of annoying when migrating a WordPress blog from blog.domain.com to www.domain.com/blog in Webflow to have to add a 301 redirect for every post.
And that just the blog home blog.domain.com can’t redirect to Webflow’s www.domain.com/blog is also a major deal breaker.
@evolross Both wildcard redirect, and the base-path redirect are possible, but you’ll need to do the redirection externally for now. I’ve used Firebase for redirection in the past, and it now supports wildcards in its JSON redirect config.
Netlify has a similar redirection capability, with some pretty cool perks like language-based redirection.
Both offer a free base plan.
If you want something with an easier UI and zero tech-wizardry, there are services for that too.
Thanks for these. I remembered I already use AWS S3 for a lot of redirection and was able to get things working in that service. If anyone is curious about how to do this in AWS S3. It’s fairly technical FYI.