URL Mappings in Settings allows you to redirect away from pages that don't exist to pages that do exist. This can be for a permanent change (301 redirect) or a temporary change (302 redirect).

URL redirects work with your Squarespace URL and custom domains.

What's the difference between 301 and 302 redirects?

The basic difference between a 301 and 302 redirect is that a 301 redirect indicates a permanent change and a 302 redirect indicates a temporary one. 301 redirects are more common than 302 redirects.

301 Redirects

301 redirects are permanent. They tell browsers to go to a different URL when someone clicks a link to a nonexistent page. They tell search engines that a page has moved, and search engines transfer the old page's Page Rank to the new page.

Most likely, when creating a URL redirect, you'll use a 301.

302 Redirects

302 redirects are temporary. They tell browsers to go to a different URL when someone clicks a link to the old page. They tell search engines that a page has temporarily moved. Search engines don't give the new page the same Page Rank as the old one. However, since this is temporary, it lets search engines know that the original page should keep its rankings, as it will be back online.

302 redirects are commonly used in eCommerce when a store or restaurant changes its products and offerings seasonally.

When should I use URL redirects?

Usually, you'll use a 301 redirect. Depending on your situation, a 302 redirect may be better. Here are the common scenarios where you'll need to create redirects.

Using 301 Redirects

Since 301 redirects are for permanent changes (the page has moved permanently), 301 redirects are mostly used when a URL has changed. For example:

  • You have changed a page's URL (in its Page Settings)
  • Your URLs are different after importing content (In this scenario, it's usually because the old site didn't display a page slug for the blog page, just posts. Squarespace has a page slug for the blog page followed by the slug for the post.)
  • You're redirecting to another domain

Using 302 Redirects

Since 302 redirects are for temporary changes (the page has gone on vacation, and will be back soon), 302 redirects are uncommon and usually used by stores and restaurants whose offerings change seasonally. For example:

  • If you need to temporarily take down a page to update it for your new offerings
  • If you want to temporarily replace a page with another page as you cycle through different offerings through the year

The rest of this guide will walk you through setting up your redirects.

Step 1 - Go to URL Mappings Settings

From your Settings, click URL Mappings.

Step 2 - Create Shortcuts

To create a URL mapping, you need four elements:

  • The old URL for the page that doesn't exist
  • The "arrow", which is a dash immediately followed by a greater than sign (->)
  • The new URL for the page you want to redirect to
  • The redirect type (301 or 302)

The URL mapping looks like this:

/old-url -> /new-url 301
Note: Ensure the old URL doesn't exist and that the new URL does. You can do this by deleting the old page, disabling it, or changing its URL. For more information on deleting pages, disabling page, and changing URLs, visit How do I add a page to my site?Enabling and Disabling Pages, and How do I configure my Page Settings?.
Note: Ensure you keep the same capitalization as your URLs. If your URLs are all lower cased, then your redirects should also be all lower cased.

Step 3 - Save

After adding your redirects, click Save.

Examples and Common Scenarios

This section sets up some common situations that require URL redirects and walks you through how set up the redirects for them.

301 Examples

Changing a Page's URL

In my website, I have a page with the URL www.mybusiness.com/about . I want to change it to www.mybusiness.com/meet-the-team . I'm going to use a 301 redirect because this is a permanent change.

I need to follow these steps:

  1. In Page Settings, change /about to /meet-the-team
  2. In URL Mappings, create the redirect from /about to /meet-the-team

My redirect looks like this:

/about -> /meet-the-team 301

Imported Content

My website used to be with a different company, and I imported my blog into Squarespace. My old website's blog had this URL structure:

http://mybusiness.com/the-title-of-this-post

In Squarespace, my blog has this URL structure:

http://mybusiness.com/blog/the-title-of-this-post

To ensure my links still work, I need to create a redirect for every blog post. They look like this:

/the-title-of-this-post -> /blog/the-title-of-this-post 301
/the-title-of-another-post -> /blog/the-title-of-another-post 301

