Published
9 MIN READ
Framer Multi Site: website and app on the same domain
Framer Multi Site is the hosting feature that brings several projects and external sites together under a single domain, through rewrite rules: the website at company.com, the blog at company.com/blog and the app at company.com/app. It comes with the Advanced Hosting add-on, at US$ 200 a month, or with the Enterprise plan.
If you have a website and a product, you need to decide where each one lives on the domain. Wama's portfolio has cases like this: Milhas Pix, with a SaaS platform, management system, website and landing pages, and Visor, with SaaS, system, app and blog. Before choosing the address, it helps to understand what separates the public page from the logged-in area.
The Portuguese-language guides on subdomains and subdirectories come from SEO agencies and don't say how much it costs or how to set it up. This guide looks at it from the side of whoever pays the bill: when a subdomain solves it for free, when a subfolder is worth the add-on and what usually breaks. If you sell software, the decision starts with what goes on the public website of a subscription product.
What is Framer Multi Site?
Multi Site is the settings area where the site owner creates rewrite rules. A rewrite serves content from somewhere else while keeping the address the visitor typed, unlike a redirect, which changes the URL in the browser. The destination can be another Framer project or an external site, such as the company's documentation or app.
According to Framer's help article on Multi Site, updated on September 15, 2026, the rules moved out of the domains panel and now live in Site Settings, Hosting, Multi Site. Each rule has a path, such as /blog or /blog/*, and a destination. They run in list order and only take effect after you publish the project.
The same page lists four uses: migrating from another platform gradually, splitting a large site into smaller projects, bringing a store, documentation or app into the site, and separating sections by team. One detail catches people off guard: when a page in the project and a rule use the same path, the rule wins.
Subdomain or subfolder: what does Google say?
Google says it treats both formats the same way. In May 2018, John Mueller, a Google analyst, said in a public session that subdomains and subdirectories are seen the same, according to Search Engine Journal. His recommendation was to keep together what is the same site and use a subdomain when the content really is different.
A guide from an SEO agency, published in November 2025, argues the opposite: that Google sees subdomains and subdirectories very differently. The official documentation records one concrete difference, and it's small. Google's page on site names, updated on December 10, 2025, says the name shown in search applies to domains and subdomains, and that a subdirectory doesn't get its own name.
In practice, the criterion is content. The blog, help center and campaign pages are the same site, and the recommendation to keep them together points to a subfolder. Nobody searches Google for the logged-in dashboard, so app.company.com does the job at no cost. Giving each customer their own domain inside the product is a different matter, solved in the software, not in the website.
How much does it cost to put the website and app on the same domain?
With a subdomain, nothing beyond the plan: you just point the DNS. With a subfolder, the cost is Advanced Hosting. Framer's pricing page, read on October 4, 2026 with annual billing, shows the add-on at US$ 200 a month on top of the Pro plan, at US$ 30, with a maximum of six rewrites. On Enterprise it's already included.
Path | Requirement | Monthly cost on the official page |
|---|---|---|
Subdomain pointed via DNS (app.company.com) | DNS record to the app's server | No add-on |
Subfolder with Multi Site (company.com/app) | Advanced Hosting or Enterprise | US$ 200 on top of Pro, up to 6 rewrites |
Blog or section in another project on the platform | Advanced Hosting and a paid plan on the destination project | US$ 200 plus the second project's plan |
The add-on has no trial period, according to Framer's hosting page. Besides rewrites, it unlocks custom security headers, up to 500 static files and the country blocking that uses the same add-on.
To keep your own proxy, such as Cloudflare, in front of the site, the official pages disagree about the plan. Framer's help article on proxying with Cloudflare, updated on September 30, 2026, accepts Pro with Advanced Hosting or Enterprise. The guide on integrating with an existing site, from September 15, requires Enterprise. Confirm with support before you subscribe.
In Wama's projects, the website almost always launches on the Pro plan, is transferred to the client's account and the subscription stays on the client's card. An add-on goes on that same bill, in dollars, with no markup. That's why the math has to be done beforehand, starting from what the Pro plan covers before any add-on.
What breaks when the app moves to a subfolder
The rewrite serves whatever the origin sends, without fixing anything along the way. The official Multi Site help article lists what needs adjusting before you publish the rule:
Base path. An external site that loads scripts, fonts and images from the root shows up broken at /docs. The fix is to set the base path in the origin application and publish it again.
Cookies. The rewrite passes the site's cookies to the external destination, and the destination can also set cookies. The guidance is to only rewrite to services the company trusts.
Password. Password protection applies only to the main project. Turned on only in the destination project, it doesn't cover the content served by the rule.
Measurement. The platform's analytics, A/B tests and funnels see only the main project. Pages served by rewrite need to be measured at the origin.
CMS. The collection path has to be the same in the rule and in the origin project. Review how CMS collections generate the blog pages before splitting the projects.
Canonical address. Each project declares the final domain as canonical. The origins' sitemaps are combined automatically.
The external origin also needs to respond over HTTPS. You can check all of this on the staging address, before any DNS change.
Migrating to Framer page by page
A gradual migration uses a single wildcard rule. According to Framer's guide to migrating page by page, updated on September 15, 2026, the /* rule points to the old site with the Match pages first option turned on. The platform serves the page that already exists in the new project and, when it doesn't exist yet, fetches the old version.
Create the project, publish it and connect the domain, without changing the DNS yet.
Create the /* wildcard rule pointing to the old site, with Match pages first turned on.
Create a separate rule for the home page, with the option turned off, until the new home is ready.
Publish and check everything on the staging domain.
Point the DNS to the new project.
Publish the new pages with the same paths as the old ones.
Remove the wildcard rule when the last page has migrated.
The method depends on keeping the addresses. In the WordPress to Framer migration Wama ran on a corporate website with hundreds of pages and a large blog, what went wrong included poorly organized old addresses: duplicate URLs, URLs with parameters and no pattern. In a case like that, cleanup comes before the first rule. The alternative is migrating all at once, with every redirect in place.
How to decide between a subdomain, Multi Site and a single project
The decision fits into four situations, from cheapest to most expensive:
Website and blog in the same project. The CMS generates the pages at /blog and no add-on is needed.
Product with login. The app lives on a subdomain, pointed via DNS, with no extra hosting cost.
Documentation, help center or blog in another tool that needs to appear as part of the site. This is the Multi Site case, with the US$ 200 a month bill.
Large website moving from another platform. Multi Site comes in during the migration, and the wildcard rule goes away when the last page is live.
At Wama, the logged-in area and restricted content stay out of the Framer website: they become a digital product project, built by the same studio with a different stack. The choice between subdomain and subfolder belongs to the scope, and it's worth bringing to the first conversation with whoever designs and sets up the project in Framer.
Frequently asked questions about Framer Multi Site
Does Framer Multi Site work on the Basic plan?
No. Framer's pricing page, read on October 4, 2026, lists Advanced Hosting as an add-on to the Pro plan, at US$ 200 a month, and as an included item on Enterprise. On Basic, the way to separate the website and the app is a subdomain, which only requires pointing the DNS.
Does a subdomain hurt the website's SEO?
Google says it treats subdomains and subdirectories the same way, in a statement by John Mueller from May 2018. His guidance is to keep at the same address whatever is part of the same site. For a logged-in app, which stays out of search, a subdomain solves it with no cost and no loss.
How many rewrites does Advanced Hosting allow?
Up to six, according to Framer's pricing page. The rules run in the order they appear in the Multi Site list, and a wildcard rule, such as /blog/*, covers every page under that path. If you need more destinations, the Enterprise plan has limits on request.
Does Framer Analytics measure pages served by rewrite?
No. The official help says analytics, A/B tests and funnels track only the main project, without including visits or events from pages served by rewrite. To get the full journey, measurement also needs to exist at the origin, whether that's another project, the documentation or the app.
Do I need Multi Site to have a blog at /blog?
No, when the blog lives in the same project as the website: the Framer CMS publishes the pages at /blog with no add-on. Multi Site only comes in if the blog is in another project or another tool and needs to appear on the same domain, as part of the main site.
If your company has a Framer website and a product, and needs to decide where each one lives before building, talk to Wama about your project.
