Home › Tools › URL Slug Generator

URL Slug Generator

Turn a page title into a clean URL slug: lowercase, hyphenated, accents folded, with an optional stopword filter and a live length check. Copy it straight out.

SerpPrism's URL Slug Generator is a free online tool that turns a page title into a clean, copy-ready URL slug: lowercase, hyphen-separated, with accents folded to plain ASCII and punctuation removed. There is no sign-up and it runs entirely in your browser. An optional filter drops common stopwords, and an optional length cap trims the slug at a word boundary instead of cutting a word in half. It is for anyone publishing a page who wants the URL decided deliberately — short, readable and stable — rather than whatever a CMS auto-generates from the headline. Type the title, copy the slug, and watch the character count as you go.

How to use it

  1. Type or paste the page title exactly as it will appear on the page.
  2. Choose whether to drop stopwords, and whether to cap the length — the slug rebuilds instantly.
  3. Copy the slug into your CMS. Once the page is published and linked, treat the slug as permanent.

What makes a slug good

A good slug describes the page in a few words, in lowercase, with hyphens between words. Hyphens matter: Google treats a hyphen as a word separator and an underscore as a joiner, so url-slug reads as two words and url_slug reads as one long one. Dates, session IDs and file extensions do not belong in a slug unless the page is genuinely about that date.

Our guide to how long a URL slug should be works through the trade-offs with real examples, including when a longer slug is the honest choice. The short version: three to five words usually say enough, and the slug should match the title's meaning without copying every word of it.

Should you remove stopwords?

Sometimes. Dropping 'a', 'the' and 'of' almost never changes what a slug means, and it buys back characters. But stopword lists are blunt: 'how' and 'what' are function words that also carry search intent, and a slug stripped of them can end up describing a different query than the page answers.

That is why the filter here is off by default and conservative when on. Compare both versions before you choose. The right question is not 'is this word a stopword' but 'would a reader still know what this page is from the slug alone'.

Worked examples: four titles, four slugs

'How Long Should a URL Slug Be?' becomes how-long-should-a-url-slug-be with stopwords kept, and long-should-url-slug with the filter on — 'how', 'a' and 'be' drop out, but 'should' stays, because it is not in the stopword list. The shorter version is 9 characters shorter, and it loses the question the page answers. Whether that trade is worth it is a judgement call, not a rule.

'Café au Lait: A Beginner's Guide' becomes cafe-au-lait-a-beginner-s-guide — the accent folds to a plain 'e', the colon becomes a hyphen boundary, and the apostrophe splits 'Beginner's' into 'beginner-s'. Possessives are the one case where the output looks slightly odd; the fix is to reword the title ('Beginner Guide' instead of 'Beginner's Guide') rather than fight the generator. '10 Best Espresso Machines for Beginners (2026)' becomes 10-best-espresso-machines-for-beginners-2026 — numbers kept, parentheses dropped.

The length cap trims at a word boundary, never mid-word. 'The Complete Beginner's Guide to Choosing Your First Espresso Machine' is 69 characters as a slug; with the 60-character cap it becomes the-complete-beginner-s-guide-to-choosing-your-first — 52 characters, ending at 'first' rather than cutting 'espresso' in half.

Changing a slug after publishing

A new slug is a new URL. Every link, bookmark and search result pointing at the old one breaks unless you redirect it, one-to-one, with a 301 to the new address. Sites accumulate redirect chains by changing slugs casually and redirecting in bulk to the homepage, which helps nobody.

So decide the slug before the page goes live, while changing it is still free. If you must change one later, redirect that exact URL to its replacement and update your internal links to point at the new address directly.

Questions

Are hyphens or underscores better in a URL slug?

Hyphens. Google treats hyphens as word separators and underscores as joiners, so hyphenated slugs are read as separate words. Every major CMS defaults to hyphens for this reason.

How long should a URL slug be?

There is no hard limit and length is not a ranking factor. Three to five descriptive words is a good default — long enough to say what the page is, short enough to read at a glance and survive being pasted into messages. Our slug length guide covers the edge cases.

Should a slug contain the full page title?

Usually a shortened version of it. Titles carry clicks and can afford extra words; slugs get retyped, shared and truncated in link previews, so cut the words that add length without adding meaning.

Can a slug contain capital letters or accented characters?

Technically yes, and it causes quiet problems: /Guide and /guide are different URLs to a server, and accented characters arrive percent-encoded (%C3%A9) in shared links. This generator lowercases everything and folds accents to ASCII so the slug you copy is the slug that works everywhere.

Do keywords in the slug help rankings?

Only marginally, if at all — Google has said the effect is very small. The real value of a descriptive slug is human: people click links they can predict, and link to pages whose URLs they can read. Optimise for that.

What happens to punctuation in my title?

Ampersands become the word 'and', apostrophes are dropped (so a title about beginners produces 'beginners', not a broken encoding), and everything else non-alphanumeric becomes a hyphen boundary. Numbers are kept.

Should a slug include the year?

Only if the page is genuinely about that year — a 2026 roundup, a dated report. For evergreen content a year in the slug becomes a liability: update the page and you either live with a stale date or change the URL and redirect the old one.

Can a slug use non-English characters?

Technically yes — Google handles unicode URLs. In practice they arrive percent-encoded in shared links (%C3%A9 for é), and some tools mangle them. This generator folds accents to ASCII; if your audience reads the language, a native-language slug is still a reasonable choice.

Related tools

Related guides