URL Parser

Break URLs into their parts and flag the pieces that cause duplicate pages.

One per line.

100 runs left today · sign up for more

About this tool

Paste URLs, one per line, and see each broken into scheme, host, path, query and fragment, with every query parameter listed separately.

The value is in what falls out. A tracking parameter turns one page into two as far as a search engine is concerned. An uppercase letter in a path is a different resource on most servers. A session id in a link is a security problem that also gets indexed.

Common questions

Why do tracking parameters matter for SEO?

Because ?utm_source=newsletter creates a second URL serving identical content. Search engines may index both, split the signals between them, and pick whichever they prefer. A self-referencing canonical pointing at the clean URL is the usual fix.

Does capitalisation in a URL matter?

In the path, yes on most servers — /Page and /page are two different resources on Linux. The domain is always case-insensitive. Mixed case in paths is a common source of accidental duplicates.

What about the fragment after #?

It never reaches the server, so it cannot change what is returned. Search engines generally ignore it, which means #section-two is not a separate page and cannot be indexed as one.

Should URLs end with a trailing slash?

Either is fine; being consistent is what matters. /about and /about/ can serve as two URLs, so pick one and redirect the other rather than letting both answer.