Use the exact source ?q=blue+shoes&tag=sale&tag=new&empty= and select the form profile. The leading question mark is accepted but is not a pair. Four non-empty segments remain, and the plus in the first value becomes one space. Write down the selected profile and compare the source, decoded rows and canonical query together. That evidence makes a later mismatch reproducible without pretending that this parser defines how every server, framework or signature system will interpret the same bytes.
Verify all four ordered rows
The decoded rows are q → blue shoes, tag → sale, tag → new and empty → an empty string. Every segment includes an equals sign. The table keeps both tag rows separately and places empty last, matching the source rather than a sorted key order. Keep duplicate names as separate ordered rows until the receiving application states its own policy. Converting early to a plain object can discard values, change their order or hide whether a parameter appeared without an equals sign in the original query.
Check pair and repetition counts
The evidence shows four pairs, three unique decoded names and one repeated distinct name. Repeated-name count is not the number of extra rows: tag occurs twice but contributes one repeated name. This definition stays stable when a name appears three or more times. A successful decode only establishes the text produced by these explicit rules. It does not validate a destination URL, authorize a redirect, verify a signature, detect an attack or prove that another implementation applies identical limits and error handling.
Compare canonical form and ordered JSON
The canonical query is ?q=blue+shoes&tag=sale&tag=new&empty=. Ordered JSON contains four objects in the same sequence, including the empty value. Copy either artifact only after confirming form profile, because component profile would preserve the plus and produce different decoded evidence. QueryLens performs the transformation locally and sends no query content to a product backend. Still review copied output before reuse: encoded data can contain identifiers, search terms or other sensitive text, and the destination remains responsible for validation and access control.