In short. SEOPress maps redirect CSV fields in a fixed order from source path to connection status.
Definition: SEOPress expects a redirect CSV whose fields follow a fixed order: source path, destination URL, redirect type, enabled state, query-parameter mode, counter, category redirect IDs, regular-expression state, and connection status. The source path omits the domain, while the destination is an absolute URL.
Key facts
- SEOPress accepts comma or semicolon separators and requires the columns in its documented order. Its import guide lists the mapping.
- The redirect type field accepts
301,302,307,410or451. - The enable fields use
yes; an empty value disables the redirect or regular-expression setting. - The query-parameter field accepts
exact_match,without_paramorwith_ignored_param. - Counter and category redirect IDs are optional. Category IDs are comma-separated, such as
738,108,134.
What is the column order?
The import guide calls the first field “URL to match” and gives a path such as category/my-blog-post-slug. The next field is “URL to redirect in absolute”, with https://www.example.org/my-super-article as its example. The remaining fields map as follows:
- Redirect type:
301,302,307,410or451. - Redirect enabled state:
yesenables it; an empty field disables it. - Query-parameter mode:
exact_matchmatches all parameters,without_paramexcludes parameters, andwith_ignored_paramexcludes them while passing them to the redirect. - Counter, optional.
- Category redirect IDs, optional and separated by commas.
- Regular-expression state:
yesenables regular expressions; an empty field disables them. - Connection status:
both,only_logged_inoronly_not_logged_in.
The documentation’s linked example contains rows with these values:
url-to-match-301-multiple-cat-ids;https://seopress.org;301;yes;exact_match;3245;738,10808;yes;both
url-to-match-302;https://seopress.org;302;yes;with_ignored_param;;;;only_logged_in
url-to-match-307;https://seopress.org;307;yes;without_param;56;10808;;only_not_logged_in
How should the file be imported?
SEOPress places the upload control at SEO, Tools, the Redirections tab, and the Import Redirections section. The same documentation says that duplicated entries from the CSV are automatically removed to avoid conflicts. After import, it directs administrators to SEO, Redirections to see the new redirects.
The separator matters because it controls how each row is split into fields. The guide warns about using a comma or semicolon and states that, since version 9.7, separator detection is automatic. The row shown above uses semicolons, so values containing commas, such as 738,10808, remain inside one category-ID field.
What should a website owner verify before upload?
Check that every row keeps the source path in the first position and the absolute destination in the second. A path such as category/my-blog-post-slug has no domain, while https://seopress.org in the example is a complete destination URL. Empty positions are meaningful in the example: the second row leaves the counter, category IDs and regex field empty while retaining only_logged_in as the connection status.
The status code and query mode should match the intended redirect rule. The documented exact_match mode requires all parameters, without_param excludes them, and with_ignored_param passes excluded parameters to the destination.
FAQ
Can I put the full source URL in the first column?
Use the source path without your domain in the first field. Put the absolute destination URL in the second field, following the examples in the import guide.
Which separator should I choose?
You can use a comma or semicolon. Since version 9.7, SEOPress documents automatic separator detection, and the example CSV uses semicolons.
What happens to duplicate rows?
Duplicate entries from the CSV are automatically removed during import. You can then view the new redirects in SEO, Redirections.
Sources
- SEOPress, "Import redirects from a CSV file", 31 March 2026
- SEOPress, "SEOPress redirections example CSV", undated
Check how a page reads to answer engines. Open the GEO score analyzer