What Is a Slug in SEO? The URL Decision You Only Get to Make Once
A slug is the part of a URL that names one page. It barely moves rankings on its own, but it is the hardest thing on the page to change later. Here is how to set one.
A slug is the segment of a URL that identifies one specific page, the part after the last slash. In https://crawlraven.com/blog/what-is-a-slug-in-seo the slug is what-is-a-slug-in-seo. Four things are worth knowing before you set one:
- IT IS A VERY SMALL DIRECT RANKING FACTOR: Google's own URL guidance is about readability and crawlability, not keyword placement. Nobody has ever outranked a better page by writing a better slug.
- IT IS THE MOST EXPENSIVE THING ON THE PAGE TO CHANGE: You can rewrite a title tag at 4pm and be done. Renaming a live URL means a permanent redirect, updated internal links, and a chunk of history in transit for weeks.
- THE RULES ARE SHORT: Lowercase, hyphens between words, three to six words, no dates, no stop words on long titles, no repeating the directory you already sit in. That is close to all of it.
- THE HARD PART IS THE PATTERN, NOT THE PAGE: Decide the shape per page type before you publish the first one. Retrofitting a URL pattern across 400 published pages is a migration, and migrations lose traffic.
Treat the slug as a permanence decision rather than an optimisation. Get it readable and stable at draft time, then never touch it again.
Every slug guide says to put the keyword in it, then stops. That advice is fine and beside the point. Words in a URL move rankings very little. What makes the slug worth thinking about is that it is the one element you cannot quietly fix later. Try CrawlRaven free: 1 site, no credit card →
What is a slug in SEO?
A slug is the part of a URL that identifies one specific page: the segment after the last slash. In https://crawlraven.com/blog/what-is-a-slug-in-seo, the slug is what-is-a-slug-in-seo.
It is the only part of the address written fresh for every page. The protocol, the domain, and the directory are all decisions you made once. The slug is the per-page one, which is why it is the only piece a reader ever really reads.
Which part is the slug
The name comes from newsroom jargon, not from software. A slug was the short working label an editor gave a story so everyone could refer to it before it had a headline. A URL slug does the same job for a page.
Two adjacent terms get used interchangeably and should not be. Worth separating before the rest of this makes sense:
- Slug is the final segment that names the page:
/what-is-a-slug-in-seo. - Permalink is the whole permanent address, slug included. WordPress uses this word for the setting that decides the shape of every URL on the site.
- URL structure is the pattern across the site: which directories exist, how deep pages nest, and what each level means.
Does the slug actually affect rankings?
Barely, and it is worth being honest about that up front. Google's own URL structure documentation is written almost entirely about readability and crawlability. It asks for words a human can read instead of opaque IDs, and hyphens instead of underscores. It does not ask you to place a keyword.
The indirect effects are the ones that actually matter, and they are real:
- Click-through. Google usually shows a breadcrumb trail rather than the raw URL now, but a readable path still tells someone what they are about to open. An opaque
/p?id=88213tells them nothing. - Anchor text you did not write. When someone pastes a bare URL into a forum or a Slack channel, the slug is the anchor text. That is a free descriptive link or a wasted one.
- Duplicate prevention. Consistent casing and a single canonical path stop the same page existing at two addresses, which is where slug decisions quietly turn into a duplicate content problem.
- Your own sanity. A crawl of 4,000 readable URLs can be skimmed. A crawl of 4,000 numeric ones has to be joined to a database before it means anything.
Keyword-in-URL advice survived because it was easy to check and easy to sell. It became a line item in every audit template, mine included, long after it stopped being worth arguing about.
The thing that genuinely costs money is renaming a URL that already ranks. In fifteen years I have seen far more traffic lost to a well-meaning slug cleanup than gained by a keyword-perfect one.
SEO slug best practices
The whole rule set fits on one screen. Everything below is either about readability or about not creating two addresses for one page.
Hyphens, lowercase, and length
- Hyphens between words, never underscores. Google treats a hyphen as a word separator and an underscore as a joiner, so
slug_seo_guidecan be read as one token whereslug-seo-guidereads as three words. - Lowercase everywhere. Paths are case-sensitive on most servers, so
/Slug-SEOand/slug-seocan serve the same page at two addresses and split its signals. - Three to six words, under about 60 characters. Length is not a penalty. It is a readability ceiling, and a long slug is usually a copied title tag rather than a considered one.
- No spaces, ever. A space becomes
%20the moment the URL leaves the browser bar, which is ugly in exactly the place you wanted readable. - Do not repeat the directory.
/blog/blog-seo-slug-guidesays blog twice. The folder already carries that.
Stop words, dates, and numbers
Stop words are the small function words: a, the, of, to, for. Dropping them from a long title usually removes about a third of the characters and none of the meaning. Keep them when the slug stops making sense without them, because /what-slug-seo is shorter and worse than /what-is-a-slug-in-seo.
Dates and numbers each have one clear rule:
- Keep years out of evergreen paths. A slug containing 2026 forces an annual choice between a redirect you did not need and a URL that contradicts the page. Put the year in the title tag instead, where editing it is free.
- Years are fine on genuinely dated pages. A core update post or an annual report is about a moment in time, so the date is description rather than decoration.
- Counts belong in the title, not the path.
/seo-audit-checklistsurvives growing from 40 checks to 87./40-point-seo-audit-checklistdoes not.
Accents and other alphabets
Non-ASCII characters are legal in a URL and get percent-encoded whenever the address is shared, logged, or pasted. An accented e becomes %C3%A9, which defeats the point of a readable path.
- Transliterate to ASCII by default for Latin-script languages, following the local convention: German normally maps
ätoaerather than toa. - Non-Latin scripts are a judgement call. A native-script slug reads correctly for the audience and encodes badly everywhere else. Whichever you pick, apply it across the whole language folder rather than post by post.
Setting slugs for a batch of planned pages rather than one? Our free URL slug generator takes a list of titles and returns clean paths. The duplicate check runs across the whole list, which is the one worth having: two pages cannot share a URL, and you only see the collision when you see the list together.
Pick the pattern before you pick the page
This is the part that matters more than any individual slug. The shape of a URL is a decision per page type, made once, before the first page of that type ships.
Get it wrong and the fix is not an edit. It is a migration across every page in that section, with a redirect map, and migrations lose traffic even when they go well.
Slug patterns by page type, and the trap in each
One rule underlies all six rows. Keep the directory stable and the slug specific, so that a page can be recategorised without its address changing. Nesting a product under its category is the classic version of this mistake: /shoes/mens/running/wool-runner looks tidy right up to the day the item also belongs in trail.
Changing a slug on a live page
Here is the asymmetry that makes slugs worth this much attention. A title tag is a five-second edit with no downside. A URL is a public identifier that other people have linked to, bookmarked, and cited.
What each option actually costs you
- •The old URL returns 404 and drops out of the index
- •Every external link to it stops passing anything
- •Internal links, sitemaps and canonicals still point at the dead path
- •Search Console reports the old URL as Not found, and the history goes with it
- •Signals carry across, though reprocessing takes weeks rather than hours
- •You now maintain a redirect forever, and a second rename creates a chain
- •Internal links still need updating so readers do not take the extra hop
- •Anything hard-coded outside the CMS, such as email templates, has to be found
- •No redirect to maintain and no chain to untangle later
- •No lost link history, because nothing moved
- •The only cost is thinking about the slug before you hit publish
The 301 redirect does its job, but it is not free. Three costs are easy to underestimate:
- Reprocessing takes weeks. Google has to recrawl the old URL to discover the redirect, and that is on its schedule rather than yours.
- Redirects accumulate. Rename twice and you have a redirect chain, which is slower for readers and messier for crawlers than either hop alone.
- Internal links do not update themselves. Every mention in your own content keeps pointing at the old path, so readers take a pointless extra hop and your internal linking quietly routes through a redirect.
So the honest test is narrow. Change a live slug when:
- It is factually wrong, such as a typo or a renamed product.
- It contains a year on a page you intend to keep updating, and you are fixing that once and permanently.
- It is part of a site migration you were doing anyway, so the redirect cost is already being paid.
Wanting a better keyword in it is not on that list. If you do go ahead, redirect the old path, update every internal link to point at the new one directly, resubmit the sitemap, and check afterwards that no chain formed. Our SEO migration checklist covers the full sequence when the change is bigger than one page.
Slug SEO in WordPress and Yoast
WordPress uses the word slug for the editable URL segment and exposes it in the post editor sidebar, or inside the Yoast SEO snippet preview if you have that installed. Both edit the same field. Yoast does not manage URLs separately from WordPress.
Four WordPress-specific things cause most of the trouble I see:
- The Permalinks setting is site-wide and structural. Settings then Permalinks. The default Day and name option bakes dates into every post URL. Post name is the option you want, and it is far cheaper to change on day one than at post 300.
- The slug is generated from the title on first save. Publish with a working headline and you inherit that headline as your permanent URL. Set the slug deliberately before you publish.
- A trailing -2 means a collision. WordPress appends it when the slug is already claimed by another post, a page, a category, or a media attachment. Chase it rather than accepting it, because the holder is usually an old draft or an image.
- Category and tag bases count as URLs too. They live in the same Permalinks screen and produce real indexable paths, which is where thin archive pages come from.
One thing Yoast genuinely helps with: its snippet preview shows the slug next to the title tag, which makes it obvious when you have simply copied one into the other. Those two fields have different jobs and should rarely match.
The slug mistakes that show up in crawls
Slug problems almost never arrive as a slug problem. They surface as duplicate content, a redirect chain, or a page that will not consolidate. These are the patterns worth grepping your own URL list for:
- Mixed casing on the same path. Two live addresses, one page, signals split between them. Fix with a lowercase redirect rule and a canonical tag.
- Trailing slash inconsistency.
/slug-seoand/slug-seo/are different URLs. Pick one convention, redirect the other, and be consistent in your internal links. - Session IDs and tracking parameters in the path. These multiply a single page into hundreds of crawlable variants and eat crawl budget for nothing.
- Redirect chains from repeated renaming. Three hops from a URL that was tidied twice, each hop slower than the last.
- Stale years across a content library. Forty posts with 2024 in the path, all updated, none redirected.
- Orphaned old paths still linked internally. The redirect works, so nothing looks broken, and every reader takes the extra hop anyway.
The reason these persist is that none of them breaks anything visibly. Finding them means crawling the site, then asking which of the findings has real traffic behind it.
That join is what CrawlRaven does: Search Console and GA4 data against a 200-point crawl, returned as a ranked list rather than an export. Lifetime licenses start at $49 at launch, with a free plan for one site. See pricing for the current batch.
If you want the wider on-page context, the on-site SEO checklist covers where URLs sit among the rest of the on-page signals, and the new website SEO checklist is the right place to start if you are still choosing a URL structure rather than repairing one.
Frequently asked questions
What is a slug in SEO?
A slug is the part of a URL that identifies one specific page, the segment that comes after the last slash. In https://example.com/blog/technical-seo-audit the slug is technical-seo-audit. It is the only part of a URL written fresh for each page, and the only part a reader is likely to actually read before clicking.
Does the slug affect SEO rankings?
Only slightly and mostly indirectly. Google's published URL guidance is about making URLs readable and crawlable rather than about keyword placement, and words in a URL have long been described as a very small ranking factor. The real benefit is that a descriptive path tells a person what they are about to open, which affects whether they click.
How long should an SEO slug be?
Three to six words and under roughly 60 characters. There is no length penalty, but long paths get truncated in the results trail, are harder to paste into a message, and usually mean you copied the title tag instead of trimming it to the topic.
Should a slug use hyphens or underscores?
Hyphens. Google's URL structure documentation recommends hyphens to separate words, because underscores join words into a single string. So seo_slug_guide can be read as one token while seo-slug-guide reads as three words. Every major CMS defaults to hyphens for the same reason.
Should the slug match the page title exactly?
No, and it usually should not. Titles carry a hook, a year, a brand suffix, or a number to earn the click in a search result. The slug wants the topic in as few words as possible. Trimming a title of 62 characters down to a four-word slug is normal rather than a mismatch.
Can I change a slug after publishing?
You can, but the old URL holds the page's accumulated links and ranking history, so a permanent 301 redirect from old to new is mandatory rather than optional. Even with the redirect in place, expect weeks of reprocessing. Change a live slug only when the current one is actively wrong, not because you thought of a better phrasing.
Should I put the year in a slug?
Not on anything you plan to update. A slug containing 2026 forces a choice every January between a redirect you did not need and a URL that contradicts the refreshed page. Put the year in the title tag, where it costs nothing to edit, and leave it out of the path.
Should slugs be lowercase?
Yes. URL paths are case-sensitive on most web servers, so /Slug-SEO and /slug-seo can serve identical content at two addresses. That splits signals and creates duplicate content for no benefit. Lowercase everywhere removes the question, and a lowercase redirect rule catches anything already published.
What is a slug in WordPress?
WordPress calls the editable URL segment the slug and exposes it in the sidebar of the post editor, or in the Yoast SEO snippet preview if you use that plugin. It is generated from the post title on first save, so the safest habit is to set it deliberately before publishing rather than after.
Why did WordPress add a number to the end of my slug?
WordPress appends -2 when the slug you asked for is already taken by another post, page, attachment, or category. A slug ending in -2 is a signal worth chasing: it usually means a draft, a media attachment, or an old revision is holding the URL you actually want.
Do stop words hurt an SEO slug?
They do not hurt rankings, they just spend characters. Dropping a, the, of, and to from a long title typically removes about a third of the length and none of the meaning. Keep them when the slug reads as nonsense without them, because an unreadable slug has given up its only real advantage.
What happens to accented characters in a slug?
They are legal but get percent-encoded when the URL is shared or logged, so cafe with an accent becomes caf%C3%A9 in most contexts. That is unreadable in exactly the place a slug is supposed to be readable. Transliterate to the closest ASCII equivalent instead, using the local convention where one exists.
15+ years of growing SaaS websites through SEO | Author, 200-Point Audit Checklist
Aditi has spent 15+ years helping SaaS companies scale organic traffic through technical SEO and content strategy. She is the author of the CrawlRaven 200-Point Audit checklist used by agencies and in-house teams to systematically improve search performance.