Free tool · No signup

Free URL Slug Generator

Paste any title and get a clean, SEO-friendly URL slug instantly — lowercased, hyphenated, diacritics transliterated, and length-capped. Pick the language and the slug adapts: Latin scripts get kebab-case ASCII, Chinese keeps native characters so the URL stays readable to your audience.

Loading…

Free · Unlimited checks · No signup required

How it works

Step 1

Paste your title

The headline of your article, product, or landing page — exactly as you'd publish it.

Step 2

Pick the language

Slug rules differ by script. Latin languages transliterate to ASCII; Chinese keeps native characters.

Step 3

Copy the slug

It updates live as you type. One click copies the slug or the full URL preview.

Step 4

Use it in your CMS

Paste it into the permalink field before you publish — changing it later costs you redirects.

Why it matters

A clean slug is a ranking signal you set once and keep forever.

The URL is one of the first things search and AI engines read about a page, and it shows up verbatim in results, citations, and shared links. A short, hyphenated, keyword-bearing slug tells engines and humans what the page is about before they click. A slug full of stop words, dates, or raw punctuation does the opposite — and unlike content, you can't quietly revise it later without a redirect.

Hyphens, lowercase, and length aren't style choices — they're compatibility rules.

Google treats hyphens as word separators but reads underscores as joiners, so my_great_post is effectively one mashed word. Mixed-case URLs create duplicate-content risk because servers may treat /Page and /page as different resources. And very long slugs get truncated in results and look like spam in shared links. Lowercase, hyphenated, and under about 80 characters is the safe envelope everywhere.

Non-English titles need script-aware handling, not a generic regex.

Naively stripping non-ASCII characters turns 'Cómo ahorrar más' into 'cmo-ahorrar-ms' — broken words that help nobody. Proper transliteration maps ó→o and ñ→n so the slug stays readable. Chinese is the opposite case: transliterating to pinyin makes slugs 5–8x longer and unreadable to the audience, so keeping native characters (which browsers render fine) is the better choice.

With Meev

Meev generates correct slugs for every article it publishes — in any language.

This tool is the exact slug logic Meev's publishing engine runs on every article: script-aware, transliterated, length-capped, language-matched. The difference is Meev also writes the article, builds the metadata, and publishes it to your site automatically.

  • Every auto-published article ships with a clean, language-correct slug — no manual permalink edits
  • Slugs, titles, and metadata are generated together so they reinforce the same keyword
  • AI visibility tracking shows whether engines actually cite the URLs you publish

Frequently asked

Why hyphens instead of underscores in URL slugs?

Google explicitly treats hyphens as word separators and underscores as word joiners. A slug like seo_cost_guide reads to the engine as one token, while seo-cost-guide reads as three words it can match against queries. Every major CMS defaults to hyphens for this reason — there's no situation where underscores in a slug are the better choice.

What's the ideal slug length?

Three to five words, and well under 80 characters. Short slugs are easier to read in search results, get truncated less in shares and citations, and force you to keep only the words that matter. This tool caps Latin-script slugs at 80 characters and Chinese slugs at 30 characters, which keeps the encoded URL comfortably under common limits.

Should slugs contain stop words like 'the', 'a', and 'of'?

Usually drop them. 'how-to-write-a-meta-description' works fine as 'write-meta-description' — shorter, same meaning, same keywords. Keep a stop word only when removing it changes the meaning or makes the slug read wrong. Engines don't penalize stop words; they just waste characters you could spend on real words.

Can I change a slug after the page is published?

You can, but every change needs a 301 redirect from the old URL to the new one, or you lose the links, rankings, and AI citations the old URL accumulated. That's why it pays to get the slug right before you hit publish. If you must change one, set the redirect in the same deploy and update your internal links to point at the new URL directly.

How should slugs work for non-English content?

It depends on the script. For Latin-based languages (Spanish, French, German, Portuguese), transliterate accents to plain ASCII — ó becomes o, ü becomes u — so the slug works everywhere. For Chinese, keep native characters: browsers render them correctly, they're far shorter than pinyin, and they're readable to the audience actually clicking the link. This tool routes by language automatically.

Stop fixing pages one at a time.

Meev tracks your visibility across every major AI search surface and publishes quality-gated content that earns citations — automatically.

Card required, no charge until day 8. Cancel anytime.

More free tools

View all →