Separate address, query and fragment
A URL may contain a protocol, domain, path, query following ? and fragment following #. Query pairs are separated with &. Values containing these characters need a representation that does not confuse them with structural separators. Editing a path segment and adding a query parameter are different operations.
Build URL accepts an HTTP or HTTPS address without credentials and one name=value parameter per line. It does not visit the address. Enter unencoded values because the tool prepares their representation. Start with a sample address and two simple parameters before constructing a longer link containing many options, so you can inspect the basic behavior first.
Retain, replace and repeat parameters deliberately
Keep existing parameters appends new pairs to the current query. Replace removes the entire old query before adding new pairs, rather than replacing only a matching name. If you add tag=a and tag=b as separate lines, both remain. Destinations can interpret repeated names differently, so inspect the receiver’s requirements when they matter.
The fragment field replaces the old fragment; leaving it empty removes that fragment. Review this setting even when your task focuses on the query. The first equals sign divides a name=value line, and later equals signs belong to its value. Keep the original address to compare the specific parts changed by construction.
Understand spaces, plus signs and encoding
Analyze URL parameters interprets + as a space in queries and %2B as a literal plus. It retains order and repeated names as a list of pairs. For example, q=hello+world&sign=%2B returns hello world and + as values. This makes it useful for reviewing how query text is interpreted.
Encode and decode URL offers component and complete URL modes. Use component for an isolated value, and complete URL to preserve structural separators. Its decoder preserves + as + and is not a form-query analyzer. Choose by input type rather than expecting every decoder to follow the same rule for a plus sign in the supplied text.
Check the constructed link before using it
Build the link, copy its output and paste it into Analyze URL parameters. Compare each name and value with the original entries. A typed space should return as a space, while a literal + should return as +. Entering pre-encoded %20 into the builder encodes the percent character rather than reinterpreting that sequence as a space.
Check path, protocol and fragment too. These tools do not establish that an address exists or that its destination accepts the parameters. Save the output before changing fields and check behavior in the intended service when your task requires verification beyond the local construction and parsing steps.
Build and parse again
In Build URL, use the given address, keep existing parameters and enter the three unencoded rows. Set Fragment to result. Generate and copy the output into Analyze URL parameters.
URL: https://example.com/?tag=a#before Parameters: q=hello world sign=+ tag=b Fragment: result
The URL is https://example.com/?tag=a&q=hello+world&sign=%2B&tag=b#result. Analysis returns tag=a, q=hello world, sign=+ and tag=b in that order.
Check both tag entries and verify that + remained distinct from a space. Replacing parameters removes the old tag=a, and leaving Fragment empty removes #before.