URL Parser

A URL has a scheme, a host, an optional port, a path, a query string, and an optional fragment after a hash. Query parameters are key-value pairs. Parsing shows those pieces without loading the page.

What you get from URL Parser is concrete. The parts of the URL are shown separately instead of as one line. Each query parameter gets its own key and value row. The address is not requested. Read those results before you paste them into a template, a file, or a ticket. A copied mistake is harder to see later than a mistake still on this page.

A careful pass on URL Parser looks like this. Start with real input, not a placeholder you do not understand. Paste a full URL, including the protocol. Then check the middle of the form, because that is where optional fields change the output. Read the protocol, host, path, and hash. Finish by reading the whole result, not only the first line. Read the query parameter table of keys and values.

The limit is the part people skip on URL Parser. Match the output to the input you actually typed, then decide whether it belongs on the live site. The parameter table says no query parameters were found. Each query parameter gets its own key and value row.

A second reading of URL Parser is worth it because the first pass is easy to rush. Say out loud what the output is claiming. The parts of the URL are shown separately instead of as one line. Each query parameter gets its own key and value row. The address is not requested. Then say what it is not claiming. No. It only splits the string you paste. The parameter table says no query parameters were found. Protocol, host, port, path, query keys and values, and the hash fragment. If those two speeches disagree, change the input or pick a different tool. URL Parser will not resolve the disagreement for you.

Read URL Parser once more as a single job. Part 1: Paste a full URL, including the protocol. Part 2: Read the protocol, host, path, and hash. Part 3: Read the query parameter table of keys and values. You should be able to point at this in the result: The parts of the URL are shown separately instead of as one line. You should be able to point at this in the result: Each query parameter gets its own key and value row. You should be able to point at this in the result: The address is not requested. Does the parser open the URL? No. It only splits the string you paste. What if there is no query string? The parameter table says no query parameters were found. Which pieces are labeled? Protocol, host, port, path, query keys and values, and the hash fragment. Who is URL Parser for? URL Parser is for someone already doing link tools work who needs break down any URL into its protocol, host, path, and parameters. A URL has a scheme, a host, an optional port, a path, a query string, and an optional fragment after a hash. Query parameters are key-value pairs. Parsing shows those pieces without loading the page. The first field was filled with a real value: Paste a full URL, including the protocol. The result was read: The parts of the URL are shown separately instead of as one line. Optional fields were either filled or left empty on purpose. The copy went into the place the last step names. The boundary in the guide was respected before anything was published.

Keep URL Parser as this step only. When the job moves on, the UTM Builder is the next page: UTM Builder adds campaign parameters to a website URL. The URL Encoder/Decoder covers a different piece of the same work: URL Encoder/Decoder turns a string into percent-encoding or turns an encoded string back into readable text.