A URL slug is the readable part of a path after the site name: /tools/slug-generator/ ends in slug-generator. It is not the full URL, not a query string, and not a document title. What makes a good URL slug is a small contract: people can read it, you can say it aloud, and it will not change every time you edit the heading.
This article is that contract. It is not a second generator. The Slug Generator turns a title into a conservative client-side slug. The Case Converter only changes case and leaves spaces in place. Title Case is a heading. A slug is a path.
Prefer words a reader can parse. how-character-limits-are-counted is better than hclac or a hash. Keep it short enough to paste. Do not stuff extra synonyms into the path. Stability matters more than a perfect phrase: changing a published slug breaks bookmarks unless you add a redirect. YallaSolve does not check uniqueness against your CMS or anyone else’s.
Spaces become hyphens. Other separators, including underscores, become hyphens on this generator because two separator styles in one slug are how links later disagree. Repeated hyphens collapse. Leading and trailing hyphens are stripped. Commas, quotes, and similar punctuation are dropped. Digits stay: “Review 2024” becomes review-2024.
If the title is full of tabs or double spaces, clean it first. How to clean and normalize text is the spacing job. Hyphenating a dirty title encodes the dirt.
Latin letters with accents are unaccented by decomposing and dropping combining marks: café becomes cafe. That is limited folding, not translation. Arabic, Cyrillic, CJK, and other letters are kept. The generator will not invent ni-hao from Chinese. A punctuation-only title is rejected because nothing usable remains.
Unicode in a path is allowed on many modern stacks and still needs encoding in a full href. Servers and search tools do not all treat a Unicode slug the same way. Some CMS pipelines force ASCII. WordPress sanitize_title may fold more, or less, than this browser page. Always look at the stored permalink.
Example input Hello, World! Café -- already--hyphenated becomes hello-world-cafe-already-hyphenated. There is no underscore mode, no stop-word list, and no romanization table. Input over 200,000 characters is refused. Pasted markup is not executed.
A good slug is the one you can still recognize next year and that your CMS actually stored. Generate, paste, then read the live path. If the live path differs, the CMS rule won. The generator is the preview, not a guarantee.
Changing a slug after publish is a redirect problem, not a generator problem. If the heading improves and the old path already has links, keep the old slug or add a redirect. A “better” slug that 404s the previous one is not better.
Stop words such as “and” and “the” stay if you typed them. Removing them by hand is a taste choice. This page will not strip them for you and then pretend the slug is still the same title. If the title is only punctuation, the generator refuses instead of emitting a hyphen.
Encoding is a second step. The box shows the path segment. A browser will percent-encode some Unicode when it builds a request. Your sitemap and your internal links should use one consistent form. Do not mix a raw Unicode path in one place and an encoded copy in another and then ask which one is canonical. The CMS canonical wins when they disagree.
Search engines do not all display Unicode slugs the same way, and they do not all treat hyphenation as a ranking lever you can game. Write the slug for readers and for your own ops. That is enough of a job.
No. Latin accents are unaccented. Other scripts stay as letters. There is no romanization table.
The letter is decomposed and the combining mark is dropped. That is Latin folding, not a translation of the word.
This generator emits hyphens only. Mixed separators in one site are a common source of broken links.
Only if the CMS uses similar rules. Check the stored permalink after you publish.
