A list of redirects can fit in a spreadsheet. Its interest does not come from the number of lines, but from the quality of the decisions made for each. During a SEO migration, the correspondence table links an old page to a new destination that meets the same need. Here's how to build and test it without turning all URLs into home shortcuts.
Start with useful pages
Gather the URLs of the sitemap, CMS, Search Console and pages that receive external links or requests. Deduplicate obvious variants, but keep track of old addresses that are actually reachable. A page removed from the menu two years ago can still be visited from an article or an email. Note business pages, articles, downloadable resources and important images.
For each URL, add its function: attract a search, explain a service, sell a product, answer a question or receive a contact. This column prevents you from choosing a destination just because its name resembles the old address. The Google guide to site moves recommends inventorying old URLs and preparing their correspondence.
Use six columns that lead to a decision
Create the columns: old URL, page type, traffic or known importance, new URL, decision, test result. The decision can be “page kept”, “merged”, “replaced with an equivalent resource” or “removed”. Add a comment when the case is not obvious. An old product page that is permanently out of stock can point to a relevant category if it really helps to continue the choice; a completed event page can remain in the archive if it has informative value.
A fictitious example: `/services/creation-site-artisan` becomes `/creation-site-artisan`. The destination still needs to explain the offer and the form. Another old article, `/blog/sites-pour-artisans`, contains advice similar to the new guide; you can merge the two texts and redirect the old URL to the new guide. This decision is editorial before being technical.
Avoiding the pitfalls of automatic rules
A global rule can override a URL prefix, but it can also send products to the wrong categories. Before enabling it, test one page of each template and the exceptions. Verify that redirects are permanent on the server side when the change is final, that they do not loop, and that they lead directly to the correct destination.
Do not confuse “reply 200 after redirect” with “successful migration”. The final address can open while presenting a different offer. Open priority destinations on mobile and ask if the visitor finds the information they were looking for. HTTP codes are necessary, but so is the meaning of the page.
Test before and after going live
In pre-production, check all commercial URLs and a sample of other families. Note the expected code, destination and status of the content. After publication, repeat the tests on the public domain; Rules that worked on a test environment may be overwritten by the actual configuration. Also check internal links so that they point directly to the new URLs.
Keep the table for several months. If Search Console reports an old page not found or a customer reports a broken link, you'll be able to find the original decision. Add the correction and its date. The complete SEO migration checklist replaces this table in the launch of the site.
Include new URLs in the sitemap
The public sitemap should show the canonical pages you want to make discoverable, not all the old redirected addresses. On a platform that generates it automatically, check the result after publication. On a custom site, update the list with actual uploaded content. The Google documentation on sitemaps reminds that a sitemap declaration is not a guarantee of indexing.
To go further, the guide “Audit and correct your site” helps move from observed URLs to prioritized and verified fixes. However, start with the pages that support your requests or sales; a comprehensive table is only useful if it leads to testing.
Frequently asked questions
Should URLs without traffic be put in the table?
Yes if they are still accessible, linked or useful. You can process them after priority pages, but don't make them disappear from inventory.
Is a redirection to the category sufficient for a removed product?
Only if the category really offers a relevant sequel. Review the intent of the old listing and the available alternatives.
Why keep the test column?
It distinguishes the planned decision from what works after it is put online. Note the status, destination and date of the check.
