Convert any title into a clean, SEO-friendly URL slug.
Turn any title, heading, or phrase into a clean, URL-safe slug. Lowercase, hyphen-separated, with accents stripped and special characters removed. The slug format major CMSs and SEO tools expect, generated entirely in your browser. Nothing is sent to a server.
A URL slug is the human-readable part of a URL that identifies a specific page. The segment after the domain. In textkit.tech/url-slug, the slug is url-slug. Slugs are the URL handles that show up in Google search results, social media previews, and browser address bars. Done well, they're invisible. Done badly, they cost you click-through rate, ranking signal, and AI search citation probability.
The consensus has crystallized over fifteen years of SEO practice into seven rules. The slug generator above applies all seven automatically:
/My-Post and /my-post as different URLs, splitting link equity.my-blog-post reads as three words to Google. my_blog_post reads as one.how-make-markdown-table.café → cafe, São Paulo → sao-paulo. Otherwise the URL bar shows hex sequences.| Title | Slug |
|---|---|
| 10 Best Word Counters for Writers in 2026 | best-word-counters-writers-2026 |
| How Do I Convert Excel to Markdown Table? | convert-excel-markdown-table |
| The Complete Guide to URL Slug SEO | url-slug-seo-complete-guide |
| Café Culture in São Paulo: A Walking Tour | cafe-culture-sao-paulo-walking-tour |
| Why ChatGPT Output Doesn't Render Properly | chatgpt-output-not-rendering |
The generator transliterates accented Latin characters automatically using Unicode NFD normalization. Reference table:
| Accented | Transliterated |
|---|---|
| é, è, ê, ë | e |
| á, à, â, ä, ã | a |
| í, ì, î, ï | i |
| ó, ò, ô, ö, õ | o |
| ú, ù, û, ü | u |
| ñ | n |
| ç | c |
WordPress: Settings → Permalinks → Post name. Override the auto-generated slug on each post by editing the URL field beneath the title. WordPress's default slug generator keeps stop words, which most SEO practitioners strip manually.
Webflow: Each collection item has a "Slug" field. Webflow auto-generates from the title; override manually for SEO control. Webflow does not strip stop words by default.
Ghost: The slug is generated from the title and editable in the post sidebar. Ghost handles transliteration of accented characters automatically and is more aggressive about stop-word removal than WordPress.
Shopify: Each product page has a URL handle in the format /products/{handle}. Edit the handle in the product editor under "URL handle". Shopify lowercases automatically but doesn't strip stop words.
Notion: Notion-published pages use the title as the slug with limited control. For SEO-critical pages, publish through a static site generator like Astro, Eleventy, or Next.js where slug control is explicit.
This part of slug SEO didn't exist three years ago. ChatGPT, Perplexity, Claude, and Gemini cite URLs as sources when generating answers. And they don't fully render every candidate page. They look at high-signal metadata: page title, meta description, sampled body content, and the URL itself. A URL slug that clearly states the page topic is more likely to be selected as a citation than one that doesn't. example.com/post-4729 tells an AI nothing. example.com/url-slug-seo-the-definitive-guide-2026 tells it everything in one glance.
A URL slug is the human-readable part of a URL that identifies the page. The part after the domain. In "textkit.tech/url-slug-generator", the slug is "url-slug-generator". Good slugs are short, lowercase, hyphenated, and descriptive.
Google uses the slug as a ranking signal and a click-through signal. Clear slugs that contain the target keyword earn a small ranking boost and a measurable CTR lift in search results. Backlinko's analysis of millions of SERPs showed up to 39% higher CTR for keyword-matched URLs.
Hyphens. Google parses hyphens as word separators ("my-blog-post" = three words). Underscores are treated as word joiners ("my_blog_post" = one word). Always use hyphens for SEO. The generator above never produces underscores.
Aim for under 60 characters. Google truncates URLs in search results around 60–70 characters. Slugs longer than that look messy in SERPs and lose CTR.
For most blog and content URLs, yes. Drop articles and prepositions to keep slugs short. Exception: when the stop word is essential to meaning (e.g., "war-of-the-worlds"), leave it in.
Accents are stripped via Unicode NFD normalization. "naïve" becomes "naive", "São Paulo" becomes "sao-paulo". This matches how WordPress, Ghost, and most CMSs generate slugs.
Non-Latin characters are removed by default because most URL routing systems prefer ASCII slugs. Modern Google handles non-Latin URLs reasonably well, but for pages that need to be shareable across multiple scripts, transliterated slugs remain safer.
Yes, but every change requires a 301 redirect from the old URL to the new one to preserve SEO equity and avoid 404s for incoming links. Multiple redirect hops drain link equity, so commit to a slug before publishing if possible.