LSI Keyword Extractor
Pull the related phrases a piece of content actually uses.
Break any URL into its parts, query string included.
The URL Parser splits any address into its parts — protocol, subdomain, domain, suffix, port, path segments, every query parameter on its own row, and the fragment — with percent-encoded values decoded so you can read what is really in them. It also flags the malformations that quietly create duplicate URLs.
Paste a URL and every part of it is separated out: protocol, subdomain, domain, top-level domain, port, path segments, each query parameter as its own row, and the fragment. Percent-encoded values are decoded so you can read what is actually in them.
This is a debugging tool more than an SEO one, but the SEO uses are real. A URL with fourteen query parameters is a URL that generates fourteen factorial variations for a crawler to discover. A path with an encoded space, a double slash or a stray semicolon is a URL that exists twice as far as an index is concerned. And when a tracked link is not reporting, the fastest way to find out why is usually to look at what is genuinely in it rather than what you think you put there.
Including the subdomain and public suffix split, which the browser's own URL object does not give you.
Each key and value on its own line, decoded, so a long query string becomes readable.
The same parameter twice is legal and handled differently by every server, so both are listed.
Encoded spaces, double slashes and stray characters that create a second URL for one page.
Paste a list and every URL is parsed into the same table.
One, or a list of them. Bare hostnames get https added so they parse.
Protocol, host, path and fragment, with each query parameter on its own row.
Percent-encoded values are shown decoded alongside the raw form.
Double slashes, encoded spaces and duplicated parameters are flagged.
Protocol or scheme (https), then host (which splits into subdomain, domain and top-level domain), an optional port, the path, the query string after the question mark, and the fragment after the hash. This tool labels each one.
No. Everything after the # stays in the browser and is never sent in the request. That is why a fragment cannot be read server-side, why analytics needs JavaScript to capture it, and why Google generally treats a fragment URL as the same page.
Not in themselves. What causes trouble is parameters that produce the same content at many URLs — filters, sort orders, session IDs — because each one is another URL to crawl and another candidate to be indexed. Canonicals are the usual fix.
It is legal in a URL and each server handles it differently: some take the first value, some the last, some collect both into an array. It is almost always a bug in whatever built the link, and this tool shows both occurrences rather than quietly collapsing them.
What people who use the URL Parser think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
0 reviews
Newest first
No reviews yet
Be the first to rate the URL Parser. It takes half a minute and no account.
Write the first reviewPull the related phrases a piece of content actually uses.
Build a complete set of meta, Open Graph and Twitter card tags.
Turn a list of old and new URLs into Apache redirect rules.
Turn one image into every favicon size, plus the markup.
Build Article, NewsArticle or BlogPosting JSON-LD in one pass.
Compare two pages and find the passages they share.
Tag hundreds of links at once and export them as a spreadsheet.
Dates, venue, tickets and status as Event JSON-LD.