301 redirects: send old URLs to new pages

A redirect forwards an old URL to its replacement, so visitors following an old link can reach the right page. Use Permanent (301) for a lasting move or Temporary (302) when the old address will return.

Open Redirects

You need site administrator access to add, edit, or delete redirects on your site. Other members may be able to view the list.

1. Open Redirects.
2. Check the account and site name. If needed, select the site name at the top to choose another site, then open Site Admin → Redirects.

Add a single redirect

Choose a relevant replacement page before saving. A redirect on Carrot handles requests reaching this site; it cannot forward an old domain still pointing to another host.

1. In From, enter the old path on this site, such as /old-page. Don’t include the domain.
2. In To, enter the replacement path, such as /new-page, or a full external URL beginning with https:// or http://.
3. Check the destination preview below the fields.
4. Choose Permanent (301) or Temporary (302).
5. Select Add redirect. Your rule appears in Active redirects.

If a field reports an error, correct it and save again. A source path can have only one rule; edit the existing rule to change its destination. The source and destination cannot be the same.

If you see Saved, but we couldn't update your site, the rule is saved in Carrot but the live-site update failed. Use the help drawer’s Support tab if this persists, and test the old URL before relying on it.

Redirect a whole section at once with a wildcard

A trailing /* matches everything beneath a path:

• From /blog/*, To /resources/* — /blog/my-post goes to /resources/my-post.
• From /old-section/*, To /new-home — every matching path goes to the same page.

Use the single-redirect steps above to save the rule. A wildcard must be a single trailing /*; /blog* and /a/*/b are invalid. Test more than one old page after saving a wildcard.

Add redirects in bulk

Bulk import creates permanent 301 redirects. You can edit a rule to 302 afterward.

1. Expand Bulk 301 Redirect Import.

2. In Paste redirects, enter one from,to pair per line:

   /old-page,/new-page
   /about-us,/about
   /blog/*,/resources/*
   

   Alternatively, use Or, upload a CSV with the same two-column format. An optional source,target header is skipped. Choose one input method: an uploaded file takes priority over pasted text.

3. Select Add / upload redirects.

4. Review Import results for every row:

   • Added — saved.
   • Duplicate — a prior successful row in this import used that source.
   • Already exists — this site already has a rule for the source; edit it in Active redirects instead.
   • Error — correct the row using the displayed explanation.
   • Limit reached — review the displayed limit and remove unneeded rules before adding more.

Successful rows stay saved when other rows fail. Correct and re-import only the failed rows. A live-site update warning still requires the check below, even when rows say Added.

Review, edit, and remove redirects

1. In Active redirects, select Edit on the intended rule.
2. Change its values and select Save, or select Cancel to discard your edits.
3. Check that the row shows your saved values, then test the old URL as described below.

To remove a rule:

1. Select Delete on the intended rule and confirm. Requests to its old URL will no longer use that rule.
2. Check that the row disappears from Active redirects.

Check the live result

1. Open an old URL on your public domain in a fresh browser tab.
2. Confirm that the address changes to the intended destination and that the replacement page loads.
3. Repeat for each important old URL, including examples covered by wildcard rules.

If the result is wrong, check From, To, and the selected site. Avoid chains or loops that send visitors between multiple old URLs. If the saved rule still fails, use the help drawer’s Support tab with the old URL and intended destination.

Matching details

• Case and trailing slashes — /About/ and /about use the same source rule.
• Tracking parameters — the original query string, such as UTM tags, carries over only if the destination has no query string of its own.
• Site moves — use the SEO migration checklist to plan URL changes before switching your domain.