Getting Started

Subpath is a reverse proxy built for Webflow and no-code sites. With Subpath you can host multiple projects under a single domain, integrate external platforms like Ghost or WordPress, and get automatic SSL for every domain you connect.

ℹ️

Subpath is in active development. The product described in this documentation reflects the full feature set at launch. Join the waitlist to get early access.

What can Subpath do?

Host multiple Webflow projects under a single custom domain using subfolders (e.g. yourdomain.com/blog)
Integrate any web platform, Webflow, Framer, Ghost, WordPress, Shopify, under one domain
Automatically provision free TLS/SSL certificates for every domain you connect
Merge all your Webflow project sitemaps into a single unified sitemap.xml
Configure and update routes instantly. No redeployments, no waiting.

How does Subpath work?

Subpath is a reverse proxy, which means it sits in front of your Webflow site and intercepts incoming requests. When a visitor accesses yourdomain.com/blog, Subpath routes that request to your Webflow blog project, transparently, with no visible redirect.

Subpath is optimized for performance and low latency, keeping overhead minimal for visitors regardless of their location.

When you update a route in your Subpath dashboard, the change takes effect globally within seconds. No server restarts, no redeployments.

Quick setup

1

Create a Subpath account

Sign up at subpath.app with your email or Google account. Your account comes with a free trial during beta.

2

Add your domain

In your dashboard, click Add domain and enter your domain name (e.g. yourdomain.com). Subpath will generate the DNS records you need to configure.

3

Configure your DNS

Add the CNAME record shown in your dashboard to your DNS provider. Point your domain's CNAME to proxy.subpath.app. Subpath will verify the DNS and provision your SSL certificate automatically, usually within 5 minutes.

4

Create your first route

Once your domain is verified, go to Routes and add your first path. Set the root path / to your main Webflow project, and add additional paths like /blog for other projects.

Prerequisites

