How to use Multi Sites with rewrites
Multi Sites allows you to combine multiple websites under a single domain using rewrite rules. Manage rewrites directly in Framer instead of setting up Cloudflare Workers, Vercel rewrites, or custom reverse proxy configurations.
What are rewrites?
Rewrites act as a URL proxy, allowing you to map paths on your domain to content from other sources. Unlike redirects that change the URL in the browser, rewrites serve content from another location while keeping the original URL visible to visitors.
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
Multi Sites is perfect for…
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.
Faster build times – Smaller, focused projects build faster than one large monolithic site.
How to set up rewrite rules
On the dashboard select your domain in the sidebar and navigate to the Multi Site tab.
Adding a rewrite rule
Click the + icon to add a rule
Choose the rewrite type:
Project: Route to another Framer project
External: Route to an external website
Enter the Path where you want the content to appear (e.g.,
/blog
or/blog/*
)Enter the Target:
For projects: Select your Framer project and specify the path
For external: Enter the full URL of the external site
Click Add to save the rule
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
Important: Changes on Rewrites take effect after you published your site.
Examples
Serve a blog from a different project
Path: /blog/*
Target: blog-project.framer.website/*
This serves your blog project at designer.com/blog
while keeping your main site separate.
Host external documentation
Path: /docs/*
Target: https://docs.yoursite.com/*
This displays your externally-hosted documentation at designer.com/docs
.
Combine multiple sections
You can create multiple rules to combine different sources:
/
→ Main Framer project/blog/*
→ Blog project/help/*
→ External help center/app/*
→ Web application
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
.
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: You can password-protect individual paths by pointing them to password-protected projects.
Pricing
Multi Sites is available as an add-on with our Scale plan or included in our Enterprise plans.
View pricing