ID
Description | Example Value |
Shopify's unique redirect identifier |
|
If present, the ID will be used to group multiple rows together into a single redirect. When importing, the ID will be used to see if the redirect already exists on the store. If there's no ID match the app will attempt to find an existing redirect using the Path.
Path
Description | Example Value |
Original URL path to redirect from |
|
The path is the original URL path that visitors are trying to access. The path is used for grouping multiple rows together into a single redirect and finding an existing redirect on the store if the ID is not present.
Command
Description | Example Value |
Action to perform: MERGE, UPDATE, DELETE, NEW |
|
MERGE: Update existing redirect or create if not found
DELETE: Remove the redirect from the store (will skip if redirect doesn't exist)
NEW: Create a new redirect (will skip if redirect already exists)
UPDATE: Update existing redirect (will skip if redirect doesn't exist)
Target
Description | Example Value |
New URL path to redirect to |
|
The target is the destination URL path where visitors will be redirected when they access the original path.
Export Filters
You can use these filters to limit which redirects are exported:
path: Filter by the redirect path. Use starts with to export every redirect under a prefix such as/products/, or equals any of for an exact list of pathstarget: Filter by the redirect target, with the same relations aspath. Targets can be full URLs, so starts withhttps://finds every redirect that points to another siteid: Filter by redirect IDcreated_at: Filter by when the redirect was created
Shopify compares path and target against the whole stored value, so these fields have no contains relation. Matching is case-insensitive. A leading slash is added if you leave it out, so products/ and /products/ filter the same redirects.
