SEO & URLs

Slug Generator Online Free — Convert Any Title to a URL-Safe Slug

A bad URL slug costs you rankings, breaks links, and confuses users. A good one reinforces your keyword, reads cleanly at a glance, and never needs changing after publishing. This guide explains what a URL slug is, the exact rules for building one, and how to generate a perfect slug from any title in seconds — for free, in your browser.

By FusionPDF Team · July 2, 2026 · 8 min read · Updated July 2026

Key Takeaways

A URL slug is the human-readable path segment after the domain: /blog/my-article-title
Always use hyphens, never underscores — Google treats underscores as word joiners, not separators (confirmed by John Mueller)
Keep slugs under 60-70 characters and put the primary keyword first
Accented characters (é, ü, ñ) must be transliterated to ASCII equivalents before use in slugs
Changing a slug after publishing requires a 301 redirect — or you lose rankings and break links
Use FusionPDF's free slug generator to convert any title in one click

Most people pick a URL slug by instinct and move on. That works — until you publish the wrong one, need to change it six months later, and realize you've broken dozens of inbound links. Getting the slug right the first time is a five-second decision that saves hours of redirect management later.

What Is a URL Slug?

A URL slug is the human-readable segment of a URL that identifies a specific page, coming after the domain and any subdirectory path. In https://example.com/blog/my-article-title, the slug is my-article-title. Slugs replace spaces and special characters with hyphens, use only lowercase ASCII letters, numbers, and hyphens, and describe the page content in a way both users and search engines can parse at a glance.

The term "slug" comes from newspaper print production, where it referred to a short label identifying a story internally before publication. On the web, it serves the same purpose: a concise, machine-safe identifier for a piece of content.

Slugs appear in multiple contexts across a typical website:

Blog posts: /blog/how-to-extract-text-from-pdf
Product pages: /products/wireless-noise-cancelling-headphones
Category pages: /category/digital-marketing
Author pages: /author/jane-smith
Tag pages: /tag/javascript

The slug is part of the page's canonical URL. It factors into search engine ranking, user click-through from SERPs, and the shareability of links in messages and social media. A clear, keyword-rich slug reinforces all three.

How to Generate a Slug Online Free (3 Steps)

FusionPDF's slug generator converts any title or text string into a clean, URL-safe slug instantly. It lowercases everything, replaces spaces with hyphens, strips accents and special characters, removes consecutive hyphens, and trims leading and trailing hyphens — all in real time, with no account required.

Paste your title. Go to fusionpdf.pro/slug-generator and paste your page title, article headline, or product name into the input field. You can also type directly — the slug updates live as you type.

Get your slug instantly. The tool processes your input in real time: lowercase conversion, space-to-hyphen replacement, accent stripping (é→e, ü→u, ñ→n), special character removal, and consecutive hyphen collapsing. The result appears immediately below the input field.

Copy and paste. Click the Copy button to copy the slug to your clipboard. Paste it directly into your CMS slug field, your static site generator's frontmatter, or your URL configuration. No further editing needed.

Tip: If your target keyword phrase is different from your article title (e.g., your title is "7 Ways to Speed Up Your Website in 2026" but your target keyword is "website speed optimization"), paste the keyword phrase into the generator rather than the full title. Your slug should reflect the keyword, not the headline.

The Rules: What Makes a Good Slug

A well-formed URL slug follows a consistent set of rules that make it readable for humans, parseable by search engines, and safe across all web infrastructure. There are five non-negotiable rules and two best-practice guidelines that apply to every slug you generate.

Non-negotiable rules

Lowercase only. URLs are case-sensitive on most servers. My-Article and my-article are two different URLs. Always lowercase.
Hyphens as word separators. Use hyphens between words: url-slug-generator. Never use spaces (they become %20 when encoded), underscores, or dots as separators.
No special characters or punctuation. Apostrophes, quotes, colons, slashes, question marks, ampersands, and percent signs all have special meaning in URLs or require encoding. Strip them entirely.
ASCII characters only. Accented characters (é, ü, ö, ñ, ç) and non-Latin scripts (Chinese, Arabic, Japanese, Korean, Cyrillic) must be handled explicitly — see the next section.
No consecutive or trailing hyphens. my--article-title- is malformed. Collapse multiple hyphens into one and strip leading/trailing hyphens.

