URL Slug Generator

How to Use the URL Slug Generator

1. Pick Single title for one slug, or Bulk mode to paste a list of titles (one per line).
2. Paste or type your title into the input area. The slug updates live as you type.
3. Choose a preset — SEO blog post, GitHub / npm, Python / DB column, or Tweet / short URL — or tune the four options individually.
4. Verify the URL-safe badge under the output. It turns red if any non-ASCII character would need percent-encoding.
5. Click Copy slug (or Copy all slugs in bulk mode) to send the result to your clipboard.

Why Slug Quality Matters for SEO and UX

Search engines use the URL slug as one signal of what the page is about. Human readers use it as a preview — when a slug reads /blog/how-to-bake-sourdough/ they can predict the content before they click; when it reads /posts?id=42 they can't. Google's John Mueller has publicly recommended hyphen-separated, lowercase, keyword-rich slugs since 2011, and the rule has held up across every major ranking-factor study run by Ahrefs, Backlinko, and Moz. The slug is a single low-effort lever that compounds across every internal link, social share, and search snippet for the life of the URL — so it is worth getting right the first time, because changing it later means a permanent 301 redirect.

Preset Comparison

Examples — Input → Slug

When to Pick Which Separator

• Hyphen (-) — Google's official recommendation for web URLs. Treated as a word separator by every modern search engine. Use this for blog posts, product pages, and anything you want to rank.
• Underscore (_) — Treated as a letter joiner, not a word break, so search engines see hello_world as one token. Use this for Python and Ruby variable names, database column names, and SQL identifiers — anywhere a hyphen would be parsed as subtraction.
• Dot (.) — Useful for hierarchical configuration keys, namespaced JavaScript module names, and Clojure namespaces. Avoid in web URLs — many systems trim or reinterpret trailing dots.

How Unicode Transliteration Works

Naïvely lowercasing a title in another language usually produces a slug that still contains characters outside the URL-safe set, forcing the browser to percent-encode them and turning /münchen into the unreadable /m%C3%BCnchen. This tool applies a two-stage transliteration:

1. Explicit map for compound substitutions — German ä → ae, ö → oe, ü → ue, ß → ss; ligatures æ → ae, œ → oe; Nordic þ → th, ð → d, ø → o; Polish/Slavic ł → l.
2. Unicode NFKD normalisation — Decomposes accented letters into a base letter plus combining diacritic, then strips the combining mark. é becomes e, ñ becomes n, č becomes c, and so on.

The final pass replaces any character outside [a-z0-9] with the chosen separator, producing a slug that is safe in any URL, file system path, or DNS label.

Common Mistakes to Avoid

• Don't stuff keywords. A slug like best-cheap-budget-affordable-laptop looks spammy and rarely outranks budget-laptop-2026.
• Don't include the year unless the page will be updated annually. A 2024 slug looks stale by 2026 and forces a 301 redirect to refresh.
• Don't change a published slug. Every change requires a permanent redirect, leaks a fraction of link equity, and breaks bookmarks. Get it right before you publish.
• Don't mix separators. Pick hyphens or underscores and stay consistent across the site — mixed URLs confuse crawlers and humans equally.
• Don't slugify identifiers. If your CMS already exposes a numeric ID, treat the slug as a vanity layer — and accept either /posts/42-how-to-bake-sourdough/ or /posts/how-to-bake-sourdough/ in the router.