Turn any title into a clean URL slug. Strips accents, chooses a separator, controls case and length, optionally removes stop words and keeps Unicode.
Turn a title into a clean, URL-safe slug. Accents are folded to plain ASCII, punctuation is dropped and words are joined by the separator you pick. Use the options to control case, trim a maximum length or strip common stop words.
What makes a good URL slug
Why slugs exist
A slug is the human-readable part of a URL that identifies a page: the how-to-cache-resumes-in-redis in /blog/how-to-cache-resumes-in-redis. It replaces an opaque numeric ID with something a person can read, remember and evaluate before clicking. Search engines display the URL in results, so a descriptive slug both reassures readers and reinforces the topic of the page.
The rules a slug should follow
Keep to lowercase ASCII letters, digits and a single separator. This avoids three separate classes of problem: URLs are case-sensitive in their path on most servers, so /About and /about are different resources and a mixed-case slug invites duplicate-content errors. Percent encoding makes any non-ASCII character three times longer and much harder to read when copied into plain text. And spaces are simply not allowed, becoming %20 or +.
Hyphens are the conventional separator. Google has stated for years that it treats hyphens as word separators and underscores as word joiners, meaning cache_redis may be read as a single token while cache-redis is clearly two words. Unless you have a specific reason, choose the hyphen.
Transliteration versus keeping Unicode
By default this tool folds accented characters to their closest ASCII equivalent: é becomes e, ß becomes ss, ł becomes l. It does this by decomposing the text with Unicode NFD normalisation and dropping the combining marks, plus a lookup table for the ligatures and special letters that decomposition does not handle.
Keeping Unicode is a legitimate alternative. Internationalised URLs work in every modern browser and are far more readable to a reader of that language — a Chinese or Russian slug transliterated to ASCII is usually meaningless. The cost is that the raw URL contains percent-encoded bytes, which look alarming when pasted into an email or a terminal, and some older tools still mangle them. Enable Keep Unicode letters if your audience reads the script; leave it off if the slug has to survive arbitrary systems.
Length and stop words
There is no technical limit worth worrying about, but slugs beyond roughly 60 characters get truncated in search results and become awkward to share. Trimming is best done on a word boundary rather than mid-word, which is what the length option does here.
Removing stop words — the, a, of, and — shortens a slug without losing much meaning. It is a stylistic choice rather than a ranking factor; modern search engines are perfectly capable of ignoring them. Be careful with titles where a stop word carries meaning, since stripping them from "The Who" or "To Be or Not to Be" destroys the phrase.
Stability matters more than perfection
Once a slug is published and linked, changing it breaks every inbound link unless you add a redirect. A slightly imperfect slug that has been live for a year is almost always better than a cleaner one that costs you your backlinks. Decide the format before launch, then leave it alone.
FAQs
Hyphens or underscores?
Hyphens. Search engines treat a hyphen as a word separator and an underscore as a word joiner, so hyphenated slugs are parsed into individual words. Underscores also disappear visually under the underline that links carry by default.
Should slugs be lowercase?
Yes. The path portion of a URL is case-sensitive on most servers, so /About and /about can resolve to two different pages and split your ranking signals. Forcing lowercase removes the whole class of problem.
Can I use non-English characters?
Yes, modern browsers handle them fine and they are far more readable to native speakers. The trade-off is that the raw URL becomes percent-encoded, which looks noisy outside a browser. Enable Keep Unicode letters if that trade-off suits your audience.
How long should a slug be?
Long enough to be descriptive, short enough to read at a glance. Around three to six words, or under 60 characters, keeps it fully visible in most search result listings.
Should I remove stop words?
Usually it is harmless and makes the slug tidier, but it is a cosmetic choice with no ranking benefit. Skip it when a stop word is load-bearing, as in a band name or a quotation.
Is it safe to change a slug later?
Only with a 301 redirect from the old URL. Without one you lose every existing link and bookmark, along with the accumulated ranking signals. Settle on a format early and keep it.