URL Slug Generator
Clean, readable, stable URLs from any title.
What makes a good slug
- Lowercase. URLs are case-sensitive on most servers, so
/Aboutand/aboutcan be two different pages that split your ranking signals. - Hyphens, not underscores. Google treats the hyphen as a word separator and the underscore as a joiner, so
url-slugreads as two words whileurl_slugreads as one. - Readable. A slug appears in search results, in shared links and in the browser status bar.
/how-to-build-a-slug-generatortells people what they will get;/p?id=4821tells them nothing. - Stable. Once published, a slug is a public address. Changing it breaks inbound links and bookmarks unless you set up a redirect.
- Short enough. Excessively long URLs get truncated in search results and look untrustworthy when shared.
Should you remove stop words?
Dropping words like "a", "the", "of" and "to" produces shorter slugs, which is why many CMS platforms do it by default. The trade-off is readability: /how-build-url-slug-generator is shorter than /how-to-build-a-url-slug-generator but reads like telegram style. There is no ranking benefit either way — stop words in URLs carry essentially no weight. The sensible rule is to drop them only when the slug is otherwise long, and to keep them when removing them would make the phrase confusing. This tool lets you compare both.
Handling non-Latin scripts
Accented characters are transliterated — "é" becomes "e", "ü" becomes "u" — because unencoded non-ASCII characters in a URL become long percent-encoded sequences that are hard to read and share. For scripts with no Latin equivalent, such as Chinese, Arabic or Japanese, there is a genuine choice. Transliterated slugs are safest and most portable. Native-script slugs are perfectly valid in modern URLs, are handled correctly by Google, and are more readable for the local audience. If your audience is primarily local, keep the native script; if the content may be shared internationally, transliterate.
Changing a published slug
If you must change one, always set a 301 redirect from the old URL to the new one. Without it, existing links, search rankings and bookmarks all break, and the accumulated authority of the old address is lost rather than passed on. Avoid changing slugs for cosmetic reasons — a slightly imperfect slug with two years of links pointing at it is worth far more than a perfect one starting from zero. Plan the slug before publishing, and treat it as permanent.
Things to avoid
- Dates in slugs for evergreen content —
/2026/03/…makes good content look stale and forces a URL change if you ever update the year. - Keyword stuffing. Repeating the phrase adds no ranking benefit and looks like spam to users.
- Auto-generated IDs. Numbers say nothing to a reader and nothing to a search engine.
- Trailing punctuation and double separators, which create duplicate-looking variants of the same URL.
If you are converting a batch of titles, run them through one at a time or clean the list first with the line cleaner.