First, the site moved from /catalog/a to /shop/a, then to /products/a. The old rules remained, so users go through two redirects. Shorten the chain using the mapping: a direct redirect is useful only when the destination page genuinely replaces the original.
Map the paths from both migrations
Permanent server redirects tell Google that a URL has moved. Official documentation.
Find the mapping from the first migration and the mapping from the second. If there are no documents, use saved routes, redirect settings, and confirmed old links. Do not reconstruct the mapping based only on a similar part of the address: a service may have been merged with another, or a product may have been removed. For each old URL, record the intermediate page B and the current page C. Ask the catalog owner to confirm that C replaces the old page. For example, /products/a should show the same product, not an unrelated category. Only then redirect A straight to C.
Which redirects to keep
| Redirect path | Where the extra hop was introduced | What to change | Expected redirect |
|---|---|---|---|
| A → B → C | Two migrations | Change to A → C | Confirm that C is relevant |
| B → C | Second migration | Keep the rule | Check the direct redirect |
| A → B → 404 | No destination page | Find a suitable equivalent | Do not shorten it to an error |
| A → C in another language | Destination changed | Correct the mapping | Check the language |
Find a chain or loop
Record the response headers and the address of the next redirect from Location for each response. If an address repeats, you have a loop, not just a long chain. If the path stays the same but http and https or www and non-www alternate, check the infrastructure rules separately from the content migration. Ask a developer to compare a regular page request (GET) with a browser where cookies preserve the user's previous choice. A message about exceeding a limit does not explain which rule is incorrect. Give the developer a list of addresses and Location values. Using the logs and settings, they can determine which redirect is issued by the content delivery network (CDN), web server, or content management system (CMS).
To record the redirect chain for an old product page, run this in a terminal or give it to a developer:
curl -sS -L --max-redirs 10 -D headers.txt -o response.html 'https://example.com/catalog/a'All responses in the chain are recorded consecutively in headers.txt. For each redirect, note the status and Location, then the final address. The contents of response.html will help confirm that you reached the right product page, not the general catalog. Replace example.com with your domain; this GET request does not change the site settings. curl documentation.
Check the addresses of both previous sites
Choose two old pages and their versions after both migrations. For one, check a product variant parameter, such as variant=blue; for the other, check a language prefix or nested path. First record the current A → B → C, then add the A → C rule on a test copy. Repeat by opening A, B, and C directly. Checking only A will not show whether B still works. Also check an unknown old path so the new regular expression rule does not send all missing pages to an unrelated destination.
Redirect old paths straight to new ones
Change the first historical rule so that it points to the confirmed current address. Keep B → C for the second migration period. Take web server rule order into account: a general rule may intercept an exact exception or add the intermediate domain again. Check the outgoing Location, not just the configuration text. If the redirect is configured both on the CDN and in the CMS, keep the page migration in one place. Before making a bulk change, save the configuration so you can restore the previous rules if something goes wrong. Do not remove redirects from other migrations.
Update the menu and sitemap
After the migration, the menu, product pages, and sitemap should use C directly. The canonical for C should not continue to point to B. Check hreflang tags and links from important old posts if they are part of the current interface. You do not control saved external links through your menu, so redirects are still needed. After changing a redirect, check the new links in the menu, product pages, and breadcrumbs. Otherwise, the site will continue sending visitors to A even though they could go straight to C. Find the template setting that generates the old addresses.
Open A, B, and C separately
A and B should each redirect straight to a suitable C; C should open without a redirect and return the correct page. Checking a URL with a language or variant shows whether the selection was preserved. A repeated URL in the headers indicates a remaining loop.
See also: Checking redirects when moving to a new domain and Redirects in SEO: a complete guide to setup and optimization. Site checks are available on the reChecker technical audit page.