If you no longer need the Swift Redirects app for your Shopify store, follow the steps below to uninstall it properly and ensure a smooth transition without disrupting existing redirects.

Step 1: Access the Shopify Admin Panel

1. Log in to your Shopify store admin panel.
2. In the left-hand sidebar, click on Apps to view the list of installed applications.

Step 2: Locate and Uninstall the Swift Redirects App

1. Scroll through the list to find the Swift Redirects app.
2. Click the Delete button next to the app name.
3. Confirm the deletion by selecting Remove on the pop-up confirmation window.

Step 3: Verify Redirect Status

1. Ensure that critical redirects remain functional after uninstalling the app.
2. Go to Online Store > Navigation > URL Redirects to review any Shopify-native redirects.
3. If necessary, manually recreate important redirects using Shopify's built-in URL Redirect feature.

Step 4: Remove App Code (If Applicable)

If you manually added any code snippets during installation, follow these steps:

1. Navigate to Online Store > Themes.
2. Click Actions > Edit Code.
3. Look for any code related to the Swift Redirects app (usually in theme.liquid or snippets folder).
4. Delete these snippets carefully to prevent errors.

Step 5: Confirm Successful Uninstallation

1. Clear your browser cache and cookies.
2. Test previously redirected URLs to confirm they are functioning correctly.
3. Check Google Search Console for any new 404 errors and resolve them promptly.

Optional: Provide Feedback

We value your feedback! If you experienced issues or have suggestions, please consider sharing your thoughts to help us improve the app.

If you encounter any issues during or after uninstalling the app, feel free to contact our support team for assistance.

In the Swift Redirects Shopify app dashboard inlcuded unresolved, resolved, live and ignored redirect interface.

Table of Contents

• Unresolved Redirects Overview
• Resolved Redirects Overview
• Live Redirects (301) Overview
• Ignored Redirects Overview

Unresolved Redirects Overview

The Unresolved Redirects section is a redirect management tool that helps you fix broken links by assigning correct targets, monitor traffic on those broken URLs, and improve SEO & user experience.

This section highlights broken or invalid redirects. These are URLs where:

• The original URL doesn't exist,
• No valid redirect target is defined,
• Resulting in 404 errors, harming SEO and user experience.

Features in the Unresolved Redirects Interface

Search Bar

• Allows you to quickly search URLs (both redirect-from and redirect-to fields).
• Helps filter large lists of redirects.

Redirect From (Blue Links)

The original broken URL (e.g., /pages/old-page ).

• Clicking these likely opens the broken URL in a new tab.

Redirect To (Editable Field)

Input box to define a correct target URL (e.g., /pages/new-page).

• Example placeholder: Example: /#.
• You can manually assign the correct destination.

Action Buttons (Icons next to Redirect To)

• Redirect → Clicking on the redirect icon will successfully assign a destination for the broken URL.
• Ignore → Ignore or disable this redirect.

Hits (Number column)

Number of times users attempted to access the broken URL.

• Example: 1 or 2 hits recorded.

First Seen

The date when this broken redirect was first detected.

• Example: August 21, 2025.

Last Seen

The date when it was last triggered by a visitor.

• Example: August 29, 2025.

Pagination (Bottom Controls)

Navigation arrows (◀ ▶) to browse through multiple unresolved redirect pages if the list is long.

Resolved Redirects Overview

The Resolved Redirects section ensures broken URLs are already mapped correctly from Unresolved Redirects section, providing details like original broken link, fixed destination, action controls, usage stats, and tracking dates.

 This section highlights valid redirects. These are URLs where:

• This section highlights resolved redirects. This ensures users/search engines get redirected to the correct content without hitting a 404 error.
• Valid redirect target (Redirect to) is defined.

Features in the Resolved Redirects Interface

Search Bar

• Allows you to quickly search URLs (both redirect-from and redirect-to fields).
• Helps filter large lists of redirects.

Redirect From (Blue Links)

Shows the original broken URL that was fixed.

• Clicking these blue links will likely open the old/broken URL (e.g., /pages/old-page).

Redirect To

Shows the corrected target URL where the broken link redirects (e.g., /pages/new-page) 

• Clicking these will open the new valid page.

Action Buttons (Icons next to Redirect To)

• Trash Bin  → Delete the redirect rule.
• Ignore  → Ignore or disable the redirect.

Hits (Number column)

Number of times users attempted to access the broken URL.

• Example: 1 or 2 hits recorded.

First Seen

The date when this broken redirect was first detected.

• Example: August 21, 2025.

Last Seen

The date when it was last triggered by a visitor.

• Example: August 29, 2025.

Pagination (Bottom Controls)

Navigation arrows (◀ ▶) to browse through multiple unresolved redirect pages if the list is long.

