The migration preserves the product page path but removes ?variant=blue. The buyer lands on the default product instead of the selected variant. Parameters after ? may store a selected color, catalog page, language, or campaign tag. Removing them all can send some visitors to a different page.
What each parameter selects
When checking a server redirect, account for the actual purpose of each parameter, as indicated by the Location response header—the destination address. Official documentation.
Consider the old address /item/a?variant=blue&utm_source=mail. The first key selects a product variant; the second describes the traffic source. Removing them has different consequences. Add page, language, sort, and signature parameters if the site actually uses them. For each parameter, record what it selects and how it should work on the new site. Do not automatically carry over every parameter after the question mark if the new domain handles it differently. But clearing all parameters to create a single URL can also erase the user’s selection. Make this table before changing the redirect rule.
Product variant, list page, and traffic source tag
| Parameter | What it changes on the page | Keep or remove | How to check the result |
|---|---|---|---|
| ?variant=blue | Selected variant | Keep or map it | Correct product |
| ?page=2 | A different part of the list | Preserve its meaning | Correct page |
| ?utm_source=mail | Analytics tag | Separate policy | Check that the visit is recorded |
| ?token=... | Access or signature | Check requirements | Do not publish the value |
Find where the parameter is lost
First, record the Location value from the initial response, then open the final URL and check the visible result. Client-side code may restore a selection saved in localStorage, so test in a clean session without old settings. Also compare by opening the new address directly. If Location contains variant but the page ignores it, the issue is on the destination side. If the parameter disappears before reaching the destination, check the redirect or an intermediate rule. This helps pinpoint the problem: either the redirect drops the parameter or the new product page does not recognize it. Fix the identified cause, then repeat the same test.
The following terminal command saves the first response so the developer can see where the parameter disappears.
curl -sS -D headers.txt -o response.html 'https://example.com/item/a?variant=blue&utm_source=mail'In headers.txt, check the first response’s Location: was variant=blue preserved, or was it replaced with a corresponding new parameter? Without -L, the response.html file contains the body of the first response. To check the color, open the URL from Location separately in a browser. Replace example.com with your domain; this GET request does not change the site’s settings. curl documentation.
Check Location. If variant is already missing here, fix the redirect rule. If it is still present, open the destination in a private window: the wrong color points to how the new page handles the parameter.
Map old and new names
If the new site renamed variant to color, configure an explicit mapping between the keys and values. For example, blue can map to the internal identifier 12 only after you confirm the lookup table. If the new catalog expects a number, passing blue alone will not select the blue product. If UTM parameters are being removed, document where the source is recorded before they are cleared, if such a process is in place. Tokens and signatures passed between domains must be checked against the requirements of the specific protocol; they cannot be mechanically transferred to another domain. Explicitly specify in the rule which parameters are kept, which are renamed, and what happens to an unknown key.
Check value encoding
Test a space, Cyrillic characters, a plus sign, an ampersand inside an encoded value, and repeated keys. Compare the parsed value before and after, not just the number of characters in the string. Manually building Location by concatenating strings often breaks encoding. Use standard URL mechanisms and check the outgoing response. For signed requests, the exact representation may matter; do not normalize them without the owner’s documentation. In test logs, replace sensitive values with safe placeholders, keeping only the data needed to explain and reproduce the issue.
Check the selected variant without old settings
The blue and red variants open correctly from old links; page=2 does not reset to the first part of the list. Check UTM separately in your analytics. Give the developer example values instead of access tokens.
See also: How to use reChecker to analyze redirects and URL parameters and SEO: filters, UTM tags, and duplicates—how not to ruin indexing. Website checks are available on the reChecker technical audit page.