Slug Generator

How the slug is built

1. Transliterate — accented Latin letters become their base letter (é→e, ñ→n, ß→ss). The Unicode NFKD normal form does most of this; a small map covers the rest.
2. Lowercase (optional, on by default).
3. Strip everything that isn't a letter, digit, space or hyphen — so &, !, ?, quotes, em dashes and emoji are removed.
4. Drop stop words (optional) — a, an, the, and, or, but, of, to, in, on, for, with, is — only when the slug still reads clearly.
5. Collapse runs of whitespace and hyphens into a single separator, and trim it from both ends.
6. Truncate to the max length (optional), cutting at a word boundary so the slug never ends mid-word.

So Café Menu & Prices — Summer 2026! becomes cafe-menu-and-prices-summer-2026 (the & is spelled out, the accent and punctuation are gone).

What makes a slug good

Do	Avoid
Lowercase, hyphen-separated	Spaces, underscores, mixed case, %20
Short — 3–5 meaningful words	The whole 12-word title, or a bare ID like /p?id=482
Descriptive of the page	Dates and version numbers that will change
Stable once published	Renaming without a 301 redirect

Hyphen, not underscore. Google reads a hyphen in a URL as a space between words and an underscore as a joiner, so rest-api-guide is three keywords and rest_api_guide is one.

Non-Latin text

Characters with no ASCII base — Cyrillic, Arabic, CJK, most emoji — are dropped, which can leave an empty or partial slug. If your titles are in a non-Latin script, keep the readable text in the URL and percent-encode it instead; modern browsers display the decoded form in the address bar.

Questions