Field guide · technical workflow
Preserve the useful WordPress URLs during a Webflow move
A visual rebuild can make a website look better while changing almost every address behind the scenes. WordPress posts, category archives and media files rarely have identical route structures in a new Webflow project. That mismatch deserves a deliberate migration decision, not just a redirect plugin export.
Who this is for: Help a website owner map WordPress page, post, taxonomy and media paths to meaningful destinations when changing CMS.
Editorial preview — facts, worked examples and publication approval are still being checked.
The practical problem
A practical preserve the useful wordpress urls during a webflow move exercise: Inventory WordPress post, category, page and media URLs before replatforming. The outcome is a documented decision backed by classify exact matches, deliberate consolidations and intentional removals. The final check is to check final HTTP responses, canonical targets and content parity after release.
What you will be able to check
- Inventory WordPress post, category, page and media URLs before replatforming.
- Classify exact matches, deliberate consolidations and intentional removals.
- Check final HTTP responses, canonical targets and content parity after release.
Reproducible scenario
Worked example: Preserve the useful WordPress URLs during a Webflow move
An illustrative professional-services firm rebuilds a WordPress site in Webflow. The new design has polished service pages and a modern CMS collection, but legacy WordPress blog posts, category archives and technical PDFs remain reachable from search and saved links. The redesign's menu captures only the current marketing pages. A responsible migration maps those older source journeys before changing hosting, not after traffic falls.
Starting assumptions
- The team can export WordPress posts, pages, archives, media URLs and significant search landing pages.
- The Webflow destination has drafted content and real candidate collection routes, but source-to-destination relevance has not yet been signed off.
Decisions and checks
Include old posts, taxonomies and media in the inventory
A full source crawl and available Search Console records identify content that the new navigation might omit. Group service pages, posts, category archives and downloadable files separately. A missing post in the Webflow CMS import should be a documented exception rather than a silent omission.
What to verify: An exhaustive-for-priority URL inventory with discovered source type, landing relevance and intended retention decision.
Assign a meaningful Webflow successor to each retained topic
An old WordPress post should lead to a corresponding article, not the new blog home. A category archive may consolidate into a useful new collection only when the visible destination explains the same subject. Media should remain downloadable or redirect to a genuine replacement.
What to verify: A content-equivalence map with approved new URLs, notes on intentional consolidation and explicit unresolved files.
Rehearse both direct old links and destination rendered HTML
Test response codes, redirects, final canonicals and internal links using one example of each source class. Webflow routing and WordPress permalink histories can differ, so a universal regex should not be assumed safe without inspection.
What to verify: Production retests of the same sample confirm that legacy users reach relevant Webflow content with coherent indexability.
Expected output: The final migration register makes invisible legacy content visible to the new team's release process. It gives readers suitable destinations, distinguishes intentional removals from accidental omissions and exposes content mismatches before a production move. It should not rely on the beauty of the new design as proof that search landings survived.
This wordpress to webflow url mapping migration story is hypothetical and is not an observed client cutover or verified ranking result.
Inventory the WordPress content types
Export real pages, posts, categories, author archives and important downloadable files. Combine the technical crawl with Search Console landing-page evidence; old blog posts not linked in the new navigation may still attract valuable visitors. Mark which content is retained, consolidated or intentionally removed.
Reference: official · 2026-11-07
Choose the right new destination for each route
An old tutorial should normally point to the same subject in the new CMS, not automatically to the blog home. For categories that are being reorganised, decide whether a useful consolidated collection replaces them. Keep an exception list for media and redirects that the destination platform may not create by default.
Reference: official · 2026-11-07
Test before removing the old hosting
Test a representative sample on a controllable preview: HTTP response, final destination, canonical, visible content and internal links. After cutover, request those old URLs again. A visually polished launch is not a substitute for confirming that the content visitors sought still exists.
Reference: official · 2026-11-07
Decision aid
Decision table: WordPress to Webflow SEO: URL mapping checks
| Legacy issue or URL class | Relevant decision | Real evidence required |
|---|---|---|
| Old service page has a direct new service counterpart | Retain that buyer task and create a corresponding old-to-new mapping. | Review both visible service descriptions and final redirect status. |
| Several WordPress posts form one substantial new guide | Consolidate only if the destination contains the important original information. | Compare source topics, merged article coverage and incoming link paths. |
| PDF linked in articles is not imported to Webflow | Preserve a working download or appropriate successor, not a generic blog redirect. | Request the old asset URL and verify the final file or resource page. |
What a passing test looks like
These checks describe the evidence that should exist after a real implementation. They are not reports of tests already completed on a customer website.
Include old posts, taxonomies and media in the inventory
Expected result: An exhaustive-for-priority URL inventory with discovered source type, landing relevance and intended retention decision.
Keep as evidence: Archive the exact source URL requests, final destination and reviewer signoff for include old posts, taxonomies and media in the inventory.
Assign a meaningful Webflow successor to each retained topic
Expected result: A content-equivalence map with approved new URLs, notes on intentional consolidation and explicit unresolved files.
Keep as evidence: Archive the exact source URL requests, final destination and reviewer signoff for assign a meaningful webflow successor to each retained topic.
Rehearse both direct old links and destination rendered HTML
Expected result: Production retests of the same sample confirm that legacy users reach relevant Webflow content with coherent indexability.
Keep as evidence: Archive the exact source URL requests, final destination and reviewer signoff for rehearse both direct old links and destination rendered html.
Scope and limitations
The professional-services firm and CMS collection are illustrative. WordPress and Webflow route structures vary by plugins, collection settings and hosting configuration. This exercise has not observed real redirect behaviour and cannot guarantee post-move rankings; the website owner must approve content equivalence and test production responses.
Sources and verification
These references explain documented technical behaviour. The worked decisions are illustrative until checked on your own installation.
- official reference — Google's site move documentation covers URL inventories, mapping to relevant new pages and testing redirects after a CMS or domain transition. Recorded: 2026-11-07