URL Slugs: Write Web Addresses That Last with Free Online Tools
A URL slug is the human-readable tail of a web address: the part after the domain and any folder path. In https://example.com/guides/url-slug-basics, the slug is url-slug-basics. It tells visitors and search engines what the page is about, and—unlike a query string—it is meant to stay fixed for the life of the page. That permanence is why slugs deserve more thought than most people give them.
Plenty of free online tools will turn a headline into a hyphenated string in a second, and many of them do the job well. The trouble starts when you treat the output as a final decision. A slug is not a cleaned-up title; it is a contract with every future link, bookmark, social post and search result. Once a page is indexed, changing that string is possible, but it is rarely free.
What a slug actually is (and what it is not)#
A slug is the final, path-level identifier for a single page. In a full URL such as https://siteb.biz/text-tools/url-slug-basics, the domain is siteb.biz, the folder path is /text-tools/, and the slug is url-slug-basics. It is not the page title, not the meta description, and not the headline that appears above the article. Some content management systems generate a slug automatically from the title, but the two fields serve different purposes: the title can change with a redesign or a seasonal campaign; the slug should not, because every external link points to it.
| Part of the URL | Example | What it does |
|---|---|---|
| Protocol + domain | https://siteb.biz | Identifies the site |
| Folder path | /text-tools/ | Groups related pages |
| Slug | /url-slug-basics | Identifies one specific page |
| Query string | ?id=123 | Passes temporary data; usually bad for permanence |
Why a slug is not the title with hyphens#
A headline is written to catch attention in a feed; a slug is written to survive for years in a link. That difference explains why you should strip marketing language, year numbers and product version strings from slugs. A title like '10 Best Free Online Tools for 2024' becomes a slug such as 10-best-free-online-tools-for-2024, which looks fine today and broken in January 2025. The same applies to promotional phrases: 'Limited-Time Offer' ages badly, while 'offer' stays neutral. Keep the noun, lose the adjective.
- A title can change every season; a slug should change almost never.
- Marketing words such as 'ultimate', 'best' and 'free' date quickly and add no meaning.
- Numbers are fine when they are part of the topic, not the calendar.
- Hyphens are the only safe separator; underscores and spaces break in email and some social platforms.
- Lowercase is safer because most servers treat URLs as case-sensitive.
The transliteration question: accents, diacritics and non-Latin scripts#
Accented characters are valid in URLs, but they create two problems. Browsers usually display ü as ü while the underlying address is percent-encoded as %C3%BC, which is ugly in plain text and fragile when copied between systems. For German, the convention is to transliterate ü to ue, ä to ae and ö to oe, but the shorter 'u' form is acceptable in many international contexts. French and Spanish accents are more often dropped: résumé becomes resume, not reesume. For non-Latin scripts—Cyrillic, Arabic, Chinese—percent-encoding is unavoidable unless you use a Latin transliteration layer, which introduces its own inconsistencies.
| Original word | Recommended slug | Reason |
|---|---|---|
| Über | uber | Short and recognisable; German formal 'ueber' is also valid |
| Café | cafe | Drop accents in French and Spanish loanwords |
| München | muenchen | German 'ue' convention for umlauts |
| 日本語 | nihongo | Latin transliteration avoids percent-encoded URLs |
| naïve | naive | Diaeresis is usually dropped in English contexts |
If your audience is almost entirely German and your site is German-language, 'ueber' is often the safer choice; for an international audience, 'uber' is easier to type.
Stop words, length and dates in URLs#
Stop words—the, a, an, of, and—can usually be removed from slugs without losing meaning. 'Guide to URL Slugs' becomes url-slugs-guide or guide-url-slugs; both are readable. Length matters because long slugs truncate in search results, social previews and email clients. Aim for roughly 40 to 60 characters in the slug itself, including hyphens. Dates are the most common regret: /blog/2024/url-slug-basics locks the content to one year and forces a redirect when the guide is updated in 2026. If the date is part of the archive structure, keep it in the folder path, never in the slug.
- Remove stop words unless the slug becomes ambiguous.
- Keep slugs under 60 characters; very short slugs can be too vague.
- Put dates in folder paths, not slugs, if you need them at all.
- Avoid promotional seasons, version numbers and temporary qualifiers.
- Read the slug aloud: if it sounds like a file name from 2003, rewrite it.
The real cost of changing a slug#
Changing a slug after a page is indexed is not a typo fix; it is a migration. You must return a 301 redirect from the old URL to the new one, update every internal link, and wait for search engines to re-process the signal. During that window, rankings can slip, referral traffic can drop, and any bookmarks or backlinks that miss the redirect become 404 errors. The work is straightforward on a small site and expensive on a large one: a redirect audit from an SEO consultant typically runs €400–€1,200 depending on site size, while a developer implementing the redirects may charge €150–€600 depending on the CMS and the number of rules.
| Redirect type | Effect on SEO | When to use it |
|---|---|---|
| 301 permanent | Passes most link equity; preferred for slug changes | The page has moved permanently |
| 302 temporary | Does not pass full equity; confuses long-term indexing | A temporary test or maintenance page |
| Meta refresh / JS redirect | Unreliable; search engines may ignore | Avoid for structural changes |
| No redirect | Old URL becomes 404; equity is lost | Only if the page never had traffic or links |
A five-year checklist for a durable slug#
Before you publish, imagine someone reading the URL in five years. Will the topic still be accurate? Will the year in the slug feel stale? Will the file still exist if the author leaves? A durable slug is descriptive, language-appropriate, and free of anything that ties it to a campaign or a quarter. It should be easy to type from memory and safe to paste into an email without breaking. The best slugs look obvious in retrospect and survive redesigns because they name the thing, not the moment.
- Use the core noun or phrase the page is actually about.
- Strip years, seasons, version numbers and campaign slogans.
- Transliterate or drop accents based on your primary audience.
- Keep it under 60 characters and remove stop words where meaning stays clear.
- Check that the slug is unique across your site and does not clash with a folder name.
- Confirm you can live with it for five years before you click publish.
When a free online tool is the right choice (and when it is not)#
Browser-based slug generators are useful for the first pass: paste a title, get a hyphenated string, copy it into your CMS. The five tools we publish on siteb.biz run entirely in your browser, so nothing leaves your machine, and the independent mini projects we list each sit on their own subdomain with their own privacy policies. Still, a slug generator cannot know your content strategy, your existing URL patterns or your redirect history. For a one-off blog post, a free online tool is enough. For a site migration, a rebrand or a multilingual setup, hire a developer or an SEO professional; the cost of getting it wrong is usually higher than the cost of the advice.
Always read the privacy policy of any slug generator that asks you to sign in or that processes text on a server; if it is not clear, do not use it.
What to do when you must change a slug#
If a slug is genuinely wrong—misleading, offensive, or blocking a restructure—change it, but change it once. Map the old URL to the new one with a 301 redirect at the server level, not a plugin-only redirect that can be disabled by accident. Update every internal link, including navigation, footer links and image srcset references if they contain the URL. Submit the changed URL through your search console and monitor 404 logs for at least 30 days. Keep the redirect live indefinitely; removing it after a year is the most common way to recreate the original problem.
- Audit existing internal links and backlinks before you change the slug.
- Set a server-level 301 redirect from the old URL to the new one.
- Update internal links so they point directly to the new URL instead of relying on the redirect.
- Submit the new URL to search engines and request re-indexing.
- Monitor 404 logs and backlink reports for at least 30 days.
- Keep the redirect in place permanently; do not treat it as temporary cleanup.
Frequently asked questions
Should I include keywords in my URL slug for SEO?
Including a relevant word or phrase can help a little, because search engines still use the URL as a signal and because users scan addresses before they click. The benefit is modest, however, and it is easily outweighed by keyword stuffing or by a slug that becomes awkward when the topic shifts. A slug such as /url-slug-basics is clearer and more durable than /seo-url-slug-best-practices-guide-2024. Write the slug for humans first, make sure it describes the page accurately, and let the title, headings and body copy carry the heavier SEO load. A readable slug also earns more trustworthy clicks over time.
Can I use capital letters or underscores in a slug?
Technically yes, but practically no. Most web servers treat URLs as case-sensitive, so /URL-Slug-Basics and /url-slug-basics can be two different pages, which creates duplicate-content risk and broken links when someone types the address by hand. Underscores are even worse: some social platforms and email clients do not underline or wrap them cleanly, and search engines have long treated hyphens as word separators while treating underscores as part of a word. Use lowercase letters and hyphens only. The result is easier to read, harder to break and more consistent across phones, desktops and printed materials.
How do I fix a slug that is already indexed by Google?
First, decide whether the problem is serious enough to justify a migration. A slightly awkward slug that ranks well is usually better left alone. If the slug is misleading, offensive or structurally wrong, change it once and set a 301 redirect from the old URL to the new one. Update every internal link, request re-indexing through your search console, and monitor 404 reports for at least 30 days. Expect a temporary dip in rankings while search engines reassign signals. Keep the redirect active forever; removing it is the easiest way to resurrect the original error.
what is a URL slughow to write URL slugsURL slug best practicesURL slug generatorshould I change URL slugtransliterate accents in URL