URL Cleaner
URL Cleaner parses an absolute URL, removes its fragment, and deletes all occurrences of utm_source, utm_medium, utm_campaign, utm_term, utm_content, fbclid, and gclid. Parameter names are case-sensitive, so UTM_Source remains; every other query parameter remains. URL serialization may normalize escaping or append a slash. The page does not know which parameters affect page content, attribution, sessions, signatures, or application behavior.
Runs locally — files stay on your deviceWhich parameters are removed?
Five standard lowercase UTM fields plus fbclid and gclid.
Removing tracking parameters can change analytics and signed URLs
Some query fields are disposable attribution labels; others select content, authorize access, or participate in signatures. Their meaning is application-specific.
How it works
new URL parses trimmed input, hash is cleared, seven exact names are deleted with URLSearchParams, and the URL is serialized.
Key concepts
Allowlist of removals
Unknown parameters are preserved.
Fragments never reach HTTP
They are removed because they identify client-side state.
When to use it
- Create a shareable copy after reviewing known tracking fields.
- Remove a fragment from an absolute URL.
- Inspect the destination without common campaign labels.
When not to use it
- Do not clean signed or tokenized URLs without testing.
- Do not assume mixed-case variants disappear.
- Do not use output as an automatic canonical decision.
Worked examples
UTM URL
- Input
https://e.test/?utm_source=x&id=4#top- Expected output
https://e.test/?id=4
Known tracking and fragment are removed.
Uppercase key
- Input
?UTM_SOURCE=x- Expected output
Key remains
Deletion is case-sensitive.
Signed URL
- Input
?sig=...&utm_source=x- Expected output
sig retained but signature may depend on full query
No verification occurs.
Common mistakes
Assuming all trackers removed
Only seven names are known. Correction: Review remaining fields.
Breaking signed links
Any change can invalidate a signature. Correction: Do not alter without protocol knowledge.
Using as canonical generator
Content equivalence is untested. Correction: Choose canonicals from site semantics.
Best practices
- Compare destination behavior before sharing.
- Maintain an application-specific parameter policy.
- Never expose sensitive tokens merely because tracking was removed.
Related operations and differences
URL Parameter Remover
Choose URL Parameter Remover when you need to remove every query parameter and fragment.; use URL Cleaner specifically for url clean.
Canonical Tag Generator
Choose Canonical Tag Generator when you need to generate a canonical link element from a URL.; use URL Cleaner specifically for url clean.
External Link Extractor
Choose External Link Extractor when you need to extract links pointing away from a hostname.; use URL Cleaner specifically for url clean.
FAQ Schema Generator
Choose FAQ Schema Generator when you need to generate FAQPage JSON-LD from question-answer blocks.; use URL Cleaner specifically for url clean.
Heading Structure Checker
Choose Heading Structure Checker when you need to list H1–H6 elements from pasted HTML.; use URL Cleaner specifically for url clean.
Hreflang Tag Generator
Choose Hreflang Tag Generator when you need to generate language alternate tags from URL lines.; use URL Cleaner specifically for url clean.
Limitations and privacy
- Absolute URLs only.
- Seven case-sensitive parameter names and fragment removal; no redirect, behavior, signature, content-equivalence, privacy, or canonical validation.
The pasted text or URL is processed locally in this browser and is not fetched or submitted by the tool.
Frequently asked questions
Are all query parameters removed?
No.
Is the fragment removed?
Yes.
Are uppercase UTM names removed?
No.
Does it open the URL?
No.