Framer Redirects: How to Protect SEO During a Migration

Author: We Optimizz - Framer SEO and migration specialists

Last updated: May 1, 2026

TL;DR: Framer Redirects for SEO Migrations

Framer has a built-in redirect system accessed via Site Settings → Redirects. Framer handles these as permanent redirects — suitable for SEO migrations. You can redirect individual pages or use wildcard patterns for bulk migrations. Redirects require a Framer plan that includes the feature — if you do not see Site Settings → Redirects, check your plan or handle redirects via your hosting, CDN or edge redirect layer. For domain-level redirects, use the old domain's host, CDN or edge redirect layer — Framer only handles sub-path redirects within your current domain. Map URLs before building, test every redirect before launch, and monitor Google Search Console for 404s in the first 90 days after going live.

---

If your URLs change during a Framer migration, redirects are not optional.

A permanent redirect tells search engines and users that an old URL has moved to a new location. Without it, old URLs can return 404 responses, backlinks can point to dead pages and Google may drop previously indexed pages over time.

Framer includes a built-in redirect system for most path-level migrations. This guide shows you how Framer redirects work, when to use one-to-one redirects or wildcards, where Framer's redirect system has limits, and how to test your migration before launch.

Redirects, metadata and indexation checks are usually the three biggest technical controls in a Framer migration. This post focuses on the redirect layer.

Planning a migration to Framer? Get a free Framer migration scan. We check your current URLs, identify high-risk pages, flag redirect gaps and show which pages need one-to-one redirects before launch. Get my Framer migration scan

---

Why Redirects Matter for Framer SEO Migrations

Short answer: When a URL changes without a redirect, Google has no clear URL-level signal that the old page and new page are the same destination. The new URL may need to earn visibility again, while the old URL can drop from the index.

Ranking URLs build signals over time through backlinks, internal links, relevance and repeated crawling. Those signals live at the URL level.

When you migrate to Framer and change URLs without redirects:

• Google crawls the old URL, gets a 404 response and may eventually drop it from the index

• The new URL has no connection to the old URL's backlinks or history

• Any site linking to your old URL now points to a dead page

• Users clicking old bookmarks or shared links land on a 404 error page

If redirects are missing or mapped poorly, rankings can drop quickly and recovery can take weeks or months. That is why redirect setup is not optional for any migration that involves URL changes.

Correctly implemented permanent redirects help Google transfer signals from the old URL to the new URL, especially when the destination is a close content match. They do not guarantee that rankings or traffic stay identical after a migration.

For broader context on how redirects fit into a full Framer SEO strategy, read our Framer SEO guide.

---

How Framer Redirects Work

Short answer: Framer's redirect system lives in Site Settings → Redirects. Framer redirects are permanent. Depending on implementation, permanent redirects may be served as 301 or 308 status codes; both indicate a permanent move and are treated similarly by search engines for SEO purposes. You enter the old path and the new path, publish your site, and Framer handles the rest.

In Framer, a redirect rule has two parts: the old path visitors request and the new path they should land on.

In practice, you do not need to choose a redirect type in Framer. Treat Framer redirects as permanent redirects and verify the final status code during testing.

Many SEOs refer to these as "301 redirects," but in Framer the safer term is permanent redirects because the final status code can be 301 or 308 depending on implementation.

To set up a redirect in Framer:

1. Open your Framer project

2. Go to Site Settings → Redirects

3. Click Add Redirect

4. Enter the old path (e.g. /old-page) in the From field

5. Enter the new path (e.g. /new-page) in the To field

6. Reorder rules by dragging if priority matters

7. Publish or update your site to apply the changes

Important: if you change a sub-path from the canvas or CMS, it will not automatically update in your redirect settings. Update the old URL manually or create a new redirect to account for the changes.

Which Framer plans include redirects?

Redirects require a Framer plan that includes the Redirects feature. If you do not see Site Settings → Redirects in your project, your current plan may not include it. Check Framer's current pricing and plan features before planning a migration — plan names and feature availability can change.

If you cannot access redirects natively in Framer, handle them outside Framer through your old host, CDN or edge redirect layer, such as Cloudflare Redirect Rules.

Domain-level redirects

You can only redirect sub-paths within your current domain. To redirect an entire domain — for example, www.abc.com to www.xyz.com — use your hosting provider for the old domain to set up domain-level redirects. Once complete, connect the new domain in Framer and handle sub-path redirects as needed.

---

One-to-One Framer Redirects: One Old URL to One New URL

For individual page migrations or URL changes, simple one-to-one redirects are straightforward in Framer.

