
URL Redirects Guide: Understanding 301 vs 302 Mapping Implementation
URL redirects help prevent visitors from encountering non-functioning or duplicate pages by forwarding traffic from inactive to active pages. These redirects can be permanent (301) or temporary (302).
301 Redirects (Permanent)
- Informs search engines that a page has permanently moved
- Transfers ranking from old page to new page
- Use when:
- Changing page URLs
- Deleting pages
- Importing content with different URL structures
- Redirecting to different domains
302 Redirects (Temporary)
- Indicates temporary page relocation
- Maintains original page ranking
- Use when:
- Temporarily removing pages for updates
- Rotating seasonal content
- Replacing pages temporarily
Creating Redirects:
- Open Developer Tools panel
- Click URL Mappings
- Add redirects using proper formatting
- Click Save
Format Structure:
/old-url -> /new-url 301
For Collection Pages (blogs, stores, events):
/old-collection/[name] -> /new-collection/[name] 301
Important Formatting Tips:
- Match case sensitivity
- Avoid ?, &, or # symbols
- Limited to 400 KB (~2500 lines)
- Redirects process top to bottom
- Only works if original page is deleted/deactivated
Common Examples:
- Modified URLs:
/about-us -> /team 301
- Deleted Pages:
/history -> / 301
- Seasonal Content:
/summer-sale -> /fall-sale 302
- External Domains:
/fundraiser -> https://external-domain.com 301
Troubleshooting:
- Verify redirect format is correct
- Ensure destination pages are active
- Check for redirect loops
- Confirm proper URL structure
- Monitor for 404 errors
Remember: Always test redirects after implementation to ensure proper functionality and user experience.
Related Articles

Add Custom Nameservers to Your DNS Settings
