Generate clean, SEO-friendly URL slugs from any title. Free slug generator with transliteration, stop-word stripping, max-length truncation, and bulk mode for blogs, e-commerce, and CMSes.
Convert any title, sentence, or product name into a clean, SEO-friendly URL slug. Handles transliteration of accented characters (é→e, ñ→n, ß→ss, ö→o), strips or keeps stop words, enforces a max length with word-boundary truncation, and supports bulk conversion of hundreds of titles at once. Live URL preview shows the slug in context (e.g. https://yourblog.com/post/your-slug) with a colored character-count bar matching Google's SEO sweet spot of 60 characters or fewer. Includes WordPress, GitHub, and filename presets, custom find-and-replace rules, and a saved history of the last 10 slugs. Built for bloggers, content marketers, e-commerce managers, and developers wiring up CMS routes.
Search engines rank pages on hundreds of signals; the URL slug is one of the smallest, but it is also one of the only signals you have direct control over and that humans read. A clean slug tells the user (and Google's click-through analysis) what the page is about before they click. Compare example.com/post?id=4279 vs example.com/post/best-noise-cancelling-headphones-2026. The second pre-qualifies clicks, gets shared more, ranks slightly higher, and is more memorable. The cost is one minute of slug-cleaning per post — exactly what this tool automates.
If your audience speaks French, German, Spanish, Vietnamese, Turkish, or Polish, your titles will contain accented characters. Browsers handle café in URLs via percent-encoding (caf%C3%A9) but the result is ugly, breaks copy-paste in some apps, and looks worse in search snippets. Transliteration replaces each accented character with its ASCII equivalent — café becomes cafe, München becomes muenchen (German uses ue for ü in romanisation), śmieszny becomes smieszny. The result is a clean ASCII URL that survives any platform.
WordPress trims slugs to 75 characters by default, lowercases everything, and uses hyphens — the WordPress preset matches exactly. Ghost behaves similarly but allows longer slugs. Hugo and most static-site generators read the slug from the file name or front matter — the Filename preset gives you a safe filesystem name. Next.js dynamic routes ([slug].tsx) match whatever you put in the URL, so any preset works as long as you keep slugs URL-safe and consistent across your site. The GitHub preset matches how GitHub generates issue URLs and wiki page paths automatically.
Short (under 60 characters), lowercase, descriptive, separated with hyphens, no stop words unless they meaningfully change the meaning, no special characters, no dates unless evergreen-vs-news matters. Google's John Mueller has confirmed that exact-match slugs give a tiny ranking signal but the bigger benefits are click-through rate (people see and trust the URL) and shareability (clean URLs paste well in messages and emails).
Google typically truncates URLs in search results around 50-60 characters, replacing the rest with an ellipsis. Beyond 90 characters social platforms (Slack, Twitter, WhatsApp) increasingly truncate or hide the path, hurting click-through. The bar is green up to 60, yellow 61-90, and red above 90 — a visual nudge to keep slugs in the SEO sweet spot.
Usually no — they do not add semantic value to the URL and they make slugs longer. Strip them by default for blog posts, articles, and product pages. The exception is when the stop word is part of a brand name or title that loses meaning without it ("the-beatles", "to-kill-a-mockingbird"). For those, keep stop words on.
No — it covers Latin-1 Supplement and Latin Extended-A (Western European languages, Vietnamese, Turkish, Polish, etc.) plus a handful of common ligatures. CJK, Arabic, Hebrew, Devanagari, Cyrillic and similar are stripped or left as-is. For those scripts, slugs work better when generated from an English-translated title or a romanised version.
WordPress: lowercase, hyphen separator, transliterate, max 75 chars (matches WordPress default permalink behaviour). GitHub: lowercase, hyphen, no max — matches the format GitHub uses for issue and wiki page URLs. Filename: lowercase, underscore separator, transliterate — produces names safe for any filesystem on any OS. All three respect cross-platform character restrictions.
Related: slug generator, url slug generator, seo slug generator, permalink generator, wordpress slug generator, url friendly text, kebab case generator, transliteration tool, remove special characters, clean url generator, pretty url generator, blog slug, product slug generator, bulk slug generator, github slug, cms permalink, seo url generator