Home / Compare URLs
Compare URLs side by side
Put two URLs next to each other and see every part that differs, whether they normalize to the same address, and where each one actually ends up on the live web.
Different URLs, probably the same page. They differ only in protocol, www, trailing slash, tracking parameters, parameter order or fragment. Pick one form and redirect the other to it.
| Part | URL A | URL B | Same? |
|---|---|---|---|
| Scheme | http | https | differs |
| Host | Example.com | www.example.com | differs |
| Port | — | — | same |
| Path | /mugs/blue | /mugs/blue/ | differs |
| Query | color=navy&utm_source=mail | color=navy | differs |
| Fragment | — | — | same |
| ?color | navy | navy | same |
| ?utm_source | — | differs |
"Equivalent" means the raw text differs but RFC 3986 normalization makes it identical (case in the host, default port, percent-encoding, dot segments).
When comparing URLs helps
- Search Console says "Duplicate, Google chose different canonical": put your URL next to Google's choice and see what separates them.
- Migration QA: check that the old and new URL land on the same final page.
- Analytics splits one page in two: find the stray slash, capital letter or parameter.
- hreflang or canonical mismatches: a tag that is "almost" right is still wrong.
What counts as the same URL
To a server, /Mugs and /mugs are different paths, and so are /mugs and /mugs/. The scheme and host are case-insensitive; the path and query are not. Fragments (#reviews) are never sent to the server at all. The URL normalizer walks through each rule.