Yes, migration is safe — if you treat it as a URL project first and a design project second. Rankings live on URLs, not on WordPress. Inventory every live URL, map each one to a Framer destination with a 301, keep titles, canonicals and schema identical at launch, then watch Search Console for 30 days.
TL;DR
Traffic loss comes from broken URLs and rewritten metadata, not from Framer. Both are avoidable.
Build the URL inventory from four sources — crawl, sitemaps, database, Search Console — because no single source is complete.
Every old URL gets exactly one 301 to the closest topical match. No blanket redirect to the homepage.
Freeze titles, descriptions, canonicals and schema at launch. Change them 30 days later so you can attribute movement.
Keep WordPress if you run WooCommerce, membership gating, or a multi-author editorial workflow. Framer is the wrong tool for those.
Rankings live on URLs, not on WordPress
Google does not rank your CMS. It ranks URLs that have content, internal links, external links and crawl history attached to them. Change the platform underneath a URL and keep the URL, the content and the metadata intact, and there is nothing for the ranking to fall off.
Every migration disaster I have looked at came from one of three self-inflicted causes:
URLs changed and nobody wrote redirects for the long tail.
Metadata got “improved” during the rebuild, so a page that ranked for a phrase in its title no longer has that phrase.
Content got trimmed to fit a prettier layout, and the page that answered eight questions now answers three.
The platform change itself is usually the part that helps. Framer outputs static pages served from a CDN, so the typical WordPress site carrying six plugins’ worth of render-blocking CSS tends to move in the right direction on Core Web Vitals — the targets being LCP under 2.5s, INP under 200ms and CLS under 0.1. That is a tailwind, not a rescue. It will not save a site that lost 400 URLs.
Step 1: build a URL inventory nothing escapes
Use four sources. One source is never enough.
Crawl the live site
Run a full crawl with Screaming Frog or similar. Export every HTML URL returning 200, along with its title, meta description, H1, canonical, indexability status and word count. Set the crawl to follow all internal links to unlimited depth and include subdomains if you have them.
A crawl only finds pages that something links to. That is its blind spot.
Read the sitemaps and the database
Pull /sitemap_index.xml and every child sitemap: posts, pages, categories, tags, authors, custom post types. Then export the published post list straight from WordPress — the WXR export or a wp post list --post_status=publish --format=csv from WP-CLI. This is where orphan pages surface: the 2019 landing page that still ranks, still earns clicks, and has not been linked from the nav in four years.
Export Search Console
Search Console is the only source that tells you which URLs actually matter. Go to Performance → Search results → switch to the Pages tab → set the date range to the full 16 months → Export → Google Sheets or CSV.
Two rules I apply to that export:
Any URL with one or more impressions in the last 12 months must appear in the redirect map. Not “should”. Must.
Then open Links → Top linked pages → export. Those URLs carry external equity. Breaking one of them costs more than breaking fifty pages nobody links to.
Merge into one sheet
One row per normalized URL. Normalize by lowercasing, stripping the trailing slash and dropping tracking parameters, otherwise you will produce duplicate rows and miss real pages. Columns I use: old URL, discovery source, 12-month clicks, 12-month impressions, referring domains, current title, current meta description, current canonical, template type, new URL, redirect type, verified status, verified date.
For a 60-page business site this is a two-hour job. For a 3,000-post publisher it is a day. Either way it is the single part of the project that pays back most.
Step 2: build the redirect map 1:1
Framer has native redirect settings in site settings, so the map lives inside the project rather than in a plugin or an .htaccess file you will lose access to.
The rules:
One destination per old URL. Redirecting the whole long tail to the homepage is the most common cause of a migration crash. Google treats a mass redirect of unrelated URLs to one page as a soft 404 and drops them.
301, not 302. A 302 tells Google to keep the old URL indexed.
One hop. If the old site already had redirect chains, flatten them.
/a→/cdirectly, not/a→/b→/c.Keep the slug wherever you can. Change slugs only when there is a ranking reason, and never in the same release as the platform change. If you change both, you cannot tell which one caused a drop.
What to do with each WordPress URL pattern
WordPress pattern | Example | Handling in Framer |
|---|---|---|
Post/page permalinks |
| Rebuild at the identical path. No redirect needed. |
Dated permalinks |
| Recreate as |
Plain IDs |
| Map individually from the database export. Query-string redirects are unreliable — check each. |
Category archives |
| If it earns clicks, build the equivalent page and 301 to it. If not, 301 to the blog index. |
Tag archives |
| Almost always thin. 301 the few with clicks to the closest article or category; send the rest to the blog index. |
Author archives |
| 301 to an About or team page if one exists, otherwise the blog index. |
Pagination |
| 301 to |
Feeds |
| Verify before you promise anything. If a newsletter or aggregator consumes the feed, plan a replacement before cutover, not after. |
Attachment pages |
| 301 to the parent post. These should have been disabled years ago. |
Uploads |
| Image URLs change. Accept the image-search loss or keep the old files reachable. |
Search and admin |
| Ignore. They were never indexable. |
The Framer CMS slug trap
Framer CMS generates slugs from the first string field in a collection. If you import 400 posts and the first field happens to be the excerpt or the author name, every slug will be wrong and every redirect in your map will point at a 404. Set the field order before the import, not after. I check five slugs against the map by hand before importing the remaining 395.
Step 3: metadata, canonical and schema parity
Parity means identical, not similar.
Titles and descriptions
Copy the existing title tags and meta descriptions character for character into Framer’s page settings. Yes, including the ones you think are bad. If a page ranks second for a phrase that appears in its title, rewriting that title at launch is a change you cannot untangle from the platform change. Rewrite them in week five, one batch at a time.
Canonicals
WordPress SEO plugins set canonicals you may not know about — cross-domain canonicals from a syndication tool, paginated canonicals pointing at page one, or a canonical still aimed at an old domain from a previous move. Export the canonical column from your crawl and reconcile it. In Framer, most pages want a self-referencing canonical.
Also check your noindex parity in both directions: the pages that should stay out of the index, and the Framer staging domain, which is a separate domain and should not be indexed while you build.
Schema
Framer has no plugin ecosystem for SEO. Schema is added as custom code — site-wide markup in site settings, page-specific markup in the individual page’s settings. Practically that means:
Site settings:
OrganizationandWebSite.Blog template:
ArticleorBlogPostingwith CMS fields bound into it.Service pages:
ServiceorLocalBusinesswhere relevant.Any page with an FAQ block:
FAQPage.Anywhere you had breadcrumbs:
BreadcrumbList.
Run every template through the Rich Results Test before the cutover, not after. A rich result you had on WordPress and lose in Framer is a visible CTR loss even when the position is unchanged.
Step 4: staged versus big-bang cutover
Big-bang | Staged | |
|---|---|---|
How it works | Build the whole site on the Framer staging domain, verify, then repoint DNS and publish all redirects at once | Move sections in phases using Framer Advanced Hosting’s match-pages-first, which serves any page that exists in Framer and passes everything else through to the existing site |
Best for | Sites under roughly 100 URLs, or any site where the old stack is a liability | Large sites, publishers, sites with a section that must stay on WordPress |
Main risk | Every mistake goes live at the same moment | Two systems live at once: duplicate analytics, split internal links, drifting nav |
Rollback | Revert DNS. Fast, but the redirect map is already live | Remove the Framer page and traffic returns to WordPress instantly |
What bites people | Redirects published after DNS instead of with it | Internal links on the WordPress side still pointing at old paths for weeks |
I default to big-bang under 100 URLs, because the coordination cost of a staged move exceeds the risk it removes. Above that, or whenever part of the site is staying on WordPress permanently, staged wins.
Whichever you pick: publish the redirects in the same release as the DNS change. Not an hour later.
Step 5: the 30-day monitoring window
Day 0. Verify the domain property in Search Console if it is not already a domain-level property. Submit the new sitemap. Keep the old sitemap submitted too — it makes Google recrawl the old URLs quickly and see the 301s.
Day 1–3. Crawl your own redirect map in list mode with “follow redirects” on. Every row must resolve as a single 301 to a 200. Any 404, any 302, any chain is a defect to fix that day. This is the step most agencies skip, and it is the one that catches the 30 URLs somebody typo’d.
Week 1. Watch the Pages report in Search Console. “Not found (404)” climbing is expected for a few days as Google recrawls; “Page with redirect” climbing is the signal you want. Compare the 404 list against your map — anything in the 404 list that is not in your map is a URL your inventory missed.
Week 2. Compare clicks page by page, week over week. Expect noise. A single page moving two positions is not a trend.
Week 4. For anything still down where the redirect is clean and the content is intact, look at internal links. A rebuilt navigation that dropped six footer links is the usual cause of a page quietly losing weight.
Keep the WordPress install running but not publicly reachable for 90 days. When someone asks “did that page used to say X?”, you want to be able to answer.
When this is the wrong approach
I turn down migrations. Framer is the wrong tool when:
You run WooCommerce. Framer does not support it. Third-party embeds such as Shopify buy buttons cover a handful of products; a catalog with hundreds of SKUs, variants, tax rules and coupon logic does not belong in Framer.
You have membership or gated content. Framer has no native membership or gating and no server-side logic. Courses, paywalls, logged-in dashboards — keep them where they are.
You have a multi-author editorial operation. Framer CMS is comfortable for one to three people publishing. Contributor and editor roles, revision history, embargoed scheduling and an editorial calendar are WordPress strengths, and losing them is a real operational cost, not a cosmetic one.
Content volume is the product. Five thousand posts is a WordPress job.
Your site depends on plugin logic — booking engines, LMS, multi-step forms with conditional server-side processing.
The hybrid is often the right answer: marketing site on Framer, shop or member area left on WordPress, joined with match-pages-first. Nobody loses.
What a migration costs
Flat $1,200 covers the first page plus all the shared work — design system, CMS structure, redirect map, schema, analytics. After that it is $250 per page for pages 2–10, $150 for 11–25, and $45 for 26 and beyond. Typical outcomes: 5 pages lands around $2,400–3,000, 10 pages $3,800–4,700, 25 pages $6,300–7,800, 100 pages $10,000–12,500. Full detail sits on /pricing.
Blog posts are CMS items, not pages. Five hundred posts running through one template do not cost 500 × $45; they cost the template plus the import.
If you want to test the working relationship before committing, the hourly trial is $50/hour with a 5-hour minimum, credited against the project if you continue.
FAQ
Will I lose rankings moving from WordPress to Framer?
Not if every indexed URL gets a 301 to a matching page and the metadata stays identical. Expect two to four weeks of fluctuation while Google recrawls and consolidates the redirects. Losses that persist past 30 days almost always trace back to a missing redirect, a rewritten title tag, or content cut during the redesign — not the platform.
Do I have to keep the same URLs?
Keep them wherever you reasonably can. Identical URLs need no redirect at all, which removes an entire category of risk. If your structure genuinely needs fixing — dated permalinks, for instance — change it, redirect one-to-one, and do it in the same release. Never change slugs a second time three weeks later while you are still reading the recovery curve.
What happens to my blog categories and tag archives?
Categories become a CMS field in Framer, and any archive that earns real clicks gets rebuilt as a page. Tag archives are usually thin, so check Search Console first: redirect the handful with impressions to the closest article or category, and send the rest to the blog index. Paginated URLs like /blog/page/3/ redirect to /blog.
Is Framer actually better for SEO than WordPress?
Better on delivery, weaker on tooling. Framer outputs static pages from a CDN, which usually improves LCP without any tuning. But there is no SEO plugin ecosystem, so schema, hreflang and anything non-standard is hand-written custom code. If your SEO depends on plugin-driven automation across thousands of URLs, WordPress remains the stronger choice.
Should I redesign at the same time as migrating?
Design, yes. Content, carefully. Rebuilding the visual layer while keeping copy, headings, internal links and metadata intact is low risk. Cutting page length, merging pages or rewriting titles at the same time is how sites lose traffic and lose the ability to diagnose why. Migrate first, measure for 30 days, then change content deliberately.
---
Related reading: the WordPress to Framer migration service page covers deliverables and timelines, website SEO covers what happens after the move, and website speed optimization covers the Core Web Vitals side in detail.
Send me your URL and I will send back a crawl summary, a redirect risk list and a fixed quote within 48 hours, free.
Framerfry
Founder-led Framer studio by Zakir Ullah — Official Framer Expert & Creator. Design, build, migrate, maintain and rank — one person, end to end.
© 2026 Framerfry. Built by an Official Framer Expert.
