Reading and Auditing URL Parameters
Paste a URL and this tool splits its query string into a table of decoded key-value pairs. Percent-encoding is resolved, so a value like %20 appears as a space and nested URLs become readable.
Query strings are easy for machines and awkward for people. A URL with six parameters, some of them encoded, is a wall of text where you cannot tell at a glance whether the tracking is right or which value is breaking something.
What you can use it for
- Auditing campaign URLs — confirming utm_source, utm_medium and utm_campaign match your naming conventions.
- Debugging redirects — reading the destination passed in a redirect_uri or return_to parameter.
- Checking what an agency or partner is actually sending you.
- Understanding filter and sort URLs on your own site, which are often generated rather than designed.
- Reading a URL from an analytics report or server log to see which variant a visitor hit.
Functional versus tracking parameters
The distinction matters because they need opposite treatment. Functional parameters change what the page shows — a product variant, a page number, a search query, a language switch. Remove them and the page breaks or shows something else.
Tracking parameters change nothing about the page. utm_source, fbclid, gclid and their relatives exist purely so analytics can attribute the visit. Remove them and the page is identical.
Seeing them separated in a table makes it obvious which is which, which is the first step in deciding what to do about them. The URL Cleaner removes the tracking ones automatically while leaving functional parameters intact.
Why parameters cause SEO problems
Every distinct parameter combination is a distinct URL to a search engine. A product page with colour, size and sort options can generate hundreds of URLs serving essentially the same content, and a faceted-navigation system can generate effectively infinite ones.
The consequences are duplicate content — ranking signals split across variants instead of concentrating on one page — and wasted crawl budget, as search engines spend requests on parameter combinations that will never be indexed.
The standard fixes are a self-referencing canonical tag on every page pointing at the clean URL, and for large parameter spaces, blocking the worst offenders in robots.txt. Which you need depends on whether the parameter URLs should be reachable at all.
Nested URLs and encoding
A common pattern is a full URL passed as a parameter value — return_to, next, redirect_uri. The inner URL must be encoded, otherwise its own query string would be parsed as part of the outer URL's parameters.
This tool decodes those values, so you can read the destination directly. That is useful for debugging login flows and tracking redirectors, and worth doing for security reasons too: a redirect parameter accepting an external domain is the classic open-redirect vulnerability.
If a value still looks encoded after extraction, it was double-encoded — the URL Decoder will unwrap the second layer, though the real fix is finding whichever system is encoding twice.
Auditing campaign URLs at scale
Inconsistent UTM values are one of the most common analytics problems, and they are invisible until you look. Facebook and facebook become separate rows; medium=email and medium=newsletter split one channel in two.
Extracting parameters from a sample of your campaign URLs surfaces this quickly. For a full list, the Bulk URL Formatter and URL Deduplicator help spot the same campaign tagged several slightly different ways.
To build new URLs correctly rather than audit existing ones, the UTM Builder assembles them with consistent encoding.
Parameter order and duplicates
Parameter order does not affect what a server returns, but it does affect URL identity for search engines and caches. ?a=1&b=2 and ?b=2&a=1 are different URLs serving identical content — another quiet source of duplication.
Repeated keys are also legal. ?tag=red&tag=blue passes two values for one key, and how a server interprets that varies. The table shows each occurrence separately so you can see when it happens.
Frequently asked questions
What is a URL parameter?
A key-value pair after the question mark in a URL, separated by ampersands. Parameters either change what the page shows (functional) or carry attribution data for analytics (tracking).
Do URL parameters hurt SEO?
They can, by creating many URLs serving similar content, which splits ranking signals and wastes crawl budget. Self-referencing canonical tags are the standard fix; robots.txt helps for very large parameter spaces.
Can I just delete parameters from my URLs?
Only the tracking ones. Functional parameters — page numbers, variants, search queries, language switches — change what the page shows, so removing them breaks the page. The table makes it clear which is which.
Why is a parameter value still encoded after extraction?
It was double-encoded, meaning the percent sign itself was escaped. Decoding once only unwraps the outer layer. The real fix is finding whichever system is encoding the value twice.
Does parameter order matter?
Not to servers, but it does to search engines and caches, which treat ?a=1&b=2 and ?b=2&a=1 as different URLs. Consistent ordering avoids creating duplicates for no reason.