Bulk import via CSV
Instead of creating rules one at a time, you can import a batch from a CSV file, straight into a specific domain.
Where to import
Import happens from within a domain's page, since the CSV itself doesn't include a domain column, every row you upload becomes a rule on whichever domain you're currently viewing.
CSV format
Four columns: source_path, destination_url, redirect_type, notes.
source_path and destination_url are required, a file missing either column won't process at all. redirect_type is optional, leave it blank and it defaults to 301. notes is optional too. The first row must be a header row, that's how columns are matched, order doesn't matter as long as the names are right. Only .csv files are accepted.
If something's wrong with the file
Errors block the entire import, nothing partial gets through. If any row has a problem, you'll see the issues listed inline with line numbers before anything is saved, fix those rows in your file and re-upload. This is intentional, it means you'll never end up with a half-imported, inconsistent set of rules.
Handling conflicts
If a row's path already exists as a rule on that domain, it's flagged in the import preview as a conflict. You decide row by row, keep the existing rule and skip that row, or let the import overwrite it. There's no single all-or-nothing choice for the whole file, you control each conflict individually before confirming.
Getting the format right the first time
Starting from a template avoids most formatting issues. See CSV Import Format for the full column reference and a downloadable template.
Related
Need to go the other direction? See Exporting Redirects, the export format matches this import format exactly, so you can round-trip a domain's rules through a spreadsheet.