Examples of when you need simple redirects:

• You renamed a service page: /services → /web-design

• You changed a blog post slug: /post/old-title → /post/new-title

• You removed a landing page and want to redirect traffic: /promo-2023 → /

• You restructured navigation: /about-us → /about

For each of these, you add one redirect rule in Framer with the exact old path and the exact new path.

What to watch for:

• Paths in Framer are case-sensitive in some implementations — test with the exact casing of your old URL

• Always include the leading slash: /old-page not old-page

• Do not redirect to a page that itself redirects — that creates a redirect chain which slows crawling and makes debugging harder

---

Framer Wildcard Redirects: Migrating Entire Sections at Once

For migrations involving dozens or hundreds of pages — blog posts, case studies, product pages — setting up individual redirects is impractical. Framer's wildcard system handles bulk migrations with a single rule.

Short answer: Framer supports wildcard redirects and capture groups for folder-level migrations. Test the exact syntax in your Framer Redirects panel before relying on it for a full migration, especially when multiple path segments are involved.

Framer supports the following wildcards: use  to match the remaining path after a folder prefix. Example: /blog/ matches /blog/hello-world and /blog/2022/07/18/hello-world.

Common wildcard patterns

Redirect entire blog folder:

Old URL structure: /news/post-title New URL structure: /blog/post-title

Rule:

