URL Slug Generator
How it works
Type or paste a title and the slug updates as you type: lowercased, accents transliterated (è→e, ü→u, ß→ss, œ→oe), every run of symbols or spaces collapsed into a single separator, leading and trailing separators trimmed. Paste multiple lines to slugify a whole content calendar at once, one slug per line.
A slug is the human-readable tail of a URL: `/blog/my-post-title`. Search engines treat words in the URL as a mild relevance signal and, more importantly, readable links get clicked more often in search results and when someone shares them. The safe alphabet is lowercase a-z, digits and hyphens: no spaces (they become %20), no accented characters (they become percent-escaped UTF-8 soup), no apostrophes or ampersands.
Hyphen vs underscore: pick hyphens for public URLs. Google documents that it treats a hyphen as a word separator but joins the words around an underscore, so my_post reads as the single token 'mypost'. The underscore option is there for the other use cases: file names, database identifiers, code symbols where snake_case is the convention.
Keep slugs short. Three to six meaningful words beat a full sentence, and stop-words (the, a, di, il) can usually be dropped by hand without hurting readability. And once a page is published, never change its slug casually: the slug is the URL's identity, so changing it needs a 301 redirect from the old address. Nothing you type is uploaded, because the slugifying happens in the page itself.
Frequently Asked Questions
Hyphens or underscores for SEO?
- Hyphens. Google's documentation is explicit: a hyphen is read as a word separator, an underscore is not, so my-blog-post is three words while my_blog_post risks being read as one. Use the underscore option for file names and code identifiers, not for public URLs.
What happens to accented characters like è, ü, ç?
- They are transliterated to their base ASCII letter via Unicode decomposition: è→e, ü→u, ç→c, plus special-case mappings for the letters that do not decompose (ß→ss, æ→ae, œ→oe, ø→o). Perché No becomes perche-no, which is readable and URL-safe.
Can I slugify many titles at once?
- Yes. Paste one title per line and you get one slug per line, ready to paste into a spreadsheet or CMS. Empty lines are dropped.
Are non-Latin scripts (Cyrillic, Arabic, CJK) supported?
- No. Characters that do not decompose to a-z are removed rather than transliterated, so a fully non-Latin title produces an empty slug. For those languages the honest options are a proper transliteration scheme or keeping the native script percent-encoded in the URL, both beyond a generic slugifier; this tool is built for Latin-script content.
How long should a URL slug be?
- Under 60 characters in practice, even though a URL can technically run to about 2,000. Search snippets truncate long URLs, and every extra word dilutes the signal. This tool never truncates: trimming to the essential words is an editorial call, not a mechanical one.