Live Redirects (301) Overview

Live Redirects (301) in Shopify are executed on the client-side, meaning the user's browser handles the redirection after the page has loaded. This differs from server-side redirects (like 301 redirects set within Shopify's admin), which happen before the browser even fully renders the initial page.

When a user visits a page containing in the JavaScript, the browser executes the script after the page's HTML and CSS are parsed.

Features in the Live Redirects (301) Interface

Search Bar

• Allows you to quickly search URLs (both redirect-from and redirect-to fields).
• Helps filter large lists of redirects.

Redirect From (Blue Links)

Shows the original broken URL that was fixed.

• Clicking these blue links will likely open the old/broken URL.

Redirect To (Editable Field)

Shows the corrected target URL where the broken link redirects.

• Clicking these will open the new valid page.

Action Buttons (Icons next to Redirect To)

• Trash Bin  → Delete the redirect rule.
• Ignore  → Ignore or disable the redirect.

Hits (Number column)

Number of times users attempted to access the broken URL.

• Example: 1 or 2 hits recorded.

First Seen

The date when this broken redirect was first detected.

• Example: August 21, 2025.

Last Seen

The date when it was last triggered by a visitor.

• Example: August 29, 2025.

Pagination (Bottom Controls)

Navigation arrows (◀ ▶) to browse through multiple unresolved redirect pages if the list is long.

Ignored Redirects Overview

Ignored redirects are simply broken links you’ve chosen not to redirect, with clear options to delete or restore them, while still tracking hits, and the first/last seen activity.

Features in the Ignored Interface

Search Bar

• Allows you to quickly search URLs (both redirect-from and redirect-to fields).
• Helps filter large lists of redirects.

Redirect From (Blue Links)

Shows the original broken URL that was fixed.

• Shows the original broken or unused URL.

Redirect To

Shows the corrected target URL where the broken link redirects.

• Displays the destination URL (if any was previously assigned).

Action Buttons (Icons next to Redirect To)

• Trash Bin  → Delete the redirect rule.
• Restore/Undo Arrow Icon → Move the ignored redirect back to unresolved redirects so it can be reassigned to a new destination.

Hits (Number column)

Number of times users attempted to access the broken URL.

• Example: 1 or 2 hits recorded.

First Seen

The date when this broken redirect was first detected.

• Example: August 21, 2025.

Last Seen

The date when it was last triggered by a visitor.

• Example: August 29, 2025.

Pagination (Bottom Controls)

Navigation arrows (◀ ▶) to browse through multiple unresolved redirect pages if the list is long.

Here's a step-by-step guide on how to import and export redirect URLs in bulk using the Swift Redirects Shopify App:

Export Redirects in Bulk

1. Access the Swift Redirects App:
   
   
• Go to your Shopify Admin.
• Click on Apps > Select Swift Redirects.
2. Export Existing Redirects:
   
   
   • All Redirects – Export the entire list of redirects.
   • Filtered Redirects – Export based on applied filters (e.g., only 301s).
• Navigate to the Redirects tab.
• Click on the Export button (usually located at the top-right corner).
• Choose between:
• Download the CSV file and save it to your system.

Import Redirects in Bulk

1. Download the CSV Template

• In the Swift Redirects app, go to the Import Redirects section.
• Click Download CSV Template to get a pre-formatted sheet.

2. Prepare Your CSV File

Ensure the CSV is formatted correctly with the following columns:

From URL	To URL	Redirect Type
/old-url	/new-url	301
/products/*	/collections/all/	301
/old-blog/*	/blogs/news/	302

Notes:

• From URL: This is the old path (e.g., /old-page).
• To URL: This is the new path where you want to redirect (e.g., /new-page).
• Redirect Type: Use 301 (permanent redirect) or 302 (temporary redirect).
• Wildcards: Use * in the From URL and in the To URL to manage dynamic patterns.

3. Upload the CSV File

1. Go to the Import Redirects section in the app.
2. Click Upload CSV and select your prepared CSV file.
3. Review the preview of your redirects.
4. Click Confirm Upload to complete the import.

4. Validate the Import

• Check the Redirect List to confirm all entries are imported.
• Test a few redirected URLs to verify they work correctly.

Pro Tips:

• Avoid Redirect Chains: Ensure the To URL doesn't point to another redirect.
• Bulk Cleanup: Use the Export feature to audit and clean outdated redirects.
• Dynamic Redirects: Utilize wildcards for product/category changes (e.g., /products/* to /collections/all/).

A 301 redirect is an HTTP status code that indicates a resource has been permanently moved to a new URL. It's a server-side redirect, meaning the server itself sends the instruction to the browser and search engines to go to the new location. This is important for SEO, as it passes most of the link equity from the old URL to the new one.

While Live (Active) Page can be used to perform redirects, a "JavaScript 301 redirect" is not a true 301 redirect in the HTTP sense. Instead, it refers to using JavaScript code on the client-side (within the user's browser) to redirect them to a new page. This is typically achieved by modifying the window.location object in JavaScript, for example:

JavaScript
window.location.href = "http://www.newsite.com/new-page.html";

Key differences between a true 301 redirect and a JavaScript redirect:

Server-side vs. Client-side:

301 redirects are handled by the server before content is loaded, while JavaScript redirects occur after the page starts loading in the browser.

SEO Impact:

True 301 redirects are recognized by search engines as a permanent move and pass link equity, which is crucial for maintaining search rankings. JavaScript redirects, while they can move users, are not as effective for SEO and may be interpreted differently by search engines.

Reliability:

JavaScript redirects rely on the user's browser having JavaScript enabled and functioning correctly. Server-side 301 redirects work regardless of client-side settings.

When to use a JavaScript redirect (as a last resort):

While 301 redirects are generally preferred for permanent moves, JavaScript redirects might be used in situations where server-side access to implement a true 301 is unavailable, such as:

• When you only have control over the HTML content of a page and cannot modify server configurations.
• For temporary client-side routing within a single-page application (SPA) where the URL changes without a full page reload.

However, for permanent URL changes with SEO considerations, a server-side 301 redirect is the recommended method.

Wildcard redirects let you fix many URLs at once with a single rule. Use placeholders to catch any text in the "Redirect From" path and send visitors to the right destination—no coding required.

How it works

• * matches "anything" across one or more path segments.
• $1, $2, … reuse what the wildcard captured (first match is $1, second is $2, etc.).
• Rules work on the path part of the URL (everything after your domain).

Example:

From: /blog/* → To: /blogs/news

Any URL that starts with /blog/… will go to /blogs/news.

Common recipes (copy & use)

Move an entire folder

From: /old-collection/*

To: /collections/new-collection

Use when every page under /old-collection/ should point to one place.

Preserve the article/product slug

From: /blog/*

To: /blogs/news/$1

/blog/how-to-grow → /blogs/news/how-to-grow

Rename a folder and keep sub-paths

From: /pages/*/*

To: /info/$1/$2

/pages/help/shipping → /info/help/shipping

Collapse many product URLs into one