• From: /news/*

• To: /blog/:1

This redirects every URL under /news/ to the same slug under /blog/. Use /news/* → /blog/:1 only after testing with at least five real URLs from your old site to confirm the pattern behaves as expected.

Migrate date-formatted WordPress URLs:

Old URL structure: /2024/03/15/post-title New URL structure: /blog/post-title

This pattern is risky with a simple wildcard rule because the date folders need to be removed while the final slug is preserved. Test your exact Framer redirect syntax first. If it cannot produce the desired destination, use individual redirects or handle the rewrite at your CDN/edge layer.

Redirect a removed section to the closest parent page:

Old URL structure: /old-section/* New URL structure: /resources

Rule:

• From: /old-section/*

• To: /resources

Use this only when the parent page is a relevant replacement for the removed section. If there is no close match, return a clean 404 instead of sending unrelated URLs to the homepage.

Preserve slug across folder restructure:

Old URL structure: /resources/tutorials/post-title New URL structure: /learn/post-title

Rule:

• From: /resources/tutorials/*

• To: /learn/:1

Redirect rule priority

Reorder rules by dragging and dropping to set priority. More specific rules should sit above broader wildcard rules. If a specific redirect and a wildcard rule both match the same URL, the rule higher in the list takes priority.

---

Bulk Redirects: The Redirect Sync Plugin

For large migrations with many individual redirects, use Framer's Redirect Sync Plugin instead of entering redirects one by one.

Framer introduced the redirect APIs powering this workflow in Plugins 3.2. The plugin exports all redirects from your site into a single CSV file — useful for bulk editing and SEO audits.

Use it to prepare a redirect map in CSV and import redirects in bulk.

For large migrations with 100+ URL changes, use this workflow:

1. Crawl the old site with Screaming Frog or Ahrefs to get a full URL list

2. Map old URLs to new URLs in a spreadsheet

3. Export the mapping as CSV

4. Import via the Redirect Sync Plugin

5. Test a sample of redirects before publishing

6. Publish and monitor

Redirect limit

Framer currently allows up to 2,500 redirects per project. That is enough for most small and mid-sized migrations, but large content sites should check the redirect count before committing to Framer as the only redirect layer.

---

The Framer Migration Redirect Workflow: Step by Step

Before you build

1. Crawl the current site — use Screaming Frog, Ahrefs or Google Search Console to export all indexed URLs

2. Identify which URLs will change — compare current URL structure with planned Framer URL structure

3. Build a redirect map — a spreadsheet with Old URL | New URL | Status (mapped / needs decision)

4. Keep URLs the same where possible — every URL you can preserve is one redirect you do not need to create and test

5. Check your redirect count — Framer currently allows up to 2,500 redirects per project; large sites should verify their map stays within this limit

Redirect map template

Build this spreadsheet before adding any redirects in Framer:

Old URL	New URL	Type	Priority	Status	Notes
/old-service	/web-design	Permanent	High	Ready	Backlinked page
/blog/old-post	/post/new-post	Permanent	Medium	Needs testing	CMS slug changed
/old-section/*	/new-section/:1	Wildcard	High	Test first	Folder migration
/promo-2023	/case-studies	Permanent	Low	Only if relevant	Old campaign — redirect to closest match, not homepage

Use this map as your source of truth during the build. Enter redirects into Framer directly from the map — do not work from memory.

Set priority based on SEO risk: High for URLs with backlinks, rankings, traffic or conversions; Medium for indexed pages with internal links but little traffic; Low for expired campaigns, thin pages or URLs with no traffic or backlinks.

During the build

5. Set up redirects before launch — do not wait until after go-live to create redirects

6. Check that new Framer URLs match your redirect map — CMS slugs in Framer must match what you entered as the destination in your redirect rules

7. Avoid redirect chains — if Page A redirects to Page B which redirects to Page C, collapse it to A → C

At launch

8. Test every redirect — open a browser, visit old URLs and confirm they land on the correct new pages

9. Submit updated sitemap to Google Search Console — go to Search Console → Sitemaps → submit your Framer sitemap URL

10. Request indexing for your most important new pages — use URL Inspection in Search Console to request crawling of key pages

11. Check canonical tags on new pages — they should point to the final new URLs, not old URLs or staging URLs

12. Confirm the Framer sitemap only contains final 200-status URLs — submit it to Search Console after launch

After launch

13. Monitor 404 errors in Search Console — go to Coverage or Pages → check for Not Found errors

14. Monitor rankings for key pages — use Ahrefs, Semrush or Search Console to track position changes on your most important pages

15. Check for redirect errors — Search Console flags redirect issues separately from 404s

16. Monitor for 90 days — most migration-related ranking fluctuations stabilise within 60–90 days

---

Common Framer Redirect Mistakes

Mistake 1: Setting up redirects after launch The most damaging timing error. If Google crawls old URLs before redirects are in place, it can see 404 responses and start treating those pages as removed. Set up redirects before you connect your domain or launch the new URL structure.

Mistake 2: Not crawling the old site first You cannot map redirects accurately if you do not know all the URLs that existed on the old site. Crawl before you build, not after.

Mistake 3: Redirect chains A chain occurs when URL A redirects to URL B, which redirects to URL C. Each extra hop slows crawling, increases failure risk and makes the migration harder to debug. Collapse chains so every old URL redirects directly to the final destination.

Mistake 4: Redirecting everything to the homepage Redirecting changed URLs to the homepage rather than the most relevant equivalent page wastes link equity and gives users a poor experience. Match old URLs to their closest equivalent new page wherever possible.

Mistake 5: Forgetting CMS pages Blog posts, case studies and portfolio entries have individual URLs. If your CMS URL structure changes in Framer — for example, from /post/title to /blog/title — every CMS page needs either a matching URL or a wildcard redirect covering the whole folder.

Mistake 6: Not updating internal links Redirects handle external links and Google's existing index. But internal links pointing to old URLs still create an extra hop even if a redirect exists. After migration, update internal links to point directly to the new URLs.

Mistake 7: Assuming your Framer plan includes redirects Not all Framer plans include the redirect feature. If you do not see Site Settings → Redirects, check your current plan. Plan the upgrade cost into your migration budget if needed, or handle redirects via your hosting, CDN or edge redirect layer such as Cloudflare Redirect Rules.

What Not to Redirect During a Framer Migration

Not every deleted or changed page needs a redirect. Redirect only when the destination is a close match for the original page's intent and content.

If there is no relevant replacement for an old URL, return a clean 404 rather than forcing a redirect to an irrelevant page. Avoid sending unrelated old URLs to the homepage — it creates a poor user experience and sends a weak relevance signal to Google.

Use this as a decision guide:

Old page situation	Correct action
Page moved to new URL	Redirect old URL → new URL
Page merged into another page	Redirect old URL → merged page
Page deleted, no equivalent	Return 404 or redirect to closest parent category
Entire section removed	Redirect to category page if relevant, otherwise 404
Temporary campaign page expired	Let it 404 — no long-term SEO value in redirecting

Do not blindly redirect old noindexed, blocked or low-quality URLs unless they have backlinks, traffic or a clear replacement. Prioritize URLs with rankings, backlinks, internal links or business value.

---

How to Test Framer Redirects Before Launch

Setting up redirects is not enough — you need to verify each one works correctly before going live.

Test redirects with:

• Browser checks for your most important URLs — visit the old URL and confirm it lands on the correct new page in one hop

• Screaming Frog List Mode — import your full redirect map and run a crawl to check status codes in bulk

• HTTP status checker — tools like httpstatus.io let you check redirect chains and final destinations

• Google Search Console after launch — monitor Coverage, Pages and the Redirect errors report for issues

For each old URL, confirm:

• It returns one permanent redirect — not a chain of multiple hops

• It lands on the final destination in a single redirect

• The destination page returns a 200 status

• The destination content matches the original page intent

Redirect test rule: A migration redirect passes when the old URL returns one permanent redirect, the final destination returns 200, the destination content matches the old intent, and the redirect chain has no extra hops.

Framer Redirects vs Webflow and WordPress

	Framer	Webflow	WordPress
Built-in redirect management	Yes — Site Settings	Yes — project settings	Usually via plugin or server config
Redirect type	Permanent redirects	301 redirects	Plugin/server-dependent
Wildcard/bulk workflows	Wildcards + Redirect Sync CSV import	Depends on setup	Plugin/server-dependent
Plan/hosting dependency	Requires a plan with redirects	Requires paid hosting	Depends on host and plugin
Domain-level redirects	Old host/CDN/edge layer	Old host/CDN/edge layer	Host/CDN/server config

For Framer's redirect system, the main constraint is the plan requirement and the lack of native support for complex regex-based patterns (like extracting a slug from a date-formatted WordPress URL). For most business migrations, the built-in wildcard system is sufficient.

---

When to Hire a Framer Migration Specialist

Most business owners can handle simple redirects following this guide. For larger or more complex migrations, specialist support protects your rankings.

Consider bringing in support when:

• You are migrating a site with 100+ pages and need a full URL map built before the build starts

• Your old site has date-formatted or query-based URLs that cannot be replicated in Framer

• You need to validate that every redirect is correct before go-live, not after

• You want to monitor ranking performance and respond to issues in the first 90 days

• You want redirects as part of a broader SEO migration strategy, not just a technical checklist

At We Optimizz, we handle Framer migrations with SEO preserved from day one — URL mapping, redirect setup, metadata migration, structured data and post-launch monitoring. With 894 websites built across 35+ countries, we know where migrations go wrong and how to prevent it.

Read our complete Framer website design and SEO guide to see how redirects fit into a full migration strategy.

Redirect mistakes get more expensive after launch. Book a migration call and we will review your URL map, redirect rules, sitemap and launch checklist before Google crawls the new structure. Book my Framer migration call

---

FAQ: Framer Redirects for SEO Migrations

Does Framer support 301 or permanent redirects?

Yes. Framer supports permanent redirects natively via Site Settings → Redirects. Framer handles these as permanent redirects, which is the correct type for SEO migrations. Note that Framer may use 308 permanent redirects in some configurations — both 301 and 308 are permanent types treated similarly by search engines. Redirects require a plan that includes the feature.

Which Framer plan includes redirects?

Redirects require a Framer plan that includes the feature. If you do not see Site Settings → Redirects in your project, your current plan may not include it. Check Framer's current pricing before planning a migration. If redirects are not available on your plan, use your old host, CDN or edge redirect layer, such as Cloudflare Redirect Rules.

Can I redirect an entire folder in Framer?

Yes. Use Framer's wildcard redirect system. The  wildcard matches the remaining path string after the folder prefix, and capture groups (:1, :2) let you reference matched portions in the new URL. For example, /old-blog/ → /blog/:1 redirects every URL under /old-blog/ to the matching path under /blog/.

How do I redirect my old domain to Framer?

Domain-level redirects — redirecting one full domain to another — are handled by your hosting provider for the old domain, not by Framer. Set up the domain redirect at the hosting level, then connect your new domain in Framer and handle any sub-path redirects from there.

Do Framer redirects pass link equity?

Permanent redirects help Google transfer signals from the old URL to the new URL, especially when the new page is the closest equivalent. They are the correct method for permanent URL changes, but they do not guarantee that all rankings or traffic will be preserved.

When should I set up redirects — before or after launching in Framer?

Before launch. Set up all redirects before you connect your domain and go live. If Google crawls old URLs before redirects are in place, it can discover 404 responses and may start dropping those URLs from the index.

How do I handle hundreds of redirects in Framer?

Use Framer's Redirect Sync Plugin to prepare a redirect map in CSV and import redirects in bulk. Framer currently allows up to 2,500 redirects per project, so large migrations should check the redirect count before relying on Framer as the only redirect layer. For very large sites, also handle redirects at your CDN or edge layer.

What happens if I do not set up redirects when migrating to Framer?

Every URL that changes without a redirect can return a 404 response. Google may drop those pages from its index over time, backlinks pointing to old URLs lose their connection to the new pages, and users who click old links land on error pages.