Lite Tools

URL Slug Generator

Turn any title into a clean, lowercase, SEO-friendly URL slug with live preview and smart options.

Slug result-

How to use

  1. Type an article or page title: the slug updates live as you type.
  2. Adjust the separator, casing, accent stripping and length options to taste.
  3. Click "Copy slug" to use it in your blog or CMS URL field.
  4. Non-Latin characters such as Chinese are removed by default; tick "Keep non-Latin characters" for a Unicode slug.

FAQ

What is a URL slug?
The slug is the readable part of a URL that identifies a page, like my-post-title in example.com/blog/my-post-title. A good slug is short, keyword-rich and contains only lowercase letters, numbers and hyphens.
How do I slugify a Chinese title?
By default non-Latin characters are removed (most CMS setups prefer that). To keep them, tick "Keep non-Latin characters": the result becomes a Unicode slug that browsers percent-encode automatically.
Hyphens or underscores?
Google recommends hyphens (-) over underscores (_): hyphens are treated as word separators, while underscores may merge the whole phrase into a single word.

How to use

  1. Type the title

    Enter an article or page title into the Title / text box. The slug updates live as you type, with no button press needed.

  2. Tune the options

    Lowercase and Strip accents are on by default. Tick Keep non-Latin characters for a Unicode slug, or Remove numbers to drop digits entirely.

  3. Set separator and length

    Pick Hyphen or Underscore from the Separator dropdown; Google recommends hyphens. Set Max length to cap the output, where 0 means unlimited.

  4. Copy into your CMS

    Press Copy slug once the result box shows what you want. Paste it into the URL alias field of your blog or CMS.

About this tool

The slug is the human-readable part of a URL that identifies a page. It is the my-post-title inside example.com/blog/my-post-title. A good slug is short, keyword-rich and built only from lowercase letters, digits and separators. This generator applies those rules to any title in real time. Options cover accent stripping, number removal, a length cap and Unicode preservation. Every option's effect is visible the moment you toggle it.

Blog authors use it to mint clean addresses for every post. SEO specialists rely on it to keep keywords visible in URLs. Static-site developers use it to name routes and files. The default of removing non-Latin characters matches most CMS conventions. Tick Keep non-Latin characters instead, and browsers will percent-encode the resulting Chinese slug automatically, keeping links shareable. Every change lands in the result box at once, so you can compare variants before committing to one.

How it works

Strip accents leans on Unicode NFKD normalization. The letter é is first decomposed into a plain e plus a combining acute accent, then every combining mark is deleted, leaving pure ASCII. German umlauts, French cedillas and Spanish tildes all run through the same pipeline. The keep-non-Latin option skips that step and lets Chinese characters stand as the slug; the browser then percent-encodes them automatically. One CJK character spans three bytes, which becomes nine percent-escape characters in the address bar. This is the standard treatment for English content. Most CMS aliases follow the same rules.

The cost of changing a slug after publication is easy to underestimate. Once a search engine has indexed the address, replacing it means a 301 redirect and weight transfer. A temporary ranking wobble during the switchover is normal, so finalize the alias before publishing instead of reworking it later. How readable the slug is depends on keeping the title's core content words. Dates, random short codes and long runs of filler words are noise to users and crawlers alike. The common compromise keeps the key subject-verb-object terms and drops modifiers, balancing brevity against information.

When to use it

  1. Batch-naming aliases in a CMS

    Rewriting titles into lowercase-hyphen form by hand is slow and misses punctuation. Paste each title, take the compliant alias live, and keep one consistent URL style across an entire bulk publish.

  2. Localizing URLs for multilingual sites

    English sites strip accents; Chinese sites tick keep-non-Latin to mint Unicode slugs. Switching strategies in one place makes it easy to apply different rules per site or per section.

  3. Naming static routes and files

    Static site generators derive routes from filenames. Convert titles into compliant slugs first, and spaces, capitals and special symbols stop producing broken links and escaped file paths.

Tips & tricks

  • Google treats hyphens as word separators but may merge underscore-joined words into one, so prefer Hyphen for search visibility.
  • Remove numbers is off by default; untick it only when titles like 10 Tips for Better SEO in 2025 should lose their digits.
  • Aim for three to five words. Longer slugs risk truncation in search results and look cluttered in analytics reports.

Things to watch

  • Duplicate titles earn a -2 suffix

    When several posts share one title, most CMSs append -2 or -3 to keep the slug unique. The result is a long ugly address. Differentiate the titles before publishing, or adjust the alias by hand.

  • Do not leave a trailing hyphen

    A max-length cut can end the address in a hyphen, such as best-seo-. That looks sloppy and may blur tokenization. Trim the trailing character, taking care not to fuse the last two words.

  • Length caps can cut mid-word

    A strict max length may truncate inside a word, leaving fragments like best-seo-t in the address. Skim the result after capping, or relax the limit a little and regenerate.

Related Tools