URL Normalizer
Normalize URLs so that equivalent links look identical. Lowercase the host, sort query parameters, drop fragments and trailing slashes, remove www and force https.
Normalize URLs so that equivalent links look identical. Lowercase the host, sort query parameters, drop fragments and trailing slashes, remove www and force https.
The same page can be written many ways: different capitalisation, a trailing slash, parameters in another order, an anchor. When you compare or deduplicate URLs, those differences get in the way.
This tool applies the normalisations you choose so equivalent URLs end up identical.
Input: HTTP://WWW.Example.COM:80/a/b/?z=1&a=2#frag Output: https://example.com/a/b?a=2&z=1
URL normalization turns different spellings of the same address into one canonical form. RFC 3986 defines safe normalizations: scheme and host are case-insensitive, so HTTP and EXAMPLE.COM can be lowercased, and default ports such as 80 for http and 443 for https can be dropped. Paths, by contrast, are case-sensitive on many servers, so this tool does not change path case. Other steps, such as sorting query parameters, removing a trailing slash or dropping www, are practical conventions rather than guarantees of equivalence.
Those convention-based steps explain why each is an option. A trailing slash can mean a directory on some servers, and a handful of sites serve different content on www and non-www hosts. Parameter order rarely matters but occasionally does for signed URLs. Removing the fragment is safe for server requests, yet single-page apps sometimes use it for routing. When normalizing for deduplication, apply the same options to every list you compare, otherwise equal URLs may still differ.
The fragment (after #) is never sent to the server, so removing it does not change which page loads, though it can change where the browser scrolls.
Usually not, but a few sites care about order. Leave it off if you are unsure.
Most sites serve the same content with or without www, but not all. Check before applying it to a site you do not control.
They are left unchanged and counted in the note.
No. Only the host is lowercased. Paths and query values stay as written because many servers treat them as case-sensitive, and changing them could point to a different resource.
Consistent URLs make duplicate detection and log analysis easier. For search engines, you still need canonical tags or redirects, since this tool only rewrites text and does not change your site.