Keep the visitor's destination in the plan
Before replacing a website with Framer, list the old URLs people already use and the pages that should replace them. A domain connection alone does not decide where a bookmarked service page should land. This guide addresses URL routing; email records and domain access need their own migration checks.
We reviewed official Framer and Google documentation on September 14, 2026. The downloadable map and acceptance checks are our planning method, not results from a live client migration. Search visibility can change during a move; no redirect checklist guarantees rankings.
Decide what kind of move each URL needs
| Situation | Routing decision | What to record |
|---|---|---|
| Same domain and same path | Keep the URL and verify the replacement page. | Expected page title and visitor action. |
| Same domain; changed path | Plan a redirect to the equivalent new page. | Old path and final new path. |
| Different domain | Arrange domain-level routing with the old hosting provider. | Who controls the old host and full destination URL. |
| Content removed with no replacement | Plan an appropriate missing-page response. | Removal reason and suggested navigation. |
| Several pages genuinely combined | Map each old URL to the relevant consolidated page. | Why that destination answers the old intent. |
Build the map before entering rules
Use the worksheet as a manual planning and verification log; it is not a Framer import file. Start with URLs from your existing sitemap and navigation, then add URLs from campaigns, QR codes, client proposals, and saved links. Ask the owner which pages would cause the most disruption if broken.
For each row, write the old page's purpose before choosing its replacement. For example, an old pricing page should lead to current pricing when it exists. If the new design no longer explains pricing, create or revise that content before approving the row. Record an owner and unresolved decision instead of guessing.
Enter Framer rules and publish
Framer's current help article places redirects in Site Settings → Hosting → Redirects. Enter the old and new paths, order rules by priority, and publish or update the site to apply them. The article's FAQ uses a shorter menu path; use the Hosting section described in its main instructions.
Framer documents wildcard and named-segment matching. Start with explicit page mappings when the site is small. For a larger pattern, test representative URLs and exceptions before adopting it. Framer says canvas or CMS path changes do not automatically update redirect settings, so revisit the map after a slug edit.
Framer describes these rules as sub-path redirects within the current domain. For a whole-domain move, its documentation directs you to the old hosting provider for domain-level redirects. Confirm access and responsibility for that service before scheduling the switch.
Test the published old link, then the page it reaches
Open each old URL in a fresh browser session after publishing. Record the actual final URL and whether the page answers the old page's purpose. Follow the main visitor action too: a correctly routed consultation page still fails its job if its booking link is broken.
For a technical check, inspect the redirect response and destination response in browser developer tools or an HTTP checker. A working page display alone does not tell you the redirect status. Record observations in the worksheet; blank status cells mean unverified. Test a deliberately nonexistent URL separately so that an unrelated page is not silently presented as a successful destination.
Google advises routing directly to final destinations and avoiding mass redirects to an irrelevant homepage. Removed pages without suitable replacements should return 404 or 410. Update internal links, canonical references, and the sitemap to the new URLs; remove temporary indexing blocks only when the intended public pages are ready.
Use a launch gate and a follow-up owner
Our example rows are invented route patterns to show how to fill in the worksheet. Replace them with your own inventory. A green homepage check is only one row; it does not validate links visitors enter directly from search or old messages.
- Before launch: every critical old URL has an approved destination or an intentional removal decision, and the old-domain routing owner is identified.
- At launch: record actual destinations and response codes, check page purpose, and test the main action on desktop and mobile.
- After launch: assign someone to investigate missing-page reports and Search Console indexing issues; keep the map as the record of intended behavior.
Sources & verification
Product details and prices can change. Check the linked provider before buying.
- Framer: how to set up redirects Accessed 2026-09-14
- Google Search Central: site moves with URL changes Accessed 2026-09-14
- Google Search Central: redirects and Google Search Accessed 2026-09-14
Sources link directly to providers. Product buttons may use separately labeled affiliate links. Read our disclosure.