A domain name you control (registered with any provider: Cloudflare, GoDaddy, Namecheap, etc.)
At least one Webflow project with a paid hosting plan (required by Webflow's terms to use custom domains)
Access to your domain's DNS settings to add a CNAME record

⚠️

Each Webflow project you use as a route destination must have a paid Webflow Site Plan. Subpath routes traffic to your projects but does not replace Webflow hosting. Using Subpath to serve Webflow staging URLs (*.webflow.io) on a production domain violates Webflow's terms of service.

Subfolders

Subfolders let you host multiple Webflow projects (or any other platform) under different URL paths of a single domain. Instead of splitting your content across subdomains, everything lives under yourdomain.com.

Why use subfolders?

Webflow's default behavior forces you to either use subdomains (blog.yourdomain.com) or upgrade to an Enterprise plan to host multiple projects on one domain. Both options have real costs:

Subdomains fragment your SEO. Google treats blog.yourdomain.com as a separate website from yourdomain.com. Your blog's backlinks and content don't boost your main site's domain authority.
Enterprise plans are expensive. Webflow Enterprise starts at ~$500/month. Subpath achieves the same multi-project setup for $19/month.
Subfolders consolidate authority. When your blog lives at yourdomain.com/blog, every backlink and every page view contributes to a single domain's ranking power.

Setting up a subfolder route

1

Set up your Webflow origin subdomain

In Webflow, for each project you want to proxy, add a dedicated origin subdomain (e.g. wf.yourdomain.com) as a custom domain in your Webflow project settings. This is the internal domain Subpath will fetch content from. Do not use your *.webflow.io staging URL as the destination.

2

Add a route in Subpath

In your Subpath dashboard, go to your domain's Routes tab and click Add route. Enter the path prefix and the destination URL.

3

Configure route options

Choose whether to strip the path prefix when forwarding to the destination. For most Webflow setups, leave this off. Webflow expects the full path.

Example configuration

A typical multi-project Webflow setup:

Path	Destination	Platform
`/`	`wf.yourdomain.com`	Webflow (main site)
`/blog`	`wf-blog.yourdomain.com`	Webflow (blog project)
`/docs`	`docs.yourdomain.ghost.io`	Ghost
`/shop`	`yourstore.myshopify.com`	Shopify

⚠️

Route order matters. Subpath matches routes from most specific to least specific. The root path / should always be the last route, as it matches everything not caught by a more specific path.

SEO considerations

When using subfolders with multiple Webflow projects, set a global canonical URL on each project pointing to the public subfolder URL, not the Webflow origin subdomain. This prevents search engines from indexing your internal origin subdomains.

Subpath automatically rewrites internal links in the HTML response so that relative links within each project resolve correctly through the proxy. You don't need to configure this manually.

Limitations

Webflow Editor: The Webflow visual editor may not function through the proxy. Use the Webflow origin subdomain to access the editor.
Webflow Membership pages: Some Webflow Membership features may require additional configuration when proxied.
Each Webflow destination must have a paid Webflow site plan with a custom domain connected.

Domains

Subpath supports custom domains with automatic SSL provisioning. Connect any domain you own and Subpath handles the rest: certificate issuance, renewal, and global CDN distribution.

Connecting a domain

1

Add your www subdomain in the dashboard

Go to Domains → Add domain. Enter your www subdomain (e.g. www.yourdomain.com). This is the domain Subpath will proxy. Do not enter the root domain or include https://.

2

Point www to Subpath via CNAME

Add the following CNAME record at your DNS provider:

Type:  CNAME
Name:  www
Value: proxy.subpath.app
TTL:   Auto (or 300)

Remove any existing Webflow DNS records for www before adding this record.

3

Redirect the root domain to www

Root/apex domains (e.g. yourdomain.com) cannot use a CNAME record. Instead, configure a URL redirect from your root domain to https://www.yourdomain.com. Most DNS providers and registrars offer a redirect or URL forwarding option for the apex domain. Check your provider's documentation for "URL redirect" or "web forwarding".

4

Wait for verification

Subpath automatically checks your DNS every 15 minutes. DNS propagation typically takes 5–30 minutes, but can take up to 48 hours depending on your registrar's TTL settings. You'll receive an email when your domain is verified and SSL is active.

SSL certificates

Subpath provisions free TLS/SSL certificates for every domain you connect. Certificates are:

Automatically issued when DNS is verified. No manual steps required.
Automatically renewed before expiration. You never need to think about renewals.
Wildcard-capable. Your certificate covers both yourdomain.com and *.yourdomain.com
Free. SSL is included in all Subpath plans at no extra charge.

Domain status

Status	Description
`Pending`	DNS CNAME has been added but not yet verified. Subpath is checking every 15 minutes.
`Active`	DNS verified, SSL issued. Your domain is fully operational.
`Error`	DNS verification failed or SSL could not be provisioned. Check your DNS records and try again.

Why www and not the root domain?

DNS does not allow CNAME records on apex (root) domains like yourdomain.com, only on subdomains. By using www.yourdomain.com as your primary domain, Subpath can reliably proxy your traffic via a standard CNAME. The root domain then redirects to www via a URL redirect at your DNS provider, so visitors who type either version always reach your site.

Sitemaps

When you use multiple Webflow projects on one domain, each project generates its own sitemap.xml file. Without merging, search engines only see the sitemap of whichever project is at the root path. Subpath's sitemap feature solves this by generating a unified sitemap that includes all your projects.

The problem with multiple sitemaps

If you have three Webflow projects at /, /blog, and /docs, they each produce their own sitemap:

yourdomain.com/sitemap.xml          → Only covers pages at /
wf-blog.yourdomain.com/sitemap.xml  → Only covers blog pages
wf-docs.yourdomain.com/sitemap.xml  → Only covers docs pages

Google's crawler, when visiting yourdomain.com/sitemap.xml, only sees the pages from your main Webflow project. Your blog and docs pages are invisible to the automatic sitemap discovery.

Subpath's unified sitemap

With sitemap merging enabled, Subpath generates a single sitemap.xml that combines all your projects:

<?xml version="1.0" encoding="UTF-8"?>
<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <sitemap>
    <loc>https://yourdomain.com/sitemap-main.xml</loc>
  </sitemap>
  <sitemap>
    <loc>https://yourdomain.com/sitemap-blog.xml</loc>
  </sitemap>
  <sitemap>
    <loc>https://yourdomain.com/sitemap-docs.xml</loc>
  </sitemap>
</sitemapindex>

Each individual project sitemap is fetched from your Webflow origin, with URLs rewritten to reflect the public path structure (e.g. https://yourdomain.com/blog/article-1 instead of https://wf-blog.yourdomain.com/article-1).

Enabling sitemap merging

Sitemap merging is available on Pro and Agency plans. To enable it:

Go to your domain's settings in the Subpath dashboard
Open the Sitemaps tab
Toggle Enable sitemap merging
Subpath will immediately begin serving the unified sitemap at yourdomain.com/sitemap.xml

✅

Submit to Google Search Console. After enabling sitemap merging, submit https://yourdomain.com/sitemap.xml to Google Search Console. This ensures all your pages across all Webflow projects are indexed promptly.