URL Slug Generator

Turn a title into a lowercase hyphenated slug by stripping accents and unsafe characters.

What URL Slug Generator helps you do

Turn a title into a lowercase hyphenated slug by stripping accents and unsafe characters. Slugs are the readable identifiers used in URLs, and this produces the format most CMS platforms expect. It is a text transformation only: it does not check whether the slug is already taken.

Slug generation runs entirely in your browser; nothing is uploaded to Haivix.

How it works

The text is normalized to decomposed Unicode, combining marks are removed, and the result is lowercased. Whitespace and punctuation are collapsed into hyphens, and leading or trailing hyphens are trimmed. The output is a plain ASCII-style slug, not a transliteration of scripts that do not use Latin letters.

How to use URL Slug Generator

  1. Paste the title or phrase.
  2. Generate the slug, which lowercases and hyphenates it.
  3. Check the result for readability and duplicates.
  4. Copy the slug into your URL field.

When to use it

  • Create a URL slug from a blog post title.
  • Generate a filename-safe identifier from a heading.
  • Normalize a title for use as an anchor or id.
  • Create a readable path segment for a product or category.
  • Make a slug from a translated title before editing it.
  • Produce a consistent anchor for documentation headings.
  • Create a file-name-safe identifier for an exported report.
  • Normalize a campaign name before using it in a path.
  • Create an anchor for a Markdown heading.

When not to use it

  • Do not use it for non-Latin titles without checking the result; the slug may become empty.
  • Do not assume it checks for duplicate URLs.
  • Do not use it as a full URL encoder for query parameters.

Example

The title Ten Tips for Better SEO becomes ten-tips-for-better-seo. Café and résumé become cafe and resume, while a German title with umlauts loses the marks and keeps the Latin letters. A title written entirely in a non-Latin script may reduce to an empty string, so write a short manual slug in that case and check it against the URL list.

What you can do with URL Slug Generator

  • Lowercase a title or phrase.
  • Strip accents and combining marks.
  • Replace runs of unsafe characters with a hyphen.
  • Trim leading and trailing hyphens.
  • Produce a copy-ready URL segment.
  • Keep the source text in the browser.
  • Remove punctuation that a URL would need to escape.
  • Handle accented Latin letters without manual editing.

Example: create a blog slug

Paste the final title, not the working one. Changing a slug after publishing breaks links, so settle the wording first.

Generate the slug and read it aloud. A short, readable slug is easier to share than a long one with several stop words.

Check the slug against the existing URL list in the CMS. This tool does not detect duplicates.

What to know before you start

  • It removes rather than transliterates some scripts, so non-Latin titles need manual review.
  • Duplicate slugs are not checked against already-used URLs.
  • There is no length cap or stop-word removal.
  • It does not know a CMS's reserved words or routing rules.
  • Changing a slug later is outside the tool's control and can break links.

Common mistakes

  • Changing the slug after the page is published and breaking inbound links.
  • Assuming accents will be transliterated rather than removed.
  • Leaving a trailing hyphen after a dropped word.
  • Using the working title and then changing it before publish.
  • Forgetting to check that the slug is unique in the CMS.
  • Using a slug that is longer than the CMS allows.
  • Assuming a transliteration will be produced for a non-Latin title.
  • Using the same slug for a translated and an original page.

Troubleshooting

If the slug is empty, the title may be entirely non-Latin or only punctuation; write a manual Latin slug.

If two words run together, the source may have had no separator; add a space or hyphen before generating.

If the slug is very long, shorten the title or remove stop words before generating.

If the CMS rejects it, check its own length and character rules; this tool does not enforce a maximum.

If the slug contains a double hyphen, the source had punctuation between two words; edit the slug or the title.

If the slug is hard to read, remove stop words from the title before generating it.

If the slug ends with a number, the title probably did; check that the number is meaningful rather than a draft marker.

If two pages produce the same slug, add a qualifier such as a year or a category.

Related standards and documentation

  • RFC 3986 defines the URI syntax that a slug becomes part of.
  • Unicode normalization form NFD is used before accents are stripped.
Settle the title first
  • Accents are removed, not transliterated.
  • No duplicate check is performed.
  • Short and readable wins.

Frequently Asked Questions