← All posts
Guides7 Nov 2026 · 3 min read

Importing redirects from CSV: a practical walkthrough

Prepare a small, reviewable CSV file, resolve validation errors and confirm exactly which redirect rules an import will create or update.

RedirectDuck team
RedirectDuck mascot

A CSV import turns a reviewed URL mapping into redirect rules without entering every source manually. The useful part is the review: a small mistake repeated across a file can affect many old links.

Start with a few representative rows before importing the rest of your mapping.

Use the basic three-column format

source,destination,code
old.example.com/pricing,https://example.com/plans,301
old.example.com/blog/*,https://example.com/articles/$1,301
old.example.com/summer,https://example.com/current-offers,302

The source identifies an old hostname and optional path. The destination is a complete URL. The code is one of the supported redirect status codes; when it is omitted, the default is 301.

Add the source domain to the correct workspace first. An import cannot create a usable rule for an unrelated domain that the workspace does not cover.

The wildcard row uses RedirectDuck's $1 placeholder. See the wildcard guide for how the matched suffix becomes part of the destination.

Review before applying

Choose Preview an import from the redirects page and upload the CSV or paste its contents. The preview shows each proposed source and destination, along with settings such as path forwarding, query forwarding and whether the rule is enabled.

No rules change merely because a preview was generated. Review the rows, resolve reported errors and explicitly confirm the import when it is ready.

CSV uploads support files up to 2 MB and batches up to 5,000 rules. The workspace's plan limit still applies, including limits shared with its client or project spaces.

Resolve duplicates deliberately

A repeated source in the same preview is an error. An existing rule can also conflict with a proposed new source.

Do not delete a useful rule just to get the file accepted. Decide whether the mapping is genuinely new or should update an existing rule. The option to update existing rules during import requires Pro or Agency.

Keep the original mapping file. It gives the team a readable record of the intended changes, independent of the dashboard.

Recreate a stale preview

A preview expires after one hour. It is also rejected if the workspace's rules have changed since the preview was generated. Generate a fresh preview and review the current results instead of assuming an older confirmation still describes today's configuration.

Test after confirmation

Use the rule tester for an exact path, a wildcard path and a request containing a query string. Then verify a real HTTP and HTTPS request to the old domain.

The import validates configuration; it does not establish that every destination page contains the right content. For a large migration, divide the work into batches that someone can meaningfully review and test.

Point your old domain at us

One DNS record, HTTPS included. Free for your first domain.

Start for free