Accent-Safe Slugs
Transliterates café, naïve, straße, and ø into clean ASCII slugs instead of dropping or mangling the characters.
URL Slug & Query Cleaner
TL;DR: URL Slug & Query Cleaner checks slugify any text and strip tracking parameters from urls. so you can confirm the current issue, understand when it matters, and move directly into the next fix without leaving the browser.
Generate clean, readable slugs from any text and strip tracking junk from URLs — all in your browser.
更新されました
Loading tool interface...
Accent-aware slug generation (NFKD transliteration) Hyphen or underscore separators One-click tracking-parameter stripping Before/after URL comparison 100% client-side — nothing is uploaded
What does URL Slug & Query Cleaner do?
The URL Slug & Query Cleaner does two jobs in one tool. In slug mode, it converts arbitrary text — headlines, product names, foreign-language titles — into a clean, URL-safe slug by transliterating accents, stripping punctuation, lowercasing, and collapsing spaces into a single separator. In URL mode, it strips tracking parameters from a link and shows a clear before/after so you can see exactly what was removed.
Why slugs matter for SEO: A readable slug like /cafe-creme-recipes is easier for users to scan, gets cited more naturally in links, and gives search engines a clean keyword signal. Slugs full of query strings, mixed case, or unencoded accents look broken when shared and can fragment your URLs in analytics.
Why tracking parameters hurt you: Campaign tags such as utm_source, gclid, and fbclid never change the page that is served, but they create endless URL variations. Those variants split analytics, can spawn duplicate-content and crawl-budget issues when they get indexed, and make shared links look spammy. Stripping them gives you the canonical, shareable address.
Smart by default: The cleaner only removes parameters it recognizes as pure tracking or attribution noise — the full utm_* family plus gclid, dclid, fbclid, igshid, msclkid, mc_cid, ref, and dozens more. Functional parameters like id, page, q, and lang are always kept because removing them could change the page.
Private and instant: Everything runs client-side. Your text and URLs never leave the browser, so you can clean internal or unpublished links without sending them to a server.
When should you use URL Slug & Query Cleaner?
URL Slug & Query Cleaner is most useful when you need a direct answer on a live URL or draft before you change templates, ship content, or rerun a wider audit.
このツールの使用方法
- 1 Pick a mode: Slugify text or Clean URL.
- 2 Paste a headline to slugify, or paste a link full of tracking tags to clean.
- 3 Choose your separator and case for slugs, or read the before/after diff for URLs.
- 4 Copy the clean slug or stripped URL straight into your CMS or share sheet.
What should you do next?
Once you have a clean slug, confirm the live URL resolves cleanly with the Redirect Checker and that its canonical tag points at the stripped address with the Canonical Checker. Then move to the related checks below to confirm the fix on the live canonical page.
得られるもの
Tracking Param Killer
Strips the full utm_* family plus gclid, fbclid, igshid, mc_cid, msclkid, and dozens more, while keeping functional query params intact.
Clear Before & After
See exactly which parameters were removed and which were kept, so you trust the cleaned URL before you publish or share it.
Frequently Asked Questions
URL Slug & Query Cleaner についての回答
Paste the title into slug mode and the tool returns a lowercase, hyphenated, URL-safe slug. It transliterates accents (café becomes cafe), removes punctuation and symbols, and collapses spaces into a single separator so the result is ready to drop into your CMS.
It strips the entire utm_* campaign family plus click identifiers and email-tracking tags such as gclid, dclid, gbraid, wbraid, fbclid, igshid, msclkid, ttclid, yclid, mc_cid, mc_eid, mkt_tok, and ref. It also matches families by prefix (utm_, hsa_, pk_, matomo_) so newer variants are caught automatically.
No. The cleaner only removes parameters that are pure tracking or attribution noise, which never change the page a server returns. Functional parameters like id, page, q, sort, and lang are always preserved because those can determine which content loads.
No. All slugifying and URL cleaning happens entirely in your browser with no network requests. Your text and links are never uploaded, so you can safely process internal, staging, or unpublished URLs.