Setting Up a 301 Redirect for Category URL Changes

Setting Up a 301 Redirect for Category URL Changes

This article explains how to redirect an old, SEO-optimized category URL to a new category URL without restoring a deleted category. Restoring a deleted category via the admin interface is not possible, and while technical restoration may be possible via the database (available as a chargeable service), it does not recover SEO metadata or original mappings.

The preferred solution is to set up a 301 redirect from the old URL (for example, /c/22/allbooks) to the new URL (for example, /c/15/allbooks). Doing so maintains your SEO value and ensures visitors are directed to the correct category page.

Below is a guide on how to configure this redirect via the URL Rewrite Rules in the Storefront Management area of Infigo.

Use cases

• Redirecting a legacy SEO-focused category URL to a new category page.
• Ensuring seamless user experience when product categories are remapped.

Key settings in Infigo

• URL Rewrite Rules: Found under Storefront Management > URL Rewrite Rules.
• Platform Admin Access: Required to view and modify URL rewrite configurations.

Step-by-step guide

1. Log in to your Infigo platform using your platform admin credentials.
2. Navigate to the Storefront Management section and select the URL Rewrite Rules page.
   
   
   • 
     
3. Click on the option to add a new rewrite rule.
   
   
   • 
4. In the source URL field, enter the old category URL (for example, /c/22/allbooks).
5. In the destination URL field, enter the new category URL (for example, /c/15/allbooks).
6. Enable the rewrite rule.
   
   
   • 
7. Save the new rewrite rule and test the redirection to ensure it functions correctly.

Example: External Redirects (Redirecting to a Public Website)

A user wanted to redirect logout traffic from their Infigo storefront to an external site.

They initially used:

• From URL:
  https://example.infigosoftware.com/logout

• To URL:
  https://www.externalsite.com

🔧 This setup did not work due to how rewrite rules match HTTP patterns, external redirects must follow a specific format.

✅ Correct Format for External Redirects

1. Remove the s from https — Use http

Infigo matches redirects against non-secure (HTTP) traffic for internal pattern matching.

2. Use full match syntax in ‘From URL’:

• Add ^ at the beginning

• Add :80 after the domain (if using standard HTTP port)

• Add $ at the end

✅ Corrected Rewrite Rule Example:

• From URL:
  ^http://example.infigosoftware.com:80/logout$

• To URL:
  http://www.externalsite.com

💡 The ^ and $ ensure exact match, and :80 tells the system it’s listening on the default HTTP port.

🔄 Why HTTPS Doesn’t Work Here

The rewrite engine evaluates requests using HTTP pattern matching. Even if your storefront uses HTTPS, the URL pattern in the rewrite rule must be in HTTP with the correct port, otherwise the rule will not trigger.

Related links

• Infigo Academy – Redirection Capabilities in Infigo (Scenario 7)

For additional guidance, visit the Infigo Academyor contact Customer Support.