A headline with punctuation
Punctuation is stripped (the apostrophe simply disappears), spaces become hyphens, and everything is lowercased.
Input
10 Recipes You'll LOVE (2026 Edition!)Output
10-recipes-youll-love-2026-editionTurn any title into a clean, hyphen-separated URL slug — accents converted, special characters stripped, lowercase by default.
Content last reviewed
Enter the headline or phrase you want to convert — the slug updates as you type.
Leave it on for standard URL slugs, or switch it off to keep the original capitalization.
Click Copy and paste the result into your CMS permalink field or route definition.
Punctuation is stripped (the apostrophe simply disappears), spaces become hyphens, and everything is lowercased.
Input
10 Recipes You'll LOVE (2026 Edition!)Output
10-recipes-youll-love-2026-editionAccented characters are converted to their ASCII equivalents rather than removed.
Input
Café Crème Brûlée RecipeOutput
cafe-creme-brulee-recipeA slug is the human-readable tail of a URL — the part after the last slash that tells both people and search engines what the page is about. Turning "10 Recipes You'll LOVE (2026 Edition!)" into 10-recipes-youll-love-2026-edition involves a handful of fiddly rules: strip punctuation, convert accents, collapse spaces into single hyphens, lowercase everything. This tool applies all of them instantly as you type.
The transformation follows the conventions URLs actually expect. Accented characters are converted to their plain ASCII equivalents (é becomes e), so international titles produce portable slugs. Apostrophes and other punctuation are removed rather than replaced, keeping contractions readable (you'll becomes youll). Runs of spaces become single hyphens — the separator Google documents as a word boundary, unlike underscores — and consecutive hyphens are collapsed so you never get -- in a URL. A single toggle controls lowercasing, which is on by default because mixed-case URLs create accidental duplicate addresses.
The result is copy-ready for WordPress permalinks, Next.js routes, Shopify handles, documentation paths, or any CMS slug field. Everything runs in your browser with nothing uploaded, and for the rest of a page's metadata the Meta Tag Generator and SERP Snippet Preview pick up where the URL leaves off.
Type or paste your title into the Title or sentence field. The slug regenerates live below it with every keystroke.
Leave the Lowercase toggle on for conventional slugs, or switch it off if your system requires the original casing preserved.
Review the result — accents are converted, punctuation is stripped, and spaces become single hyphens automatically.
Click Copy and paste the slug into your CMS URL field, route, or filename.
Once a page is published, keep its slug stable — if you must change a live URL, add a 301 redirect from the old address.
The slug rebuilds on every keystroke — no button to press, no page reload.
Accented Latin characters are decomposed to plain ASCII, so Café Crème becomes cafe-creme instead of losing letters.
Apostrophes, brackets, exclamation marks, and other symbols are removed cleanly, keeping contractions readable.
Runs of spaces become single hyphens and consecutive hyphens are collapsed, so the output never contains doubles.
Lowercasing is on by default (the URL convention) but can be switched off when a system needs original casing.
Convert a headline into the URL slug before publishing in WordPress, Ghost, or a static-site generator.
Create consistent, readable handles for shop items and collection pages.
Generate kebab-case names for Next.js routes, documentation files, or image filenames.
Rebuild slugs for pages whose current URLs contain spaces, capitals, or encoded characters.
The conversion is a short pipeline applied to your text on every change:
The pipeline is deterministic — the same title always produces the same slug — which matters when different team members generate URLs for the same content.
Any typed or pasted title or phrase. Latin-script text with accents converts cleanly; characters from non-Latin scripts are removed rather than transliterated.
On by default. Switch it off to keep the original capitalization while still stripping punctuation and hyphenating.
The tool keeps letters a–z, digits, spaces, and hyphens after accent conversion. Cyrillic, Arabic, CJK, and other scripts are stripped rather than transliterated, so a title written entirely in one of them yields nothing — write a Latin-script slug for such pages manually.
Punctuation is removed, not replaced with hyphens, so rock&roll becomes rockroll. Add a space around symbols you want treated as word breaks before converting.
Some systems impose extra rules — length caps or reserved words. The slug here is standard kebab-case; trim it or adjust to your platform's specific constraints.
Transliteration covers accented Latin characters only — non-Latin scripts are stripped rather than romanized, so titles in Cyrillic, Arabic, or CJK need a manually written slug. There is no stop-word removal: the, and, and of pass straight through, so trim filler words from the input yourself if you want a keyword-dense slug. Punctuation is deleted rather than hyphenated, which can merge symbol-joined words. The tool converts text; it does not check whether the slug is unique on your site or set up redirects for changed URLs.
Conversion happens in your browser as you type — the titles you enter are never uploaded, logged, or kept anywhere. There is no history to clear.
Trim the input to three to five meaningful words before converting — slugs read best short and specific.
Drop dates and version numbers from evergreen content so the URL does not age.
Keep slugs stable after publishing; if you must change one, add a 301 redirect from the old URL.
Add spaces around symbols like & and / in the input so the words on either side stay separated.
Stay lowercase — mixed-case URLs create duplicate-address headaches on case-sensitive servers.
Edit before you convert. The generator faithfully converts everything you give it, so the craft is in the input: cut the headline down to the words someone would actually search — "how-to-make-sourdough" rather than "heres-my-complete-guide-to-how-to-make-sourdough-at-home". Filler words survive conversion, so remove them yourself.
Think about longevity. A slug containing 2026 or v2 forces a choice later between an outdated URL and a redirect. Naming the topic rather than the edition lets the same URL carry updated content indefinitely.
And treat published slugs as permanent. A URL accumulates links and ranking signals from the day it goes live; renaming it discards them unless a 301 redirect carries them over. An imperfect old slug is almost always better than a broken link.
The slug is computed in a memoized client-side function: NFKD Unicode normalization followed by removal of combining diacritical marks handles accent conversion; a character whitelist regex (letters, digits, whitespace, hyphens) strips punctuation; whitespace runs are replaced with single hyphens and hyphen runs collapsed; lowercasing is applied last when enabled. No network requests are made, and the same input always yields the same output.
Bloggers and content editors setting permalinks, developers naming routes and files in kebab-case, shop owners creating product handles, and SEO practitioners cleaning up messy inherited URLs. Anyone who publishes with a CMS touches slugs; this makes each one a two-second task instead of a manual find-and-replace exercise.
Modestly. URL words are a lightweight relevance signal, and readable descriptive URLs earn more clicks in results than ID strings. It is a small, permanent optimization — worth the two seconds it takes.
Google documents hyphens as word separators and treats underscores as joiners: how-to-cook reads as three words, how_to_cook as one token. Hyphens are the safe convention, and they are what this tool produces.
The punctuation is removed and the letters kept, so you'll becomes youll and don't becomes dont. That matches how most CMS slug generators behave and keeps the words readable.
They are converted to their plain equivalents — é to e, ñ to n, ü to u — so international titles produce portable ASCII slugs instead of percent-encoded URLs.
No — every word in the input survives conversion. If you want a tighter slug, delete the filler words from the input before or after converting; the live output makes that easy to see.
Technically yes, but only add a 301 redirect from the old URL first, or you lose the links and ranking signals it accumulated. If the old slug is merely imperfect, leaving it alone is usually the better decision.