Skip to main content
Use the URL Redirects screen to send visitors from one path on your storefront to another address. Each redirect is permanent (HTTP 301), so search engines move their listing to the new address. Redirects are the recommended way to keep marketing and legacy URLs working. A marketing URL such as /tv-offer, or an address from your old website such as /beet-blend-powder.html, is what customers without a rep type or click: from TV, print, ads, or old links. Redirect it to the real product or page, such as /home/products/beet-blend. Reps don’t use those URLs. When they share from the Fluid mobile app or their own links, they use credited paths such as /<username>/products/beet-blend, so they still get credit. A redirect doesn’t establish credit, and it doesn’t take away credit a visitor already has. See Rep credit.

​
Where to find it

The URL Redirects screen isn’t in the admin sidebar. To open it, do either of these: The search result appears for admins.

​
What’s on the screen

The top of the screen has Export and Add URL Redirect. Export downloads your redirects as a CSV file. The table lists your redirects, with the Old Path, the New Path, and when each was created. Edit or delete a redirect from its row.

​
Add a redirect

  1. Click Add URL Redirect.
  2. In Old Path, enter the path visitors arrive on, such as /tv-offer. It must start with / and can’t contain spaces.
  3. In Redirect to Path, enter where they should go. Use a path on your storefront, such as /home/products/beet-blend, or a full URL that starts with https://.
  4. Save.

​
How redirects work

  • Exact path only. /tv-offer redirects, but /tv-offer/extra doesn’t. The query string isn’t part of the match.
  • The query string isn’t forwarded. The visitor arrives at exactly the address in Redirect to Path.
  • Every storefront domain. A redirect works on each domain your storefront uses.
  • Redirects come first. If a custom route uses the same path, the redirect wins.
  • A rep’s username wins over a redirect. A redirect on /jordan-lee doesn’t fire while an active rep has the username jordan-lee.
Changes can be slow to reach a path visitors have already requested. Fluid remembers each path’s redirect lookup for up to 30 days, and adding, editing, or deleting a redirect doesn’t always reset that today. Add a redirect before you publish or move the URL. If a redirect doesn’t take effect, contact Fluid support.

​
Paths you can’t redirect

Fluid rejects an Old Path that:
  • Contains /app, /www, /fluid, /api, /shop, or /cable anywhere, or /cart/, /checkout/, or /admin/. These match as text, so /apple-cider and /shop-sale are rejected too. Choose another path, such as /cider or /sale.
  • Matches one of your storefront’s own pages, such as /<anything>/products/<slug>.
  • Already has a redirect.

​
Redirect or custom route?

Both can send visitors somewhere else. Pick by what the URL needs:
Email Fluid support at help@fluid.app. The Getting help page lists what to include in your request.