Slug Generator

A slug is the human-readable part of a URL after the domain and path. In https://yoursite.com/blog/how-to-start-a-podcast, the slug is how-to-start-a-podcast. It's the identifier your CMS uses to route the request to the right page, and the piece Google reads for keyword signals, breadcrumb display, and query matching in the SERP. Good slugs are short, lowercase, hyphen-separated, keyword-forward, and don't include stopwords, dates, or post IDs. Bad slugs look like /post?p=8472 or /the-article-about-how-to-start-a-new-podcast-in-2024-complete-guide. Our slug generator takes one title or a whole list of them, applies the rules automatically, and outputs clean slugs you can paste into any CMS without fighting the auto-sanitizer. Paste titles into Titles (one per line), pick a Case (kebab, snake, camel, Pascal), choose a Separator (dash, underscore, or none), toggle stopword removal, and export as CSV for bulk migrations or copy single slugs one at a time. The tool runs client-side for instant results.

A slug is just the identifier at the end of the URL: how-to-start-a-podcast. A permalink is the full URL including scheme, domain, and path: https://yoursite.com/blog/how-to-start-a-podcast. Slugs are portable across CMSs (they work anywhere that accepts a URL-safe string); permalinks are site-specific because they include your domain and path structure. Most writers and developers need slugs, not permalinks, because their CMS builds the surrounding URL from a template configured once and applied to every new post. Use our slug generator when you have a list of titles to convert at scale, want to export CSV for a site migration, or need consistent case formatting (kebab for URLs, camel for JSON keys, snake for filenames and database fields). Switch to our permalink generator when you need the full URL preview before publishing, or when your CMS's permalink structure varies by post type (blog vs product vs category) and you want to see the final link rendered.

Paste one or many titles into Titles (one per line). Each title becomes a slug on its own line in the output pane. Pick a Case: kebab-case (lowercase-with-dashes, the URL standard), snake_case (lowercase_with_underscores, common in Python and filenames), camelCase (for JavaScript keys), or PascalCase (for class names and React components). Pick a Separator if kebab or snake: dash (the standard), underscore, or none. Toggle Remove stopwords to strip 'the', 'of', 'a', 'and', 'to' and tighten the slug without losing keyword weight. Move the Max length slider to cap at 60 or shorter for product pages. Hit generate. You get a clean slug per title plus a copy-all button and a CSV download for bulk use. The tool runs entirely client-side, so nothing is uploaded, and collisions (two titles producing the same slug after normalization) get flagged automatically so you can disambiguate before publishing. For full URL previews with CMS path patterns, switch to our permalink generator.

Paste all your titles into Titles (one per line), one title per line, and hit generate. The output appears as a two-column table: original title next to clean slug. Hit Download CSV to export the whole list for migrations, Notion imports, or CMS bulk upload. The tool handles 500 titles per run without lag because it runs entirely in your browser. If two titles produce the same slug (common: 'How to Start a Podcast' and 'How to Start a Podcast: Part 2' both trim to the same words), we flag the collision in red so you can add a suffix or regenerate with stopwords kept. For WordPress or Shopify migrations where you need the full URL including path prefix, use our permalink generator with a CMS preset instead. Bulk mode is the main reason migrators and agencies pick this tool over a single-slug generator. Export the CSV, review collisions, and import directly into your CMS.

Use dashes for URL slugs. Google has said explicitly that hyphens are treated as word separators in URLs, while underscores are treated as joiners. A slug like /how-to-start-a-podcast reads to Google as the phrase 'how to start a podcast'. The slug /how_to_start_a_podcast reads as one long word 'howtostartapodcast', which kills keyword matching. Use underscores only for filenames, variable names, or systems that require them (some CMSs, some database fields, some APIs). Our generator defaults to kebab-case with dashes for a reason. Switch to snake_case only when your CMS or route pattern demands it. A few frameworks (Ruby on Rails, Django) parse both as separators internally, but the rendered URL in the SERP and share cards still reads cleaner with dashes. The readability difference matters for click-through rate: users trust clean URLs with dashes over underscored strings that look like server paths. Pick dashes unless you have a concrete technical reason not to.

