A URL slug is the human-readable part of a web address that names a specific page — the text after the last slash, like /glossary/slug where slug is the slug. A good slug tells a person and a search engine what the page is about before they click, and a clean URL pattern keeps your site easy to crawl, link, and manage. Slugs are not a heavy ranking lever, but they are cheap to get right and expensive to break, so they earn a place in every page’s setup.
URL Slug
A URL slug is the readable, hyphenated portion of a URL that identifies a single page or resource, usually appearing after the domain and any folders (for example, /blog/url-slug where url-slug is the slug).
What a URL slug actually is
Break a URL into parts and the slug is easy to spot:
https://www.seosavages.com/glossary/url-slug
└─ scheme ─┘ └──── host ────┘ └ path ┘└ slug ┘
The path is the folder structure (/glossary/), and the slug is the final segment that names the page (url-slug). On WordPress and most CMSes the slug is editable separately from the title, which is why a page titled “What Is a URL Slug? 9 Best Practices” can — and should — live at /url-slug rather than /what-is-a-url-slug-9-best-practices-for-seo. If you want the broader picture of how the whole address is constructed, see what is a permalink.
We treat slugs as a hygiene layer, not a growth lever. They will not rank a page on their own, but a messy slug system quietly taxes everything downstream: internal linking, analytics, redirects, and how your URLs read inside an AI Overview citation or a shared link.
Why slugs still matter (in 2026)
Google has said for years that words in the URL are a “very small” ranking factor, and that hasn’t changed. So why bother? Because the slug does several jobs at once that compound across a site.
- Topic clarity. A descriptive slug confirms what the page covers. It reinforces the signals already in your H1 tag and primary keywords rather than carrying the load alone.
- Click-through. The slug is part of what shows in the SERP and in shared links. A clean
/voice-search-seoreads as trustworthy; a/p?id=88421&ref=fbreads as spam. That nudges organic CTR. - AI Overview and citation context. When an LLM-backed answer cites your page, the URL is visible. A readable slug makes the citation legible to the human reading the AI summary — useful in a results page that increasingly shows fewer blue links.
- Crawl and structure. Consistent slugs map cleanly onto your SEO site structure and website taxonomy, making it easier for crawlers and for you to manage internal links.
- Stability. A unique, stable slug is a durable address. Change it carelessly and you snap inbound links and lose rankings until redirects catch up.
The slug rarely wins a ranking. But a bad slug strategy — auto-generated IDs, dates baked in, slugs that change on every edit — leaks equity for years. The return on getting slugs right is mostly downside avoided.
How to write SEO-friendly slugs
Here’s the practitioner checklist we apply on every page. None of these are exotic; the discipline is in doing all of them, every time.
- Lead with the keyword or intent. Put the term users actually search at or near the front:
/url-slug, not/the-complete-guide-to-slugs. - Keep it short — 3 to 5 words. Shorter slugs read better, share better, and break less. Trim everything that isn’t load-bearing.
- Use hyphens, not underscores or spaces. Google reads
url-slugas two words andurl_slugas one token. Spaces become ugly%20escapes. - Lowercase only. Some servers treat
/Slugand/slugas different URLs, which invites duplicate content. Force lowercase. - Drop stop words that add nothing.
how-to-write-a-slug→how-to-write-slugis fine; don’t strip words when removing them changes meaning. - Avoid dates and volatile data. A slug like
/2024-seo-trendsages instantly and tempts a risky rename later. Keep the slug evergreen; put the year in the content. - Skip parameters and session IDs in indexable URLs. Clean static slugs beat
?utm-laden query strings for sharing and indexing. See how to optimize URLs for search. - Make every slug unique. Duplicate slugs force the CMS to append
-2, which is a smell. Two pages with near-identical slugs usually means you have a content overlap to resolve. - Mirror hierarchy when it helps.
/services/local-seois clearer than a flat/local-seoif the folder carries meaning — but don’t nest for nesting’s sake.
Good slugs vs. bad slugs
The difference is obvious once you see them side by side.
| Page | Bad slug | Better slug | Why |
|---|---|---|---|
| Guide to URL slugs | /p?post=2291 | /url-slug | Readable, keyword-first, no parameter |
| Local SEO service | /Services/Local_SEO_Page | /services/local-seo | Lowercase, hyphens, clean folder |
| Blog post | /10-amazing-tips-you-wont-believe-about-slugs | /url-slug-tips | Concise, no clickbait padding |
| Product | /product/cat/87/sku/9921 | /running-shoes-trail | Names the thing, not the database row |
| Dated article | /2023/best-tools | /best-seo-tools | Evergreen, survives the next year |
If you inherit a site full of the left column, you don’t have to fix it all at once. Prioritize your highest-traffic and highest-converting pages, and leave clean, irrelevant slugs alone — changing a slug is never free.
Changing a slug without losing rankings
This is where teams get hurt. A slug is a URL, and changing a URL means the old address now points at nothing. Do it wrong and you ship a wall of 404 errors and watch rankings dip.
The safe sequence:
- Decide the change is worth it. Cosmetic slug edits on a ranking page rarely pay off — only rename when the slug is genuinely misleading or broken.
- Publish the page at the new slug.
- Add a 301 redirect from the old slug to the new one so link equity and bookmarks survive.
- Update internal links to point at the new slug directly — don’t rely on the redirect for your own navigation.
- Watch for redirect chains. Each rename that stacks another hop slows crawling and bleeds a little equity; consolidate so every old URL points straight to the final one.
For multilingual sites, give each language its own translated slug and pair it with hreflang plus a canonical so the variants don’t read as duplicates.
Frequently Asked Questions
What is a URL slug?
A URL slug is the readable portion of a web address that identifies a specific page, appearing as the last segment of the path — for example, the url-slug in /glossary/url-slug. Slugs are lowercase, hyphen-separated, and short, so both people and search engines can tell what the page covers before clicking.
Do URL slugs affect SEO rankings?
Slightly. Google treats keywords in the URL as a very small ranking factor, so a descriptive slug reinforces relevance but won’t rank a page by itself. The bigger payoff is indirect: cleaner click-through, easier crawling, stable internal links, and legible citations in AI Overviews and shared links.
How long should a URL slug be?
Aim for three to five words, roughly under 60 characters. Short slugs read better in search results, survive copy-paste sharing, and are less likely to break. Include the primary keyword near the front and cut stop words and filler that don’t change the meaning of the URL.
Should I use hyphens or underscores in a slug?
Use hyphens. Google reads url-slug as two separate words but treats url_slug as a single token, which can hurt how the page is interpreted. Hyphens are the long-standing standard for word separation in URLs; reserve underscores for code, not for slugs.
Can I change a URL slug after publishing?
Yes, but carefully. Publish the new slug, add a 301 redirect from the old one to preserve link equity, then update your internal links to point directly at the new URL. Only rename slugs that are genuinely misleading — cosmetic changes on a ranking page usually cost more than they earn.
Slugs are a small fix that compounds across an entire site. If you’re cleaning up URL structure at scale — across hundreds of programmatic pages or a tangled CMS — our core programmatic SEO and AI SEO services work bakes clean, stable slug patterns into the build so you’re not retrofitting redirects later.