404 Redirects

Last updated 20 Mar 2018
404 Redirects Overview

When migrating an existing website over to GrazeCart it's possible urls on your old site might not exactly match what is on your GrazeCart site. This can result in old links returning a 404 not found error. Redirects help solve that.

For example, lets say your old site had a store that could be reached at myfarm.com/shop

You decide you want to use your domain (myfarm.com) for your GrazeCart site. The problem is that now the link myfarm.com/shop will return a 404 not found error because by default the /shop page does not exist on your GrazeCart site. 

Redirects allow you to route any incoming traffic to a different url. So using the example from earlier, we could set up a redirect so when someone tries to visit myfarm.com/shop they get redirected to myfarm.com/store which is the url for your GrazeCart store.

Adding a 404 Redirect

You can add redirects from Settings / Redirects

Origin URL 

This is the URL of the incoming traffic. You should not include the full domain of the incoming URL. Only include the relative path, which is the part that comes after the domain. So based on the example from earlier the Origin URL would be /shop.

Destination URL

This is the URL you want to redirect to. If you want to link to a page on your GrazeCart site you don't have to include the domain. So based on the example from earlier the Destination URL would be /store

Status Codes

301 (Permanent) - Typically you will use this option. This will let search engines like Google know to stop indexing the old url and start indexing the new one.

302 (Temporary) - Not as commonly used. Only use this option if you plan on only temporarily having a redirect. This might be useful for testing purposes.

Redirecting to Other Websites

If you want to redirect to an external URL you must prepend it with the http protocol. For example if you wanted to redirect to GrazeCart.com the Destination URL would look like this: https://grazecart.com