How to set up a reverse proxy for Webflow.
There are three real ways to serve a Webflow site from a path on your own domain, and a managed one. This guide walks through all of them honestly: what you build, what you maintain, and the SEO details that bite either way.
What you are building
A reverse proxy answers for your domain, looks at each request's path, and fetches the content from the platform that serves it: Webflow for the marketing pages, and whatever else you run for the rest. Visitors and search engines see one domain; every platform keeps its own hosting and editor.
Before you start, you need: a published Webflow site, control over your domain's DNS, and a decision about where Webflow should live - / for the whole marketing site or a subfolder like /landing.
The three DIY routes
Cloudflare Workers
A worker script at the edge fetches your Webflow site and serves it under your domain path.
- 1.1Move your domain onto Cloudflare so a worker can sit on its routes.
- 1.2Write a worker that maps incoming paths to your Webflow site and forwards the request with the right Host header.
- 1.3Rewrite links, redirects, and asset URLs in the response so visitors stay on your domain.
- 1.4Bind the worker to the routes it should own and deploy.
watch out for: Redirect loops with Webflow’s own www redirect, canonical tags still pointing at the old host, and every future routing change being a code deploy.
nginx on your own server
A classic proxy_pass setup on infrastructure you run.
- 2.1Provision a server and point your domain (or the path’s host) at it.
- 2.2Configure proxy_pass to your Webflow site with the Host header and forwarded headers set correctly.
- 2.3Issue TLS certificates and automate their renewal.
- 2.4Rewrite response URLs where needed and reload the config.
watch out for: Certificate renewals, patching and monitoring a live server, and a config file that gets riskier to touch as routes accumulate.
Vercel or Next.js rewrites
A rewrites block in a project you already deploy proxies the path to Webflow.
- 3.1Add a rewrite rule mapping /path (and /path/:match*) to your Webflow site’s URL.
- 3.2Make sure your framework passes through query strings and headers you rely on.
- 3.3Deploy and test forms, redirects, and nested pages behind the rewrite.
watch out for: Caching behavior you do not control end to end, and rewrites that silently miss edge cases like trailing slashes or hashed asset paths.
The SEO checklist, whichever route you pick
The proxy is the easy half. These six details decide whether the migration helps or hurts your rankings.
One canonical host
Canonical tags, og:url, and internal links must all point at your domain, not the Webflow subdomain the content came from.
301 the old URLs
If the site previously lived on a subdomain, permanently redirect every old URL to its new path so earned links keep counting.
Consistent trailing slashes
Pick one form and redirect the other. Two URLs serving the same page splits signals and wastes crawl budget.
Sitemap and robots.txt
Your domain’s sitemap must list the new paths, and robots.txt must not block the proxied section.
Test the interactive parts
Forms, CMS pages, search, and redirects all behave differently behind a proxy than on direct hosting. Test before and after cutover.
Watch Search Console
Crawl errors and coverage reports in the first weeks tell you whether the proxy handles edge cases correctly.
The managed shortcut
Everything above is buildable, and if you have an engineer who wants to own it, DIY is a legitimate choice. Utilly exists for every other team: connect the Webflow site, map the path, preview, and go live with one DNS change. Routing, caching, TLS, and the checklist items above are handled by default, and rollback is the same DNS change in reverse.
Webflow reverse proxy FAQs
Does Webflow support subfolder serving natively?
No. Webflow serves your site on its own hosting under your connected domain or a webflow.io subdomain. Serving it as a path of a domain that another platform also uses requires a reverse proxy in front, whichever tool provides it.
Will forms, CMS content, and interactions work through a proxy?
Yes, if the proxy passes requests through at the HTTP level with the right headers. This is one of the things to verify explicitly during preview, whichever route you pick.
Do I still need Webflow hosting?
Yes. A reverse proxy does not replace hosting; it changes the address visitors see. Webflow keeps building and serving the site behind the scenes.
Should Webflow live at the root or in a subfolder?
Both work. Marketing sites usually take the root, with the blog, docs, and app in subfolders or on an app subdomain. The proxy decides per path, so you can change your mind later.