Redirecting to Another Domain

I have a page in my business's site to display information for our Kickstarter campaign. Its URL is www.mybusiness.com/kickstarter . Now I want to link directly to Kickstarter's website instead of that page.

I need to follow these steps:

  1. In URL Mappings, create a redirect from /kickstarter to my Kickstarter's URL.
  2. Delete or disable /kickstarter in my site.

My redirect looks like this:

/kickstarter -> https://www.kickstarter.com/projects/12345678/my-project 301

302 Examples

Reusing a page and using a temporary page during updates

I have an online store, www.mystore.com, which sells clothes. I have a Products Page which I use for our seasonal offerings. This page is wwww.mystore.com/seasonal-promotions

I'm going to use a temporary holding page when I update that page for the new season's offerings. Because my seasonal promotions page is only moving temporarily, I'm going to use a 302 redirect.

I need to follow these steps:

  1. Create my temporary holding page. give it a slug of /temporary-promotions .
  2. In URL Mappings, create a 302 redirect from /seasonal-promotions to /temporary promotions .
  3. Disable /seasonal-promotions .

My redirect looks like this:

/seasonal-promotions -> /temporary-promotions 302

When I'm done updating /seasonal-promotions for the new season's promotions, I follow those steps in reverse:

  1. Enable /seasonal-promotions .
  2. In URL Mappings, delete the 302 redirect.
  3. Disable /temporary-promotions .

Reusing a page and using another page during updates

This is a variation of the above example. Instead of using /temporary-promotions as a holding page, I'm going to use my main products page (www.mystore.com/all-clothes) as my holding page.

I need to follow these steps:

  1. In URL Mappings, create a 302 redirect from /seasonal-promotions to /all-clothes .
  2. Disable /seasonal-promotions .

My redirect looks like this:

/seasongal-promotions -> /all-clothes 302

When I'm done updating /seasonal promotions for the new season's promotions, I follow those steps in reverse:

  1. Enable /seasonal-promotions .
  2. In URL Mappings, delete the 302 redirect.

Cycling Through Pages

I have an online store, www.awesomestore.com, which sells clothes. I have four Products Pages that I rotate for each season's new styles. The pages are:

  • www.awesomestore.com/winter-sales
  • www.awesomestore.com/spring-sales
  • www.awesomestore.com/summer-sales
  • www.awesomestore.com/fall-sales

Since I create links to each page in its season and I don't want any links to break, I create 302 redirects to the live page.

Currently, summer is ending and my store is beginning its fall sales. I need to take these steps:

  1. Enable /fall-sales
  2. In URL Mappings, create three 302 redirects to redirect /summer-sales , /spring-sales , and /winter-sales to /fall-sales .
  3. Disable /summer-sales .

My redirects look like this:

/summer-sales -> /fall-sales 302
/spring-sales -> /fall-sales 302
/winter-sales -> /fall-sales 302

When fall is over and my winter sales start, I need to update my 302 redirects to redirect spring, summer, and fall to winter:

/summer-sales -> /winter-sales 302
/spring-sales -> /winter-sales 302
/fall-sales -> /winter-sales 302

Error Messages

If there's an error in your URL mapping, you'll see a red error message and won't be able to save your changes. Here's how to troubleshoot any error messages:

Invalid mapping: Not enough parts

This means that you're missing the -> or the redirect type.

Invalid mapping: Too many parts

This means you have more than the four parts of a redirect. Check that you only have:

  • The old URL
  • The arrow: dash and greater than sign with no space between the symbols
  • The new URL
  • The redirect type (301 or 302)

Ensure that nothing is duplicated.

Invalid mapping: expected to find 301 or 302

This means that there's an error in your redirect type. Only 301 and 301 are accepted here.

Check that there are no extra digits or letters in the redirect type.

Invalid Character

The following symbols can't be used in URL redirects:

  • #
  • %
  • ?