Docs

URL Redirects

Business Plan

Set up 301 (permanent) and 302 (temporary) redirects to preserve SEO value when migrating your domain to Prometora. Essential for stores connecting an existing domain with established search rankings.

When to Use Redirects

URL redirects are critical when you're connecting a custom domain that previously hosted a different website. Without redirects, visitors following old links or search engine results will see a 404 error page.

  • Domain migration — Redirecting old pages from your previous website to new Prometora pages
  • SEO preservation — Maintaining search rankings by telling Google where content moved
  • Broken link cleanup — Fixing URLs reported in Google Search Console
  • URL restructuring — Changing URL paths while keeping old URLs working

301 vs 302 Redirects

301 — Permanent Redirect

Tells search engines the page has permanently moved. The new URL will replace the old one in search results. Use this for most cases, especially domain migrations.

Recommended

302 — Temporary Redirect

Tells search engines the move is temporary. The original URL stays in search results. Use this for seasonal pages, A/B testing, or maintenance.

Situational

Adding Redirects

Single Redirect

  1. Go to Store Settings → Redirects tab
  2. Click "Add Redirect"
  3. Enter the source path (the old URL path, must start with /)
  4. Enter the destination (a new path or full URL)
  5. Choose the redirect type (301 or 302)
  6. Click "Add"

Bulk Import from CSV

For large numbers of redirects (e.g., fixing hundreds of broken links from Google Search Console), you can upload a CSV file:

  1. Prepare a CSV file with source and destination columns
  2. Optionally add a type column (301 or 302, defaults to 301)
  3. Click "Import CSV" in the Redirects tab
  4. Review the import results
source,destination
/old-about-page,/pages/about
/blog/2024/my-post,/pages/blog
/products/widget,/listings/premium-widget
/contact,https://forms.google.com/your-form

Source Path Rules

Must start with /
Matches exactly — /old-page only matches that exact path
No duplicate source paths — each source can only redirect to one destination

Restricted Paths

You cannot create redirects for system paths like /api/, /dashboard/,/seller-dashboard/, /signin, or /signup.

Destination Options

Relative path — e.g., /pages/about redirects to a page on your store
Listing page — e.g., /listing/my-product redirects to a specific listing
External URL — e.g., https://example.com/page redirects off-site

Limits

PlanMax Redirects
Starter / ProNot available
Business1,000

How It Works

When a visitor or search engine bot requests a URL on your store:

  1. The incoming URL path is checked against your redirect rules
  2. If a match is found, the server responds with a 301 or 302 status code and the destination URL
  3. The visitor's browser automatically follows the redirect to the new page
  4. Search engines update their index accordingly (for 301 redirects)

Redirects work on custom domains and are checked before page routing, so they take priority over any page that might exist at the source path. Matching is case-insensitive and trailing slashes are ignored (e.g., /Old-Page/ and /old-page are treated the same).

Redirects currently apply to custom domains only. They are not active on the default Prometora store URL (prometora.com/s/your-store).

Tips

  • Export broken URLs from Google Search Console and use the CSV bulk import to fix them quickly
  • Use 301 redirects for permanent moves — search engines will transfer SEO value to the new URL
  • Avoid redirect chains (A→B→C). Point the source directly to the final destination
  • Use the search/filter in the Redirects tab to find and manage specific redirects
Import Data (CSV)SEO Settings
URL Redirects (301/302) | Prometora Docs