A redirect opens the new search page, but the results are empty. The query may have been lost along the way even though the destination looks correct.
Follow a harmless example query
Fictional example: the old search uses /search/?term=lamp, while the replacement expects /search/?q=lamp. Redirecting only to /search/ removes the state. Preserving term unchanged also fails if the new application does not read that name.
Use a fictional, non-personal phrase to inspect the original request, the Location value and the final selection. Record which parameter actually controls search.
Not every old parameter should survive. Session keys and other sensitive values must not be copied blindly into new URLs or logs.
Translate known names deliberately
Define which parameters the new system accepts and how their values are encoded. Include a space and an accented character in the check. Repeated decoding or simple string concatenation can change the query.
The destination should show the intended search and make its current state clear. Check browser Back as well. Raw search phrases do not belong in analytics or publicly shared issue lists. Parameter names and non-personal example values are enough for the technical handover.
Related check: Prioritise a redirect mapping.
Once parameter mapping in the existing frontend is defined, you can request its correction through Frontend optimisation.