Redirect old URLs with 301

Help visitors and search engines get from an old address to the correct replacement page.

This guide applies to store administrators in Go, Plus, and Pro, for example, when changing platforms or product addresses. You need control over the old domain and a working destination URL. A redirect does not replace a missing product or an incorrect domain connection.

1. Choose between a new address and truly deleted content

A 301 is a permanent redirect. Use it when content has been moved or a relevant replacement page fulfills the same need. Check that the destination URL works and is in the correct language.

When you change a product's or product group's file name, its previous address may automatically redirect to the new one. Try the old address before ordering an extra manual redirect.

If content has disappeared without a relevant replacement, a proper 404 page may be appropriate. Do not routinely redirect all missing pages to the home page. Google may treat an irrelevant redirect as a soft 404 error; this does not mean that the entire store is penalized or removed from search results.

2. Prepare a list for import

Create a spreadsheet with three columns:

1. Old domain without the protocol, for example, www.exempel.se.
2. Old path with a leading slash, for example, /gammal-produkt.
3. New full URL, for example, https://www.exempel.se/ny-produkt.

Use the example file for redirects as a template and send the completed list to customer service for review and import.

Check parameter-based old addresses first. Addresses like /product.asp?pid=55849 and /product.asp?pid=56402 have the same path. The standard redirect import does not distinguish them by the query parameter. Therefore, do not order one row per product and assume they will have different destinations. Ask customer service to assess such a move before the import is performed.

3. Single manual redirect

The technical method uses Abicart's API console and requires administrator permissions. If you do not work with the API console, customer service can help you from the reviewed list.

1. First, check if the old address already displays content or redirects. Also, check the new full address.
2. Only open Abicart's official API console. Log in with Admin.login("username", "password") using your own account and use the returned authentication in the console's Auth field. Do not share passwords or authentication codes in messages or screenshots.
3. For an old address that is not already taken by another page, use Url.redirect("https://www.exempel.se/gammal", "https://www.exempel.se/ny") with your verified addresses.
4. A response {} indicates that the call was accepted. Then check the old address in a new browsing session.

For Forbidden: check permissions, the correct store/domain, and if the source address already belongs to some content. Do not delete a working product or page just to get past the error. First, investigate if automatic address history or another redirect is already in effect.

4. Check the final result

Test both the old and new addresses with the correct protocol, domain, and language. Verify that the redirect goes to the intended page, without loops or unnecessary chains. Browsers can cache permanent redirects; use a new browsing session for troubleshooting. Also, update internal links to the new address instead of letting them go through a chain.

A redirect does not guarantee an unchanged search ranking. Monitor Google's crawling and indexing separately.

Quick start

1. Check if an automatic redirect is already working.
2. Choose a relevant, working destination and check parameter-dependent addresses.
3. Prepare the import list or create a single redirect using an account with the required permissions.
4. Test the actual old address and correct internal links.

Subscription

Custom URLs and redirect management can be used in Go, Plus, and Pro. API actions require the correct permissions and domain connection; customer service handles the described import.