Should You Remove Stop Words from URL Slugs?

· 2 min read

Stop words are the connective tissue of language — a, an, the, and, or, of, in, on, to, for — words so common that early search engines simply ignored them to save index space. That history spawned an SEO tradition: strip them from URL slugs. Mostly, the tradition holds up. Sometimes it produces gibberish. Here's how to tell which is which.

The case for removing them

Take a title like "The History of the Internet in the 20th Century". Slugified verbatim:

the-history-of-the-internet-in-the-20th-century   (47 chars)

With stop words removed:

history-internet-20th-century                     (29 chars)

The second slug is 38% shorter, survives search-result truncation with room to spare, and lost nothing a reader needs — the remaining words carry all the meaning. Search engines put little weight on stop words in URLs, so the removal costs no relevance. For most titles most of the time, removal is a free win: shorter links, denser keywords, no downside.

The three cases where it backfires

1. When the stop word carries the meaning. Some phrases are made of stop words. "How to Tie a Tie" without stop words becomes tie-tie. "To Be or Not to Be" becomes be-be... or nothing at all. Titles built on questions and idioms — how to, what is, why we — often need their small words. what-is-a-url-slug is a better slug than url-slug for a definitional article, because it matches the question people actually type.

2. When removal changes the meaning. "Working with Designers" and "Working for Designers" are different articles; strip the preposition and both become working-designers. Negations are the sharpest edge: "Why You Shouldn't Use jQuery" must keep its negation or the slug says the opposite of the article. (Contractions like shouldn't aren't classic stop words, but aggressive stop-lists sometimes catch not — check yours.)

3. When the result stops reading like language. A slug is for humans first. guide-brewing-coffee-home has all the keywords and none of the fluency of brewing-coffee-at-home. If reading the slug aloud sounds like a robot with a head injury, put a word or two back.

A rule you can automate

The practical policy:

  1. Slugify with stop-word removal on by default — it's right more often than not.
  2. Read the result. If it still makes sense aloud, ship it.
  3. If it doesn't — question-style titles, negations, idioms — turn removal off, or manually restore the one word that matters.

This is exactly why stop-word removal is a toggle, not a default, in the slug generator: flip it on and off with your title in place and compare what comes out. Whichever version a stranger could read and predict the article from — that's the slug. And whichever you pick, never revisit the decision after publishing; a slightly wordy slug is permanent-grade, a renamed one costs a redirect.

One more nuance for multilingual sites: stop-word lists are language-specific. An English list does nothing for le, la, der, die, el — if you publish in several languages, slugify with the right list per language, or skip removal entirely rather than half-apply it.