URL Parser
Break a URL into its component parts.
URL components
- Protocol
- https: The scheme, including the trailing colon.
- Hostname
- shop.example.com The domain, without the port.
- Port
- 8443 Explicit port — blank when the scheme default is used.
- Origin
- https://shop.example.com:8443 Scheme plus host — the security boundary.
- Path
- /catalog/shoes The path after the host.
- Query string
- ?color=blue&size=10&utm_source=newsletter Everything after the ? character.
- Hash
- #reviews The #fragment — never sent to the server.
Query parameters (3)
| Key | Value | Copy |
|---|---|---|
| color | blue | |
| size | 10 | |
| utm_source | newsletter |
https://shop.example.com:8443/catalog/shoes?color=blue&size=10&utm_source=newsletter#reviewsHow to use URL Parser
What this tool does
The URL Parser takes any web address and breaks it into its component parts: the protocol, hostname, port, origin, path, query string and hash fragment. It also expands the query string into a clean table of key/value pairs so you can read every parameter at a glance. The breakdown updates live as you type, every part has its own copy button, and an invalid URL produces a clear inline message instead of an error. A sample URL with query parameters is loaded by default so the tool is useful immediately.
All of it runs locally. The parser inspects the text you paste — it never fetches the page or contacts the server behind the URL.
Why it matters for SEO
URLs are full of signals, and being able to read them precisely is a core SEO
skill. Query strings are where duplicate-content problems hide: a page reachable
at ?sort=price, ?sort=price&page=2 and ?utm_source=email is one page that
search engines may see as several, splitting ranking signals across near-identical
variants. Parsing a URL shows you exactly which parameters are present so you can
decide which ones need a canonical tag, which should be disallowed in robots.txt,
and which are harmless.
It is also the fastest way to audit tracking. UTM parameters, gclid, fbclid
and other click identifiers ride along in the query string; seeing them listed
plainly helps you confirm campaign links are tagged correctly and spot stray
tracking codes that are leaking into indexed URLs. Checking the protocol
confirms HTTPS, and reading the path confirms your URL structure is shallow and
readable.
How to use it
- Paste a URL into the input box, or keep the sample that is loaded by default.
A scheme-less host such as
example.com/pageis accepted. - Read the URL components panel: protocol, hostname, port, origin, path, query string and hash, each with a one-click copy button.
- Scan the Query parameters table — every key and its decoded value is shown on its own row, with a copy button for each value.
- If the URL is malformed, an inline message explains what to fix. Use Load sample to restore the example or Clear to start fresh.
SEO best practices
Keep URLs short, lowercase and descriptive, with words separated by hyphens and
a shallow folder depth. Reserve the query string for genuine parameters and
keep tracking codes off any URL you want indexed — put campaign-tagged links in
emails and ads, not in your sitemap or internal links. When parameters are
unavoidable, use a self-referencing canonical tag so search engines consolidate
the variants, and configure crawl rules deliberately rather than letting every
combination get indexed. Prefer a consistent host: pick www or non-www,
pick HTTPS, and redirect the alternatives.
Common mistakes to avoid
Do not let infinite parameter combinations — sort orders, filters, session IDs,
pagination — generate a crawlable maze of near-duplicate URLs. Avoid uppercase
letters and spaces in paths, since URLs are case-sensitive after the host and
spaces encode as ugly %20. Do not rely on the hash fragment for content you
need indexed, because servers and many crawlers never see it. And do not
confuse the origin with the hostname when reasoning about security or
analytics — the port and scheme are part of the picture.
Privacy & your data
The URL Parser is completely client-side. The address you paste is broken apart
by JavaScript using the browser’s native URL object, the same parser the
browser uses for real navigation. Nothing is uploaded, the page behind the URL
is never requested, and no history of what you parse is kept. When you clear the
box or close the tab, the data is gone. That makes it safe to inspect internal
URLs, staging links and campaign URLs that are not public yet without any of it
leaving your device.
Frequently asked questions
What is the difference between a URL's origin and its hostname?
Why does the parser show no port for most URLs?
What are tracking parameters in a query string?
Is the fragment (the part after #) sent to the server?
Does this tool send the URL anywhere?
Related tools
UTM Link Builder
Build campaign-tracking UTM links.
Canonical URL Builder
Build canonical URL tags to avoid duplicate content.
URL Encoder & Decoder
Encode and decode URL-safe text.
Slug Generator
Generate clean, SEO-friendly URL slugs.
Placeholder Image URL Builder
Build placeholder image URLs for mockups.
Robots.txt Generator
Build a robots.txt file with common crawl rules.