Best-practice guidelines

Maximum 60-70 characters. Google truncates URLs in search results, and long slugs dilute the keyword signal. If your slug runs long, cut stop words and filler — keep the core keyword phrase.
Keyword first. Search engines give more weight to terms that appear earlier in the URL path. Put your primary keyword at the start of the slug: slug-generator-online-free outperforms free-online-slug-generator-tool for the target keyword "slug generator".

Google's URL structure guidelines recommend using words rather than IDs in URLs, using hyphens to separate words, and keeping URLs as simple and descriptive as possible. The guidance explicitly states that a clean URL structure helps both users and search engines understand the content of a page. Google Search Central — URL structure best practices (developers.google.com/search/docs/crawling-indexing/url-structure)

Hyphens vs Underscores for SEO

This is settled: use hyphens. Google treats hyphens as word separators and underscores as word joiners. A slug like slug_generator is read by Google as a single token "sluggenerator" — the page will not rank for "slug" or "generator" individually. A slug like slug-generator is read as two separate words, each contributing to ranking relevance.

This distinction was confirmed explicitly by Google's John Mueller in multiple public posts and videos. In a 2016 Google Webmaster Hangout, Mueller stated directly: "We do use hyphens as word separators in URLs. We generally don't use underscores as word separators." The recommendation has not changed since.

≠

slug_generator is NOT slug + generator to Google Underscores join words in URLs — Google reads slug_generator as the single token "sluggenerator". Hyphens separate them: slug-generator = "slug" + "generator". This matters for every keyword in your URL path.

The practical implication: if your current URLs use underscores, you should migrate to hyphens with 301 redirects. It's not a catastrophic ranking factor, but it is a confirmed disadvantage, and it's easy to fix at site launch. Once a URL is published and indexed, changing it requires redirect management — another reason to get it right the first time.

Exception: file extensions and query parameters. The hyphen-vs-underscore rule applies to the readable slug portion of the URL. File extensions (.html, .php) and query parameter names (?product_id=) follow their own conventions and are not subject to the same SEO guidance.

Handling Accented and Non-Latin Characters