Aim for three to five words and under 60 characters. A slug like podcast-launch-checklist (24 characters, three words) outranks how-to-launch-your-first-podcast-in-2026-the-complete-guide (60-plus characters, ten words) for the same query nearly every time. Shorter slugs have higher keyword density, survive truncation in SERP snippets and share previews, and are easier to remember when typed by hand. Move the Max length slider to 60 by default. Drop to 40 for product pages or category archives where the surrounding path already carries context. Push to 80 only for long-tail informational posts where cutting any word loses the query match. Our generator truncates at word boundaries and drops stopwords first, so a 90-character title trimmed to 60 still reads cleanly. Shorter slugs also load faster in analytics dashboards, fit cleanly in social share cards, and reduce the chance of encoding errors when copied across systems. For a full on-page SEO check of the final URL, run it through our SEO checklist.

Usually yes. Google ignores common stopwords ('a', 'an', 'the', 'of', 'to', 'and') when matching slugs to queries, so removing them doesn't cost you keyword relevance. It does shorten the URL, bump keyword density in the URL string, and improve readability. 'How to Start a Podcast' becomes start-podcast rather than how-to-start-a-podcast. Both rank the same for the query; the shorter one looks better in share cards. Exceptions: keep stopwords when removing them changes the meaning ('how-to' vs 'how' reads differently in breadcrumbs) or produces a collision with another slug on your site. Our tool's Remove stopwords toggle is on by default. Turn it off when you need the slug to read as a natural phrase, when translating for international SEO (stopwords matter more in some languages), or when your editorial style guide requires full-title slugs. Keeping stopwords can also help when your site's breadcrumb or URL structure appears in rich results.

Yes, but lightly. Google lists the URL as a ranking factor, and keyword-forward slugs give a small but consistent boost, especially for long-tail queries where the slug exactly matches the search phrase. The larger effects are indirect: click-through rate in the SERP (readable slugs get more clicks than /p?id=8472), social share behavior (clean URLs travel better), and breadcrumb display (Google sometimes shows the slug path as a breadcrumb). A perfect slug won't save a bad page, though. Content quality, topical authority, backlinks, and page experience weigh far more. Treat the slug as free optimization: do it right once, never think about it again. Our generator produces keyword-forward slugs that check every box automatically. In competitive verticals, the cumulative effect of clean slugs across 50 or 100 pages can lift site-wide authority signals because Google sees consistent, keyword-aligned URL structures. For broader on-page SEO checks beyond the URL, run your live page through our SEO checklist for a 20-item audit.

Slug collisions happen when two different titles produce the same slug after normalization. 'How to Start a Podcast' and 'How to Start a Podcast in 2026' both trim to start-podcast if stopwords and dates are stripped. Our generator flags collisions in red inside the output table so you catch them before publishing. Four common fixes. First, keep one stopword: 'start-podcast' vs 'start-podcast-guide'. Second, add a disambiguating noun: 'podcast-launch' vs 'podcast-monetization'. Third, add a year suffix (only if the post is dated content, not evergreen): 'podcast-launch' vs 'podcast-launch-2026'. Fourth, regenerate one title with stopwords kept on. Most CMSs auto-append -2 or -3 on upload when they detect a duplicate, but that's an ugly fallback. Fix it at the slug-generation step. For migrations where hundreds of slugs might collide, export the CSV and spot-check the red rows before importing. Collisions are more common on category pages and tag archives, where titles follow templates, so review those sections separately during bulk generation.

Only if the current slug is actively hurting you. Changing a slug on a live page requires a 301 redirect from the old URL to the new one, or every backlink, bookmark, and indexed page returns a 404 and authority bleeds out. That's expensive. Only change a slug when the current one is genuinely broken: contains a typo, includes a date that ages the post, has a wrong keyword, or is so long it gets truncated in SERPs. Don't change slugs for cosmetic reasons. If you do change one, add the 301 redirect first (before the new slug goes live), then publish, then resubmit the sitemap in Search Console. For bulk slug migrations during a site replatform, export the old-to-new mapping from our tool as CSV, feed it into your CMS's redirect manager, and test three sample URLs before flipping DNS. Our permalink generator handles the full URL preview for migrations.