Page & Bell

URL Slug Generator

Turn any headline into a clean, publishable URL slug: lowercase letters and digits only, words joined by hyphens, accents transliterated to plain ASCII (crème brûlée → creme-brulee via Unicode NFKD decomposition), ampersands expanded to “and”, repeated separators collapsed, and edges trimmed. Optional extras handle the judgment calls: strip English stop words (the, a, of…) to shorten keyword-heavy slugs, switch to underscores if a legacy system demands them, and cap length with whole-word truncation so a 60-character limit never slices “management” in half. Bulk mode converts an entire content calendar — one title per line — in a single paste.

Slug

your-slug-appears-here

How to use the url slug generator

  1. Paste a title in Single mode, or switch to Bulk and paste one title per line.
  2. Pick a separator — hyphen unless you have a specific reason not to.
  3. Toggle stop-word removal to tighten long slugs (compare both versions for readability).
  4. Set a max length if your CMS or style guide caps slugs; truncation always lands on a word boundary.
  5. Copy the slug (or Copy all in bulk) and paste into your CMS before publishing.

Why hyphens beat underscores in URLs

Google treats a hyphen as a word separator and an underscore as a word joiner: red-widgets is parsed as the two words “red widgets”, while red_widgets is treated as the single token “red_widgets” — which nobody searches for. This is long-standing, explicitly documented Google guidance, and it dates back to how early tokenizers handled programming identifiers like my_variable. Hyphens also survive better in the wild: an underscore disappears visually when a link is underlined, and some email clients break URLs at underscores. The only common reason to choose underscores is matching an existing system that already uses them — consistency within a site beats either character in the abstract.

Short, keyword-bearing, and stable

A good slug states the topic in three to five words and nothing else. From the title “How to Brew Pour-Over Coffee at Home (Without Fancy Gear)”, the slug brew-pour-over-coffee beats the full 60-character transcription: it keeps the query-bearing words, reads cleanly in the SERP and in shared links, and won't embarrass you when the article gets updated for next year. Drop dates, years, and filler — /best-crm-software can be refreshed forever, while /best-crm-software-2024 broadcasts staleness and forces a URL change later. The stop-word toggle automates the first pass, but review the result: sometimes a stop word carries meaning (to-be-or-not-to-be would be destroyed by it).

Most importantly: never change a published slug casually. The URL is the address where every backlink, bookmark, social share, and ranking signal lives. If you must rename, set a permanent 301 redirect from the old URL to the new one — Google says PageRank passes through 301s, but you still risk weeks of re-indexing churn, and any redirect chain you create later compounds the cost. The time to get the slug right is before you hit publish, which is exactly what this tool is for.

What the generator does, exactly

Input is normalized with NFKD, which decomposes accented characters into a base letter plus combining marks; the marks are stripped, so é → e, ñ → n, ü → u. Letters with no decomposition get explicit mappings (ß → ss, æ → ae, ø → o, ł → l). Apostrophes are removed rather than hyphenated (“don't” → dont, not don-t), & becomes “and”, and every remaining run of non-alphanumeric characters collapses to a single separator. Note that non-Latin scripts (Chinese, Arabic, Cyrillic) have no ASCII decomposition and are removed — for those languages, either keep the native script in the URL (modern browsers and Google handle UTF-8 URLs fine) or transliterate manually.

Frequently asked questions

Should I use hyphens or underscores in URL slugs?

Hyphens. Google documents that hyphens are read as word separators while underscores join words into one token, so red-widgets matches searches for “red widgets” and red_widgets doesn't. Underscores also vanish visually under link underlines. Use underscores only to stay consistent with a legacy URL scheme.

How long should a URL slug be?

Three to five meaningful words is the sweet spot — long enough to state the topic, short enough to read in a SERP and survive content refreshes. There's no hard ranking penalty for long slugs, but every extra word dilutes the signal and increases the odds you'll want to rename later. The max-length option here truncates on whole words, never mid-word.

Does changing a slug after publishing hurt SEO?

It can, badly, if done without a redirect: the old URL 404s and every backlink and ranking signal pointing at it is orphaned. If you must change a slug, add a permanent 301 redirect from old to new. Even with the redirect expect some re-indexing churn, so treat renames as rare, deliberate events — not housekeeping.

Should I remove stop words like “the” and “of” from slugs?

Usually yes for long titles — “the-history-of-the-roman-empire” tightens to “history-roman-empire” with no loss of meaning. But it's a readability call, not a ranking trick: Google handles stop words fine either way. Keep them when removal changes meaning or produces something awkward; that's why it's a toggle here, not the default.

What happens to accented characters like é or ü?

They're transliterated to plain ASCII: the tool applies Unicode NFKD normalization, which splits é into e plus a combining accent, then strips the accent. Special letters without a decomposition get explicit mappings (ß→ss, æ→ae, ø→o). Result: café-crème becomes cafe-creme — safe in every browser, CMS, and analytics tool.

Are uppercase letters allowed in URLs?

Technically yes — URL paths are case-sensitive — and that's exactly the problem: /About and /about are different URLs that can both resolve, splitting your link equity and creating duplicate-content noise. The universal convention is all-lowercase, which this generator enforces, so there's only ever one canonical form of each slug.

Related tools

Learn more