Accented characters and non-ASCII scripts are technically valid in URLs (they're called IRIs — Internationalized Resource Identifiers), but they're not slug-safe in practice. Browsers percent-encode them on copy, making links like https://example.com/caf%C3%A9 in the address bar instead of https://example.com/café. The readable form is fragile and inconsistently handled across tools. The safe approach is transliteration to ASCII before the slug is created.

Latin-script accented characters

These have direct ASCII equivalents and should always be transliterated:

é, è, ê, ë → e
à, â, ä → a
ü, û, ù → u
ö, ô → o
ñ → n
ç → c
ß → ss
æ → ae
ø → o

FusionPDF's slug generator handles all standard Latin diacritics automatically using Unicode normalization (NFD decomposition followed by stripping the combining marks).

Non-Latin scripts (Chinese, Japanese, Arabic, Korean, Cyrillic)

For non-Latin scripts, there are two approaches:

Transliteration: Convert to a Latin phonetic equivalent. For a Japanese page titled "東京" (Tokyo), the slug would be tokyo. For Arabic, a romanized transliteration of the title is used. This is the best approach for SEO if the primary audience uses the Latin script.
Removal: Strip non-transliterable characters and slug the remaining Latin content in the title. If the title is entirely non-Latin with no transliterable content, the result is an empty slug — in that case, use a manual keyword-based slug instead.

Multilingual sites: If you publish in multiple languages with separate URL paths (e.g., /fr/, /de/), each language's slug should use transliterated ASCII even in the localized path. Native-script URLs in the slug are technically valid but introduce fragility and reduce shareability across contexts.

Slug Rules per CMS

Every CMS generates slugs differently from post titles. Some are opinionated and enforce good defaults automatically; others produce slugs that need manual cleanup. Knowing your CMS's behavior prevents you from publishing a bad slug by accident — especially on platforms that include stop words, dates, or numeric IDs in URLs by default.

CMS	Default slug behavior	Editable before publish?	Watch out for
WordPress	Auto-generates from post title: lowercased, spaces to hyphens, stop words included	Yes — editable in the block editor sidebar	Default permalink structure may include `/category/` or dates. Change to "Post name" in Settings → Permalinks.
Shopify	Auto-generates from product title: lowercased, spaces to hyphens, special chars stripped	Yes — editable in the product page URL and handle field	Shopify forces a `/products/` prefix. You cannot change this without a third-party app. Handles must be unique store-wide.
Ghost	Auto-generates from post title at creation time: lowercased, spaces to hyphens	Yes — editable in post settings panel	Ghost does not auto-redirect on slug change. Set up redirects manually in `redirects.yaml` if you change a published slug.
Jekyll	Derives slug from the filename: `2026-07-02-my-post-title.md` → slug is `my-post-title`	Yes — set `slug:` in frontmatter to override	The date prefix in the filename does not appear in the URL by default (depends on permalink config). Set `permalink: /:slug/` in `_config.yml`.
Hugo	Derives from filename or frontmatter `slug:` field. Falls back to `title:` slugified if neither is set.	Yes — set `slug:` in frontmatter explicitly	Hugo's default slugification behavior can vary by version. Always set `slug:` explicitly in frontmatter to avoid surprises.
Gatsby	No built-in slug generation — slug is whatever path you define in `createPage()` in `gatsby-node.js`	Yes — fully programmatic, defined by the developer	You are responsible for your own slug generation logic. Use a slug library (e.g., `slugify` npm package) in your build pipeline, or use FusionPDF's generator to pre-generate slugs before adding content.

Stop Words in Slugs: When to Keep or Remove Them

Stop words are common words with little semantic weight on their own: "a", "the", "and", "in", "of", "to", "for". Removing them from slugs shortens the URL and concentrates the keyword signal. But the decision is not always obvious — sometimes removing a stop word changes meaning or kills readability. The rule is context-dependent, not absolute.

When to remove stop words

The slug is running long (approaching 70 characters) and the stop word adds no meaning
The remaining slug still reads clearly and unambiguously: how-to-generate-url-slug reads as well as how-to-generate-a-url-slug
The stop word appears between two keyword terms that are just as clear without it: tools-for-pdf-editing → pdf-editing-tools

When to keep stop words

Removing the stop word creates ambiguity: guide-to-not-doing-this loses its meaning if "not" is stripped
The stop word is part of a branded term or proper name: "Lord of the Rings" should not become lord-rings
The slug is already short and readable — there is no benefit to trimming further
Your target keyword phrase includes the stop word (e.g., if you are targeting "how to generate a slug", keeping "how-to" is worth it for keyword match)

Google has stated publicly that it does not penalize stop words in URLs, and their presence or absence is not a direct ranking factor. The primary reason to remove them is to keep URLs short and keyword-focused — not to avoid a penalty. Google Search Central documentation; John Mueller, Google Webmaster Hangout, 2019

URL Best Practices: Canonicals, 301 Redirects, Trailing Slashes

Getting the slug right is only half the job. The other half is managing what happens to the URL over time — especially when slugs change after a page is published. Three practices prevent the most common URL-related SEO problems: canonical tags, 301 redirects, and consistent trailing slash handling.

Canonical slugs

A canonical URL is the definitive version of a page, declared with a <link rel="canonical"> tag in the page's <head>. When the same content is accessible at multiple URLs (with and without trailing slash, with different query parameters, via HTTP and HTTPS), the canonical tells search engines which version to index and which to accumulate ranking signals to. The canonical URL should always point to the clean, slug-based URL — not a URL with query parameters or session IDs.

301 redirects after slug changes

If you change a slug after a page is published and indexed, you must set up a 301 redirect from the old URL to the new one. A 301 (permanent redirect) passes approximately 90-99% of ranking authority from the old URL to the new one and prevents the old URL from returning a 404 error. Without a redirect:

All inbound links pointing to the old slug become broken
The old URL returns 404, which signals to Google that the content is gone
Any accumulated rankings and backlink equity for the old URL are lost

Set up the redirect before or immediately after publishing the new slug. Do not wait for the 404s to accumulate.

Trailing slashes

Trailing slashes create a duplicate content issue if not handled consistently. /blog/my-slug and /blog/my-slug/ are technically different URLs. Most web servers and frameworks treat them as the same page, but search engines will see two versions unless one redirects to the other or the canonical resolves the conflict. Pick one convention for your site and enforce it globally — either always include the trailing slash or never include it. The choice itself does not affect rankings; inconsistency does.

Comparison: FusionPDF vs Slugify.online vs Manual Regex

Several tools generate URL slugs from text. The differences come down to how they handle accented characters, what customization they offer, and whether any data leaves your device. Here is a direct comparison of the three most common options.

Feature	FusionPDF Slug Generator	Slugify.online	Manual regex
Accent transliteration (é→e, ü→u)	Yes — automatic	Yes	Requires custom char map
Real-time preview	Yes	Yes	No — run script manually
One-click copy	Yes	Yes	No
No server upload	Yes — runs in browser	Likely — but not documented	Yes — runs locally
No account required	Yes	Yes	Yes
Works without installing anything	Yes	Yes	Requires coding environment
Handles non-Latin scripts	Strips non-ASCII safely	Varies by input	Requires additional logic

Manual regex in code (Node.js, Python, PHP) is the right choice when slug generation is part of an automated pipeline — a build script, a CMS plugin, or a content import tool. For one-off title-to-slug conversion while writing content, a browser-based tool is faster and requires no setup. The regex pattern for a standard slug is roughly: lowercase the string, NFD-normalize and strip combining marks, replace non-alphanumeric characters with hyphens, collapse consecutive hyphens, and trim. FusionPDF's tool implements exactly this logic in the browser.

Frequently asked questions

Should a slug contain keywords?

Yes — your primary keyword should appear in the slug, ideally near the start. Google uses the URL path as a relevance signal, and a keyword-first slug reinforces what the page is about. Keep the slug to the core keyword phrase and drop filler words. For example, for a page targeting "best project management tools", the slug best-project-management-tools is better than the-7-best-project-management-tools-for-2026. Shorter, keyword-forward slugs also perform better in SERP click-through, since users can read the URL and confirm relevance before clicking.

What is the maximum slug length for SEO?

Google recommends keeping slugs short. As a practical guideline, aim for 60-70 characters or fewer — enough to include your primary keyword without padding. Google truncates URLs in search results at around 70-80 characters total, and unnecessarily long slugs dilute the keyword signal by adding terms with low relevance weight. Shorter slugs are also easier to copy, share in messages, and remember. If your slug is running long, identify which words are not load-bearing for the keyword match and remove them first.

Do hyphens help SEO?

Hyphens are the correct word separator in URLs for SEO. Google treats hyphens as word separators, so slug-generator is read as two distinct words: "slug" and "generator". Underscores, by contrast, are treated as word joiners — slug_generator is read as the single token "sluggenerator", which prevents the page from ranking for either word individually. This behavior was confirmed by Google's John Mueller in multiple public statements over the years. Always use hyphens. If your existing site uses underscores, migrate with 301 redirects.

What happens if I change a slug after publishing?

Changing a slug after a page is indexed breaks any inbound links pointing to the old URL and causes the old URL to return a 404 error — which signals to Google that the content no longer exists. To change a slug safely: first set up a 301 redirect from the old URL to the new one, then update any internal links on your site pointing to the old URL, and submit the new URL to Google Search Console for re-indexing. The 301 redirect passes most of the ranking authority to the new URL, but the transition can take several weeks to fully propagate. For high-traffic pages with significant backlinks, avoid slug changes unless absolutely necessary.

Does capitalization matter in URL slugs?

Yes. URLs are case-sensitive on most web servers running Linux with Apache or Nginx. A slug like Slug-Generator and slug-generator are treated as two different URLs, which creates duplicate content and splits ranking signals between them. Always use fully lowercase slugs. FusionPDF's slug generator converts everything to lowercase automatically. If you have existing URLs with uppercase characters, set up 301 redirects from the mixed-case versions to the all-lowercase canonical URL.

Generate a Clean URL Slug — Free, Instant, No Sign-Up

Paste any title and get a ready-to-use slug in one click. Handles accents, special characters, and consecutive hyphens automatically.

Open Slug Generator → Text Case Converter →