Webflow 301 redirect CSV template and import checklist
By MoveLedger · Reviewed September 24, 2026
Preparing redirects for a Webflow client migration? Start with a small two-column file, keep the existing rules safe, and separate the map review from testing the published site.
Export before importing. Webflow says a CSV import replaces all existing redirects. To retain old rules, export them and merge the intended additions before importing. Do not upload this example into a live client site as a replacement list. Read Webflow’s import guidance.
Two columns, with deliberately simple paths
Old path,Redirect to path
/about,/company
/news,/insightsColumn one is the old path; column two is the intended replacement. These fictional paths demonstrate the structure without wildcards, query strings or escaped characters. Replace them with reviewed decisions for your site. The example follows Webflow’s documented two-column shape; it has not been imported into your store or site.
MoveLedger recognizes these column labels directly. Keep extra owner, rationale and sign-off details in a separate working sheet, and preserve the original export for recovery. The checker’s findings CSV is an issue list, not a file to import into Webflow.
What the checker can—and cannot—review
The free checker reviews up to 1,000 exact-match rules and 1 MB of input. It finds loops, chains, conflicting destinations and duplicate sources. Optional old and new URL inventories help identify decisions that need review. It never connects to Webflow or requests the URLs.
Do not treat Webflow pattern rules as literal URLs. Webflow supports capture groups and percent-based escaping, including for hyphens in old paths, and applies rules in order. MoveLedger does not simulate those rules. Keep patterns and escaped source expressions in a separate platform review; do not remove escapes just to make a CSV pass. Use Webflow’s path syntax documentation.
If your export mixes exact paths and patterns, a review of the simple subset cannot prove the full redirect configuration is correct. Record the omitted rules and their separate verification. Preserve the complete intended list when preparing the import.
A practical preparation workflow
- Keep a baseline. Save the current export with a date and site identifier in your own project folder.
- Decide which URLs change. A URL that stays at the same location may need no redirect. Record unchanged and intentionally retired pages outside the redirect CSV.
- Reconcile the intended rules. Compare retained rules and additions. Resolve multiple destinations for the same source instead of blindly appending rows.
- Review exact paths. Load the supported simple-path map in MoveLedger. Resolve findings, rerun the corrected input and save its report with the reviewed CSV. Map data stays in your browser.
- Review platform rules separately. Have the person responsible for Webflow check patterns, escaping, precedence and rules excluded from the simple map.
- Confirm the complete import. The full intended list should account for retained rules as well as changes. A smaller checker subset is not a replacement for this list.
Import and verify the published result
Webflow’s documented path is Site settings → Publishing → 301 redirects → Import. Its CSV upload limit is 16 MB. Publish the site to apply imported redirects. Webflow’s upload limit is separate from MoveLedger’s 1 MB review limit. Check the current import instructions.
After publishing, test the old URLs and record observed status, final destination and content. Include representative pattern matches and exceptions in the platform test set. A clean map report is not proof that the import or live routing worked.
What goes into the client handoff?
- Original export and complete intended import CSV.
- The exact subset reviewed in MoveLedger, plus a record of excluded pattern rules.
- Findings and the report’s fingerprints for the reviewed input text.
- Live response evidence, unresolved exceptions and the person responsible for each decision.
For a broader launch review, use the agency migration checklist. For spreadsheet preparation, see the generic redirect map guide. MoveLedger is independent of Webflow.