From: /products/*

To: /collections/all

Great when products were deleted.

Move brand pages and keep the brand name

From: /brand/*

To: /collections/$1

/brand/nike → /collections/nike

Fix a wrong top-level path

From: /blog/*

To: /blogs/$1

/blog/tips/bfcm → /blogs/tips/bfcm

Legacy PHP to Shopify

From: /*.php

To: /

/index.php → / (or send to the right modern page)

Tips & best practices

• Use 301 (permanent) for moved content—best for SEO.
• One rule beats many: create a wildcard instead of dozens of single redirects.
• Order matters: keep specific rules above broad ones (if your app supports rule priority).
• Avoid loops: don't redirect /a/* → /a/$1.
• Test first: try a few example URLs to confirm they land correctly.
• Query strings: If you need to keep UTM or query parameters, ensure your rule or app setting preserves them.

Quick starter table

Goal	Redirect From	Redirect To	Result Example
Move blog to new handle	/blog/*	/blogs/news/$1	/blog/sale → /blogs/news/sale
Merge all brand pages	/brands/*	/collections/$1	/brands/adidas → /collections/adidas
Retire a folder	/outlet/*	/collections/sale	/outlet/jackets → /collections/sale
Keep deep paths	/help/*/*	/support/$1/$2	/help/shipping/rates → /support/shipping/rates
Clean up PHP	/*.php	/	/about.php → /

FAQs

Will this pass SEO value?

Yes. use 301. Search engines transfer most ranking signals from the old URL to the new one.

Does * include slashes?

Yes. It captures across path segments. Use multiple wildcards if you want to map each segment to $1, $2, etc.

Can I keep the captured text?

Yes—use $1, $2 in your "Redirect To" field to re-insert what the * matched.

What about trailing slashes?

Treat /path and /path/ consistently. If both exist, add a rule that covers the variant you receive traffic on or set a canonical preference site-wide.

Common Regex Redirect Patterns in Shopify Swift Redirects App

Regex (regular expression) redirects let you bulk-redirect URLs that follow a pattern, instead of creating redirects one by one.

1. Wildcard Redirects (Match Everything After a Prefix)

Pattern:

/blog/(.*)

Redirect To:

/blogs/news/$1

Explanation: Redirects everything under /blog/ to /blogs/news/, keeping the slug.

Examples:

• /blog/article-1 → /blogs/news/article-1
• /blog/latest-update → /blogs/news/latest-update

2. Remove Query Strings (UTM, Tracking Parameters)

Pattern:

/products/([a-z0-9-]+)(\?.*)?$

Redirect To:

/products/$1

Explanation: Strips UTM or query strings from product pages.

Examples:

• /products/shirt?utm_source=google → /products/shirt
• /products/blue-jeans?ref=fb → /products/blue-jeans

3. Force HTTPS or Remove “www”

Pattern:

http://(www\.)?example\.com/(.*)

Redirect To:

https://example.com/$2

Explanation: Redirects all http:// or www. traffic to secure non-www version.

Examples:

• http://www.example.com/page → https://example.com/page
• http://example.com/contact → https://example.com/contact

4. Category Folder Redirects

Pattern:

/collections/old-collection/(.*)

Redirect To:

/collections/new-collection/$1

Explanation: Moves entire collection path.

Example: /collections/old-collection/shoes → /collections/new-collection/shoes

5. Remove File Extensions (.html, .php)

Pattern:

/(.*)\.html$

Redirect To:

/$1

Explanation: Removes .html extensions from old migrated URLs.

Examples:

• /about-us.html → /about-us
• /products/shirt.html → /products/shirt

6. Trailing Slash Normalization

Pattern:

/(.*)/$

Redirect To:

/$1

Explanation: Removes extra trailing slashes.

Examples:

• /contact/ → /contact
• /products/shirt/ → /products/shirt

7. Handle Case Sensitivity

Pattern:

/Products/(.*)

Redirect To:

/products/$1

Explanation: Redirects uppercase/lowercase versions to the correct canonical one.

Example: /Products/Blue-Jeans → /products/blue-jeans

8. Multiple Old Slugs → One New Page

Pattern:

/(old-page-1|old-page-2|old-page-3)$

Redirect To:

/new-page

Explanation: Multiple outdated URLs point to one updated URL.

Examples:

• /old-page-1 → /new-page
• /old-page-2 → /new-page

9. Date-Based Blog Redirects

Pattern:

/([0-9]{4})/([0-9]{2})/([0-9]{2})/(.*)

Redirect To:

/blogs/news/$4

Explanation: Strips old WordPress-style date paths.

Example: /2023/11/15/black-friday-sale → /blogs/news/black-friday-sale

10. Force Lowercase URLs

Note: Not all apps support case-conversion tokens like \L.

Pattern:

/(.*[A-Z].*)

Redirect To:

/\L$1

Explanation: Converts uppercase to lowercase URLs (where supported).

Example: /Products/Blue → /products/blue

Summary Table of Regex Redirect Patterns

Type	Pattern Example	Redirect Example
Wildcard Redirect	/blog/(.*) → /blogs/news/$1	/blog/post → /blogs/news/post
Strip Query Strings	/products/([a-z0-9-]+)(\?.*)?$ → /products/$1	/products/shirt?utm=1 → /products/shirt
Force HTTPS	http://(www\.)?example\.com/(.*) → https://example.com/$2	old → new domain
Move Collection	/collections/old/(.*) → /collections/new/$1	/old/product → /new/product
Remove .html Extension	/(.*)\.html$ → /$1	/about.html → /about
Trailing Slash Fix	/(.*)/$ → /$1	/page/ → /page
Case Sensitivity	/Products/(.*) → /products/$1	/Products/abc → /products/abc
Multiple Old → One New	/(old1|old2)$ → /new	/old1 → /new
Date Blog URLs	/[0-9]{4}/[0-9]{2}/[0-9]{2}/(.*) → /blogs/news/$1	/2023/11/11/test → /blogs/news/test
Force Lowercase	/(.*[A-Z].*) → /\L$1	/Products/Blue → /products/blue

---

Notes:

• Shopify’s native admin redirect tool does not support regex. Use a redirect app that supports regex/pattern rules.
• Some advanced tokens (like lowercase conversion) may not be supported in every app.
• Always test patterns on a staging URL or with a small subset before bulk-activating.

To enable email notifications for 404 URL detections in the Swift Redirects app for Shopify, follow these steps:

1. Access the Swift Redirects App:
   
   
• Log in to your Shopify Admin Panel.
• Navigate to Apps and select Swift Redirects.
  
  
2. Navigate to Notification Settings:
   
   
• Within the app, locate and click on the Settings or Notifications section.
3. Enable Email Notifications:
   
   
• Find the option labeled Email Notifications for 404 Detections.
• Toggle this feature to ON.
• Enter the email address(es) where you wish to receive these notifications.
• Set the Frequency of notifications (e.g., immediate, daily, weekly) based on your preference.
  
  
4. Save Your Settings:
   
   
• Click Save or Apply to confirm and activate the email notifications.