URLs ?brand=a&size=42 and ?size=42&brand=a may show the same results, but the content management system (CMS) keeps both in internal links. Compare the products and selected filters at both URLs. Before sorting query strings, check repeated parameters and digitally signed links separately: how they are handled depends on the application.
First, compare the products at both URLs
Google recommends aligning the declared canonical with other signals, including internal links. Official documentation.
A URL with two reordered parameters is not yet a proven duplicate. In some applications, the first or last repeated key determines the result. Start with two simple URLs and compare the interface state, products, result order, and number of results. Then repeat the test with the same authentication and language. If the responses differ, find out whether that difference is expected. You can choose one parameter order after confirming that reordering does not change the products or selected values. A standalone filter may also retain its own URL, even if its parameters can be reordered.
Which parameters need to be preserved
| URL parameters | What they define | What can change | What must be preserved |
|---|---|---|---|
| ?brand=a&size=42 | Two filters | Compare with the reordered version | The same state |
| ?size=42&brand=a | The same two filters | Choose one consistent order | One selected canonical |
| ?tag=a&tag=b | A repeated key | Check how multiple tag values are handled | Do not sort blindly |
| ?page=2&brand=a | A different part of the catalog | Preserve the page number | Do not treat it as the first page |
Compare the server URL with the browser URL
Ask a developer to compare the server response to a standard page request (GET) with the result after scripts run. The browser history may replace the URL after loading through history.replaceState, while the server continues to serve a different version at the original URL. Record the original URL, final URL, HTTP status, and canonical before and after JavaScript runs. If a CDN—the network that delivers pages and files—changes the URL, ask the developer to compare the CDN response with the website server response. Use the CDN's standard diagnostic method. A random parameter used to bypass the cache may show a different page, so that response must not be substituted for a regular check.
Open the relevant page and run this in the browser console:
[...document.querySelectorAll('link[rel="canonical"]')].map(el => ({
записано: el.getAttribute('href'), адрес: el.href
}));The two reordered parameters should produce the same full canonical. The selected brand and size should also remain unchanged. Compare the console result with “View page source”: if the server outputs different tags, replacing the URL through JavaScript has not fixed the problem. Multiple lines in the array mean that canonical is output more than once.
Check repeated keys and Cyrillic characters
Ask a developer to test tag=a&tag=b, an empty size=, a value containing a space, and a Cyrillic brand. The JavaScript URLSearchParams method is convenient for parsing, but it does not decide for you whether repeated values can be reordered. Signed links are particularly sensitive to transformations: their validator may check the exact string representation. Keep the original string and the result in a test table, then compare their meaning, not just how the URL looks. The encoding check should show that the value selected by the user does not change or become two separate parameters.
Fix the link generator
Ask a developer to use one URL-building function in the menu, filters, and sitemap. Define the order of known keys, how empty values are handled, and how significant exceptions are preserved. The canonical output should use the selected result. A redirect does not have to be applied to every variant: choose where the server should actually change the URL and equivalence has been proven. Then check that the menu and filter no longer create non-normalized variants. If you change only canonical, the filters will continue to create two URLs for the same set of products.
How to check that the filters are preserved
Open both reordered URLs in a new private window. They should show the same products and the selected canonical. The URL with page=2 shows the second part of the list. A saved link with repeated tag values should restore the previous set of values.
Read also: URL parameters and SEO: filters, UTM tags, and duplicates—how not to ruin indexing and Duplicate content: how to find and fix it with canonical. Site checks are available on the reChecker technical audit page.