URL Slug Generator

Turn a title into a clean URL slug as you type. Paste a whole list of titles, one per line, and every slug is generated at once with duplicates flagged before they become a publishing problem.

Your titles (one per line for bulk)

Separator

Max length (0 for no limit)

Lowercase

Drop filler words

Slugs are a decision you make once

A slug is cheap to get right before publishing and expensive to change afterwards, because changing it means a redirect, and a redirect means every link to the page now takes an extra hop. That asymmetry is the whole argument for spending thirty seconds on it up front.

The other argument is durability. A slug carrying a year, a version number, or a word like "new" dates the moment the year turns, and you are then choosing between an out-of-date URL and a redirect. Leave those in the title, where you can edit them freely, and keep them out of the URL.

When you do have to change one, the redirect checker confirms the old URL lands on the new one in a single hop rather than joining a chain.

Frequently Asked Questions

What makes a good URL slug?

Short, readable, lowercase, and hyphenated. It should describe the page well enough that someone reading the URL alone knows what is on the other end. Three to five meaningful words is the usual sweet spot; beyond about 75 characters a slug stops being readable and starts being truncated in search results.

Hyphens or underscores?

Hyphens. Google treats a hyphen as a word separator and an underscore as a word joiner, so seo_tools reads as one token while seo-tools reads as two words. This has been Google's documented advice for many years.

Should I remove stop words from slugs?

Only where the slug stays readable without them. "how-to-choose-a-crm" is better than "choose-crm" because it matches how someone would describe the page. The filler option above is for the cases where a long title produces a slug carrying four prepositions, not as a default.

Can I change a slug on a published page?

You can, and you should redirect the old URL to the new one with a 301 when you do. Without the redirect you lose whatever links and rankings the old URL had. If the page is performing, the safer answer is usually to leave the slug alone: the gain from a tidier URL rarely exceeds the risk.

How does it handle accented characters?

They are transliterated rather than dropped, so "café" becomes "cafe" and "straße" becomes "strasse". A German umlaut reduces to its base letter, so "Köln" becomes "koln" and "Grüße" becomes "grusse". The tool has no way to know which language a title is written in, and the German "oe" expansion is wrong in every other language that uses the same letter, so the base letter is the rule everywhere.

What about Cyrillic, Greek, and other scripts?

Cyrillic and Greek are transliterated: "Как выбрать CRM" becomes "kak-vybrat-crm" and "Οδηγός SEO" becomes "odigos-seo". Scripts with no accepted Latin transliteration, such as Japanese, Arabic, and Hebrew, are left alone and the row says so, because a machine guess at a Japanese title reads worse than a slug you write yourself. Non-Latin characters left in a URL are percent-encoded by browsers into something no one can read or share, which is why transliteration is the default here.

Should a slug be lowercase?

Yes. Most web servers treat a URL path as case-sensitive, so /SEO-Tools and /seo-tools are two different URLs, and a stray capital is how one page ends up with two of them. Turn the Lowercase option off only when you are matching a scheme your site already uses; the slug then keeps the casing of the title you typed.

Why does it flag duplicates?

Because two titles can reduce to the same slug, and two pages cannot share a URL. Converting a list of planned articles in one go surfaces the collision while it is still a naming decision rather than a publishing error.