How to use the URL Slug Generator
1. Type or paste a title, headline, or any text into the input field.
2. Choose a separator (hyphen, underscore, or dot) and toggle lowercase.
3. Set an optional max length, then copy the generated URL slug.
What is it?
A URL slug is the human-readable part of a URL that identifies a specific page — the "how-to-build-a-rest-api" in "https://example.com/blog/how-to-build-a-rest-api". Good slugs are lowercase, use hyphens as word separators, contain no special characters or spaces, and are as concise as possible while remaining descriptive. Search engines use slugs as ranking signals, so clear and relevant slugs improve SEO.
This tool normalizes accented characters (é → e, ñ → n), strips special characters and symbols, collapses whitespace runs to a single separator, and optionally truncates to a maximum length. The max length truncation respects word boundaries — it won't cut in the middle of a word, leaving a trailing separator.
Example
How to Build a REST API: Best Practices (2024) — Naïve Approach vs. Expert
how-to-build-a-rest-api-best-practices-2024-naive-approach-vs-expert
Accented chars (ï→i), punctuation, and special chars are all handled. Copy directly into your CMS or router.
Benefits
Generate SEO-friendly URL slugs from any title in one click
Spaces become hyphens, accented characters are normalised, and unsafe characters are removed — producing clean, crawlable URLs.
Handle multilingual titles correctly
Accented characters (é, ü, ñ, ç) are transliterated to ASCII-safe equivalents rather than percent-encoded or stripped.
Prevent URL encoding problems at the source
Slugs contain only URL-safe characters that need no percent-encoding in any browser, link, or API context.
Consistent slug format for your CMS or blog
The same title always produces the same slug — preventing duplicate URL variations when content is republished or migrated.
Frequently asked questions
What separator should I use?
Hyphens (-) are the SEO-recommended separator for URL slugs. Google treats hyphens as word separators, making 'how-to-build-an-api' fully readable by search engines. Underscores are treated as word joiners by Google, meaning 'how_to_build_an_api' may be read as one word. Dots are used in some systems but are less common.
How are accented characters handled?
Accented characters (é, ü, ñ, ø, etc.) are normalized using Unicode NFD decomposition, which separates the base letter from the accent mark, then strips the accent. So 'résumé' becomes 'resume'. This works for most Latin-script accents used in European languages.
Should slugs be lowercase?
Yes — always use lowercase slugs. URLs are technically case-sensitive on most servers, meaning /Blog and /blog could be different pages. Using all-lowercase slugs avoids duplicate content issues, unexpected 404 errors, and case-sensitivity bugs. Search engines also prefer consistent, lowercase URLs.