Content

URL Slug Generator

A clean address you will not have to redirect

In build

Type a working title and get a clean slug: lowercase, hyphenated, accents folded to ASCII, stop words and dates optionally dropped, length capped, plus the full URL it produces under the path you pick, and a warning when it duplicates an existing one.

Get early access

What it returns

A lowercase, hyphen-separated slug from any title, with punctuation removed and accented characters folded to the nearest ASCII equivalent.
The full URL the slug produces under the path prefix you choose, so the length and depth of the finished address are visible before anything ships.
Optional removal of stop words, dates and issue numbers, shown next to the untouched version, so the trade between brevity and readability stays your call.
A warning when the result matches a slug already in the list you paste in, which is where silent duplicates and auto-appended numbers come from.

When this matters

A publisher's CMS builds slugs from the headline, so a post titled with a typographic apostrophe, a trademark symbol and a colon ships as a URL carrying three percent-encoded sequences: unreadable in a share, awkward in a report. Another team fixes that by trimming every slug to two words, and now half the archive needs redirects because two different posts collapsed onto the same address. The decision is small and close to permanent: once a URL is indexed and linked, changing it costs a redirect and some of its history.

How to answer this today

The decision upstream of the slug is which words belong in it, and that is a keyword research question: which phrasing people actually search, how the demand splits between variants, and whether the term deserves its own page at all. Keyword research answers that. Turning the chosen title into a safe, stable address is the mechanical step afterwards.

Keyword research

Why this is harder than it looks

Transliteration is a judgement call

Folding to ASCII is not reversible: a German umlaut can become one letter or two and both are defensible, while Greek, Cyrillic and Arabic have competing standards. A non-Latin site is often better served keeping its own script, which browsers handle fine and spreadsheets still mangle.

Keywords in the URL do very little

A descriptive slug helps a human decide whether to click a bare link pasted into a chat. As a ranking input it is very weak, and forcing the target phrase into the path has never been worth the address it produces.

Changing one is not free

Every existing link, share and stored metric points at the old address. A better slug on a page that already has history means a redirect to maintain, a temporary dip, and a referral trail that no longer lines up with the reports.

Collisions surface too late

Two different titles can reduce to the same slug, and most systems resolve that by appending a number nobody meant to publish. Checking against the slugs that already exist is the only way to catch it while the URL is still changeable.