By Mehdi HassanCan you run Webflow and Framer on the same domain?
Yes. You can run Webflow and Framer on the same domain by giving each platform its own subdomain, or by putting a reverse proxy in front of both so each serves different paths. Teams use either setup to migrate in phases instead of switching everything in one night.
The common pattern is to move marketing pages to Framer first while the blog stays on Webflow until its content is cleaned and imported. That's a useful option when the CMS is large or messy. For the full migration process, see our Webflow to Framer migration guide.
Subdomain or reverse proxy: which setup should you use?
Use subdomains unless you have a strong reason to keep both platforms under one host. Subdomains need only DNS records and are supported by both platforms; reverse proxies add a layer you have to build, host and maintain.
Factor | Subdomains | Reverse proxy by path |
|---|---|---|
Example | www on Framer, blog on Webflow | / on Framer, /blog on Webflow |
Setup | DNS records only | Worker or proxy server plus DNS |
Platform support | Standard custom domains | Not a standard setup; check each platform |
SEO | Fine with good linking | Fine if canonicals and assets resolve |
Maintenance | Low | Ongoing; the proxy is your code |
Best for | Most phased migrations | Teams that must keep one host |
Google can rank content well on either a subdomain or a subdirectory. What matters more is that the two sections link to each other, share navigation and don't publish duplicate pages.
How do you set up Webflow and Framer on subdomains?
Connect your main domain to Framer and a subdomain to Webflow, or the reverse, using each platform's custom domain settings. Each platform gives you the DNS records to add at your registrar or DNS provider.
Pick the split
Decide which platform serves www and which serves the subdomain. Usually the new Framer site takes www.
Prepare redirects
If the blog moves from /blog to blog.yourdomain.com, map every old post URL to its new address.
Connect the domains
Add the subdomain in Webflow and the root in Framer, then update DNS records as each one instructs.
Load redirects
Add 301s in Framer for old /blog paths so they point to the Webflow subdomain.
Unify the experience
Match navigation, footer, fonts and tracking so visitors don't notice the switch between platforms.
The catch is the URL change. If your blog lives at /blog today, moving it to a subdomain changes every post URL, even if the plan is to bring it back to /blog on Framer later. Two URL changes mean two rounds of redirects.
How does a reverse proxy for Framer and Webflow work?
A reverse proxy sits in front of both sites and sends each request to the right platform by path. A request for /blog/post goes to Webflow; everything else goes to Framer. The visitor sees one domain.
Teams usually build this with an edge function such as a Cloudflare Worker, or with rewrites on a host they already use. The proxy has to pass through assets, rewrite links that point at the wrong host and handle each platform's canonical tags and sitemaps. Neither Webflow nor Framer treats proxying as a standard setup, so read each platform's current documentation and plan terms before you rely on it.
How do you run a phased Webflow to Framer migration?
Run a phased migration by moving the pages that change most first, and the pages with the most content last. For most teams that means marketing pages first and the blog later.
For example, suppose a 15-page site with a 400-post blog
Hypothetical example: a company has 15 marketing pages and a 400-post blog on Webflow. The blog has years of messy rich text and inline images.
Phase one moves the 15 marketing pages to Framer on www, while the blog moves to blog.yourdomain.com on Webflow with redirects from the old /blog paths. Marketing can ship new pages immediately.
Phase two cleans and imports the blog into Framer's CMS over the following weeks, then brings it back to /blog with a second set of redirects from the subdomain. If the team wants to avoid that double move, they keep the blog at /blog behind a proxy during phase one instead, accepting the extra setup in exchange for stable URLs.
The CMS phase is the slow one; our guide to Webflow CMS to Framer CMS covers the field mapping. If your site is multilingual, read moving a localized site from Webflow to Framer first, because locale paths add another layer to the split.
What are the trade-offs of running two platforms at once?
Running two platforms lowers launch risk but raises running costs and maintenance. It's a good bridge and a poor destination.
Pros
- Marketing pages go live without waiting for the CMS
- Smaller launches are easier to test and roll back
- Rankings from the blog stay stable while it waits
- Teams learn the new platform on a small scope first
Cons
- Two platform bills and two sets of seats
- Navigation and design must be kept in sync by hand
- Analytics and cookie consent need cross-host setup
- Subdomain moves can mean two rounds of redirects
If you're also testing landing pages, our guide to A/B testing in Framer, Webflow and Next.js covers how experiments work on each. For keeping both sections fast, see Core Web Vitals fixes by platform.
Who should run a split-platform setup?
A split setup suits teams with a large CMS, a busy marketing calendar and someone who will own the proxy or the subdomain links until the end. It doesn't suit a small site that could move in one go.
If you need a team on hand through a phased move, our monthly retainer is $6,000 a month for ongoing design and development, with no hourly tracking. It fits migrations that run alongside regular page work. For a one-off move, our guide to hiring a Webflow or Framer migration agency is the better starting point.
