How to use Multi Site with rewrite rules

Multi Site allows you to combine multiple websites under a single domain using rewrite rules. Manage rewrites directly in Framer instead of setting up a custom reverse proxy like using Cloudflare or Vercel.

What are rewrites?

Rewrites display content from different Framer sites or external sources while keeping the original URL visible in the browser, letting you host multiple sites under a single domain. (Redirects, in contrast, change the URL in the browser.)

For example:

  • Your main site is at designer.com

  • Your blog (a separate Framer project) can appear at designer.com/blog

  • Your documentation (hosted externally) can appear at designer.com/docs

All of this happens seamlessly, and visitors see a single, unified domain.

Use cases

Migrating from another platform – Move your existing site to Framer step by step by redirecting selected pages or sections, while keeping the rest of your site active on its current platform.

Organizing large websites – Split your site into smaller, manageable projects that are easier to develop and maintain independently.

Combining Framer with external tools – Serve your main site from Framer while integrating external services like a shop, documentation site, or custom application.

Team collaboration – Allow different teams to work individually on different sections of your website without conflicts.

How to set up rewrite rules

Go to the Framer dashboard, select your domain in the sidebar, and navigate to the Multi Site tab.

Adding a rewrite rule

  1. Click the + icon to add a rule

  2. Choose the rewrite type:

    • Project: Route to another Framer project

    • External: Route to an external website

  3. Enter the path where you want the content to appear (e.g., /blog or /blog/*)

  4. Enter the target:

    • For projects: Select your Framer project and specify the path

    • For external: Enter the full URL of the external site

  5. Click Add to save the rule

  6. Publish your project for the changes to go live

Path patterns

  • Wildcard matching: Use * to match any path segment

    /blog/* matches /blog/my-post, /blog/2024/update, etc.


  • Dynamic parameters: Use :parameter for dynamic segments

    /blog/:slug matches /blog/my-post and captures "my-post" as the slug

Managing rules

  • Reorder rules: Drag and drop to change priority (rules are evaluated in order)

  • Edit & delete rules: Click the ··· menu or right click to edit or remove rules

  • Applying changes: Open and publish your project for the changes to take effect

Examples

Migrate to Framer from an external provider

If you want to move your site to Framer without rebuilding everything at once, you can migrate page by page. Start by recreating key pages in Framer, connecting your domain, then use rewrites to serve specific paths from your new Framer project while the rest of your site stays on your current provider.

Path: /*
Target: old-site.com/:1

This pulls all the content from your existing website and hosts it under your custom domain in Framer.

Path: /products/*
Target: old-site.webflow.com/products/:1

Visitors to your site will see the products from your old website while you rebuild the product pages. In the Rewrites list this rule must be above the general rule, because it is an exception and therefore needs the higher priority to take effect.

Serve a blog from a different project

Path: /blog/:slug
Target: another-project/:slug

Visitor at designer.com/blog will see the blog pages from the project Another Project .

Important considerations

CMS collections: For CMS-powered pages, the collection path must match between your rewrite rule and the origin project. For example, if your blog uses /blog/:slug in the origin project, your rewrite path should also use /blog/:slug (and not /posts/:slug for example).

Project targets: To use another Framer project as target, it must be published with a custom domain (.framer.website or from an external domain registrar), and it must have a paid plan.

Localization: When using localized projects with rewrites, ensure the locale path structure is consistent between the rewrite path and target.

Canonical URLs: Set canonical URLs in each project to point to the final domain where they'll be served.

Sitemaps: Framer automatically generates and merges sitemaps from all your rewrite sources.

Password protection: Password protection only applies to the main project. Enabling it on target projects won't protect content served through rewrites.

Pricing

Multi Sites is available with our Scale plan or included in our Enterprise plans.
View pricing

Updated