Skewcheck Guides WordPress to Webflow or Framer
Moving off WordPress to Webflow or Framer: the redirects to add
Updated · By SwynQ Labs Private Limited
WordPress sites usually move to Webflow or Framer with new paths. Posts, categories, tags, authors, feeds and uploaded files all had their own addresses. This page is the WordPress side of that map: which paths Settings → Permalinks created, and the rule shape each platform documents. Import steps stay on the Webflow and Framer guides.
1. Which permalink structure you had
On the old site, Settings → Permalinks is the source. WordPress's permalinks documentation (updated 28 June 2025) lists six choices:
- Plain:
/?p=123, where123is the post or page ID. WordPress calls this the default. - Day and name: a year, month and day, then the post slug. The docs show both
/2012/12/30/post-nameand a form with a trailing slash. - Month and name: a year and month, then the post slug.
- Numeric: the post ID from the database. The docs do not print the path. Copy whatever the Permalinks screen shows; do not guess
/archives/123. - Post name: the slug only.
- Custom: structure tags such as
%year%,%monthnum%,%day%,%postname%,%post_id%,%category%and%author%. The docs say a custom structure should end in%post_id%or%postname%.
Category and tag archives use a base. The default bases are category and tag, so the URLs look like /category/news/ and /tag/launch/. You can rename the bases on the same screen. WordPress says you cannot remove them. %author% puts the author into post URLs. Author archives sit under their own base, /author/ by default.
2. The old URL list
Export the paths that actually got visits before you write wildcards. How to find old URLs after a migration covers Search Console, web archives, the old sitemap, analytics and logs. Put the result in the redirect map template.
Or scan your old URLs free. The scan lists addresses public web archives saved and checks what each one returns on the new site.
3. Pattern table
Use a wildcard only when the slug did not change and only the folder did. Webflow's help writes the capture as (.*) in the old path and %1 in the target. Framer's help writes * for a path segment and :1 (or :slug) in the new path. Renamed posts need one row each. Where a cell is not in the platform docs, the table says to check it in the project.
| WordPress path | Webflow old path → target | Framer from → to | Check before you rely on it |
|---|---|---|---|
Day and name, slug unchanged, moving under /insights/ | /2012/12/30/(.*) → /insights/%1 | /2012/12/30/* → /insights/:1 | Only if every post in that day folder kept its slug. Framer's help shows /blog/* matching a dated URL with slashes after blog, so * is the rest of the path, not one segment. :slug is the one-segment form. |
| Month and name, slug unchanged | /2012/12/(.*) → /insights/%1 | /2012/12/* → /insights/:1 | Same limit: renamed posts still need their own rows, above the wildcard. |
Post name, /post-name/ | One row: /post-name → the new path | One row: /post-name → the new path | Copy the slash the old site used. See the trailing-slash section. |
Plain /?p=123 | Old path %?p%=123 → the new path | Check in your project | Webflow's help escapes ? and = with % in the old path. Framer's redirect help documents path wildcards and says sub-path redirects stay on the connected domain. It does not document query-string rules. |
Category /category/news/, or your custom base | /category/(.*) → the new archive, %1 if the slug stays | /category/* → the new path, :1 if the slug stays | Use the base from Settings → Permalinks, not the word category, if you changed it. |
Tag /tag/launch/ | /tag/(.*) → the new path | /tag/* → the new path | Same as categories: the base can be renamed and cannot be removed. |
| Author archive | Check in your project | Check in your project | Confirm the prefix on the old site. Do not assume /author/ if a plugin or the permalinks screen changed it. |
Pagination such as /page/2/ | Usually no new page | Usually no new page | Confirm the path. A 404, or a redirect to the first page of that archive, is a decision. Do not send every page number to the homepage. |
Feeds such as /feed/ | Check in your project | Check in your project | If the new site has no feed, a 404 can be the right response. Test one feed URL before writing a rule. |
/wp-content/uploads/… | One row per file that had links or traffic | One row per file that had links or traffic | Test one file on the new host before you write a folder rule. Do not assume a wildcard covers media. |
4. Trailing slashes
WordPress's own examples include a trailing slash in one Day-and-name URL and leave it off another. Copy the old path exactly, including the slash if the old site used one. How Webflow or Framer treats a missing slash is not something to guess from the redirect docs: request one real old URL with curl -sI, with and without the slash, and match the rule to the path that 404s.
5. Do not send everything to the homepage
Google's site-move guide says not to redirect many old URLs to one irrelevant destination, such as the new homepage. Google says that can be treated as a soft 404. A post goes to the same post. A category goes to the closest new section. A page you removed on purpose can return 404 or 410. Redirecting several old URLs to one page that actually combines their content is the case Google allows.
6. Import on Webflow or Framer
- Webflow. A CSV import overwrites every existing redirect. Export first, merge, then import, then publish. The columns and the failure email are in Webflow migration redirects. If a saved rule still 404s, use Webflow redirects not working.
- Framer. Redirect Sync updates a row whose
frompath matches an existing redirect and leaves the others. That is the opposite of Webflow. The CSV columns are in Framer migration redirects.
7. Check after launch, then again 7 days later
After you publish, request every old URL. The first response should be one permanent redirect (301 or 308) to a page that returns 200. Run the same check a week later: a slug edit or a fresh import can drop a rule. The header loop is in the Webflow and Framer guides.
The free Lost-URL Scan looks up the addresses public web archives saved for a domain and checks what each one returns on the live site today. It shows the top 10 free.
Fixing it yourself? The DIY Fix Kit ($49 once; ₹3,999 in India, no GST) turns your scan's lost-URL list into a ready-to-import redirect file for Webflow, Framer, WordPress, Next.js/Vercel, Netlify, Apache, Nginx or CSV, with a re-check 7 days later. It's offered on your scan results. Run the free scan
Want it done for you? Migration Repair: we map every old URL that gets search traffic, put the redirects in and check them at launch and 7 days later. $500 per site (₹40,000 in India); sites over 60 URLs are quoted first. The redirect map for your top 10 pages is free first: email hello@swynq.com. We don't promise rankings or traffic. A real WordPress-to-Framer move, with the paths generalised, is the sample record on Migration Repair.
Questions
Can I redirect every WordPress post with one wildcard?
Only when the slug did not change and the only difference is the folder. Renamed posts need their own rows, placed so they match before the broader rule.
What do I do with /?p=123 URLs?
Webflow's help escapes the question mark and the equals sign in the old path. Framer's redirect help does not document query-string rules, so test one plain permalink in the project before you write the rest.
Should category and tag archives go to the new homepage?
No. Google's site-move guide says sending many old URLs to one irrelevant page, such as the homepage, may be treated as a soft 404. Point each archive at the closest new section, or let it 404 if you removed it on purpose.