Skip to content
URL slug best practices for content teams

Guides

URL slug best practices for content teams

How to structure readable URLs, when to change one, and what to do about the redirects nobody remembers to add.

By Remi Okafor, Editor, Toolspea · Published 2026-06-20 · Updated 2026-08-05 · 5 min read

What a slug is for

The slug is the human-readable part of a URL. It is visible in search results, in shared links, and in citations. A URL that describes the page earns trust before the page loads; a URL ending in ?p=4821 tells the reader nothing.

Formatting rules that matter

Most slug problems come from four habits:

  • Use hyphens, not underscores — search engines treat hyphens as word separators.
  • Lowercase everything; some servers treat cases as different URLs, creating duplicates.
  • Fold accents to ASCII so the URL survives copying between systems.
  • Keep it to three to six words. Long slugs get truncated in results and are awkward to share.

Do not put dates in the slug

A dated slug tells the reader the piece is old even after you have updated it, and it prevents the URL being reused when the content is refreshed. Publish the date as visible metadata instead, where it can change honestly when the article does.

Changing a published slug

Treat a live URL as a commitment. When you must change it — a rebrand, a genuinely wrong slug, a restructure — create the 301 redirect in the same change, not later. Then update internal links to point at the new URL directly, so readers and crawlers do not travel through a redirect on every visit.

Frequently asked questions

Tools mentioned

  • URL Slug GeneratorTurn any headline into a clean, lowercase, hyphenated URL slug.
  • Case ConverterSwitch text between sentence, title, upper, lower, camel and snake case.
  • Meta Tag GeneratorProduce title, description, Open Graph and Twitter tags for any page.

Keep reading

Everything referenced in this article, plus the hubs and guides that go with it.