301 redirects: prepare a plan without losing useful pages

SEO technical · 6 min reading

To prepare a 301 redirection plan, start from the old URLs and give each URL an explicit decision: keep the page, move it to equivalent content, merge its content, or delete it without replacement. Then test the destinations and server responses. The decisive point is not to redirect all addresses, but to preserve access to information that is still useful.

Key points

• A 301 redirection corresponds to a permanent move, not to temporary unavailability.
• The destination must meet the same need as the old page.
• A deletion without equivalent content may warrant a 404 or 410 response.
• The plan must include the links to update and the tests to perform.

Inventory URLs beyond visible pages

Export the addresses from your CMS, then complete this list with sitemaps, known pages in Search Console and, if you have access, server logs. A browse of the site identifies the pages linked to each other, but may miss an old file still consulted from an external link.

These additional sources are recommended in the Google migration guide. Also think about PDFs, product guides and old categories. A notice may remain useful to owners of a product that is no longer sold.

Don't rank pages solely by their traffic. Note their function: present an offer, explain compatibility, provide documentation or direct you to a service. A rarely visited page can prevent a wrong order. Also check addresses used in advertisements, commercial messages and printed materials.

Build the redirection plan 301

A table that allows you to decide and test

Use one line per old URL. Provide the following columns: old address, role of the page, decision, possible destination, reason, validation manager and test result. Separate validated decisions from matches that are still uncertain.

For lasting change, Google recommends a permanent server-side redirection; the codes 301 and 308 indicate this movement. A temporary situation is a temporary redirection. This distinction appears in its documentation on redirects.

Choose a destination according to the reader's needs

Read both pages before validating their correspondence. A close title is not enough: the expected information must be present on arrival. Several old pages can join a common page if it really contains their useful content.

However, do not return all deleted pages to the home page. Google specifies that an unrelated destination can confuse visitors and be interpreted as a “soft 404”, that is to say a page assimilated to an absence of content despite its technical response.

Illustrative example: a renamed category and a discontinued product

In this fictitious example, a store reorganizes its kitchen equipment catalog. The “coffee accessories” category becomes “coffee preparation” and retains the same uses. The redirection from the old category to the new one is consistent.

A stopped mill sheet still contains its instructions and compatible part references. The store decides to keep this page with clear information about the end of the sale, rather than sending visitors to all the available mills.

An old promotion, without a replacement offer or useful documentation, is deleted. The server returns a 404 or 410 response, as specified in Google for untransferred content. The plan therefore distinguishes between movement, conservation and deletion instead of applying a single rule.

Control the result, not just the configuration

A rule saved in a tool is not proof of operation. Check the HTTP response of the old address, the announced destination and the final response. For a moved public page, check for a 301 or 308 response to the old address, then a 200 response to the final destination, without unnecessary looping or intermediate redirection.

Also test the content: a destination can work technically while displaying the wrong language, an empty category or a form without documentation. Check which variants are actually used, including addresses with parameters. Do not automatically delete a setting that determines a product or variant.

Google recommends pointing directly to the final destination rather than creating strings. Also update internal links and sitemap to new addresses. In the case of a migration, check that the canonical URL indications, which designate the preferred version, correspond to the chosen destinations. Also check that new pages intended for indexing do not retain a crawl block or a noindex instruction from site preparation.

Operational checklist

1. Gather old URLs and identify their still useful uses.
2. Assign a decision to each line, with an understandable reason.
3. Have correspondence validated by the person who knows the offers.
4. Check that each destination is accessible and contains the expected information.
5. Test HTTP codes, final destinations and possible loops.
6. Update internal links, sitemap and controlled commercial links.
7. Keep the table and organize a check after activation.

Limitations and common errors

Automatic rules become risky when the structure of old and new addresses differs. A rule based on a URL pattern must be tested on its exceptions. Implementation depends on the server and CMS: this table does not replace technical validation.

Correct redirection does not guarantee immediate stability of search results. Google indicates that visibility may fluctuate during a migration. Also avoid deleting redirects as soon as new pages appear: old links may still be used.

Frequently asked questions

Should we redirect each deleted page?

No. Redirect if a relevant destination picks up the need or content. Without proper replacement, a 404 or 410 response may be preferable to a misleading arrival.

How long to keep redirects?

For a migration, Google recommends keeping them for as long as possible, usually at least a year. This is a documented recommendation, not an automatic deletion deadline.

Can we redirect a product pages to a category?

Only if this category constitutes a relevant answer. If the visitor is looking for instructions or specific compatibility, the category does not replace the file.

Next step: validate uncertain matches

Start with URLs that change and whose destination is debated. Have their content reread together by business and technical managers. If outside help is needed, consult the 4SYSTEM services by preparing this table, rather than a general correction request SEO.

Sources and resources

• Google Search Central: redirects and search Google. Redirection types and server-side implementation.
• Google Search Central: migrate a site. Inventory, matches, deletions, testing and retention of redirects.