When to use the URL Parser
Checking campaign links
See every UTM tag in a marketing link before you publish it in an ad or newsletter.
Debugging redirects and APIs
Split callback URLs into parts to find a wrong path, port or parameter.
Removing tracking codes
Spot fbclid, gclid and other tracking codes to share a cleaner link.
Learning how URLs work
See exactly which part of an address is the host, path, query and fragment.
Features and benefits
- Protocol, host, port, origin, path and fragment
- Decoded query parameters in a table
- Detects utm_*, gclid, fbclid and similar tracking codes
- Uses the browser’s standard URL parser
Example
https://shop.example.com/shoes?color=red&utm_source=news#reviews
Host: shop.example.com · Path: /shoes color = red · utm_source = news (tracking) · Fragment: reviews
How the URL Parser works
ConvertNest passes your address to the browser’s built-in URL parser – the same code that powers the address bar – so the result follows the official WHATWG URL standard. It shows each part separately, decodes the query string into a table of keys and values, and highlights parameters commonly used for tracking. The URL is never opened or requested.
A real-life example
A marketing assistant is about to send a newsletter, and analytics later shows all clicks as “direct”. Pasting the link into the parser reveals utm_source=newsletter but utm_medium is spelled “utm_meduim” and the campaign value contains a space. She fixes both, re-checks the table, and the next campaign’s clicks are reported correctly.
Good to know
URLs collect extra baggage as they are shared: campaign codes, click IDs and redirect parameters. Breaking a URL into parts shows what is essential and what is just tracking.
Parsing uses the same WHATWG URL standard as your browser, so host names, ports and encoded characters are interpreted exactly as a browser would.
Tips for the best results
- Paste the full address including https:// for the most accurate result.
- Check that UTM values are consistent in lowercase across all your campaigns.
- Use the URL Decoder if values contain many percent codes.
- Remove tracking parameters before sharing links publicly if you prefer cleaner URLs.
- Compare two versions of a link side by side in two tabs to spot which parameter changed.
Common mistakes to avoid
Leaving out the protocol
Without https://, the text cannot be parsed as an absolute URL.
Putting the fragment before the query
Everything after # is the fragment; parameters after it are not sent to the server.
Mixing upper and lower case UTM values
Analytics treats Newsletter and newsletter as different sources.
URL Parser – frequently asked questions
What are UTM parameters?
Tags such as utm_source and utm_campaign added to links so analytics tools can attribute visits. They are safe to remove when sharing a link.
What is the fragment?
The part after #. It points to a section of the page and is not sent to the server.
Why does it show a default port?
If no port is written, https uses 443 and http uses 80.
Is the URL visited or checked?
No. The URL is only analysed as text in your browser.
What is the origin of a URL?
The protocol, host and port together, such as https://example.com. Browsers use it for security rules.
Can I parse URLs with non-English domains?
Yes. International domains are shown in their punycode form, which is how they are used on the internet.
What is the difference between the host and the hostname?
The hostname is just the domain, such as shop.example.com. The host adds the port when one is written, such as shop.example.com:8080.
Why do some links have both ? and # parts?
The query (after ?) is sent to the server to choose content; the fragment (after #) stays in the browser and usually jumps to a section of the page.
Is it safe to paste a link with a password reset token?
The link is only parsed in your browser and never visited or stored, but avoid sharing such links with anyone, as they grant access to your account.