←  All terms
S
CMS & Content

Slug

A slug is the readable, unique part of a URL that identifies a page or content item.

A slug provides a clear and human-readable identifier for a specific page or content item within a URL. It should be concise, consistent, and stable over time to support usability, maintainability, and search visibility. Changes to existing slugs should be handled carefully to avoid broken links and unnecessary redirects. The concept is closely related to URL Structure and Canonical URL.

Read more

URL Structure

Canonical URL

Redirect

Collection Page

FAQ

Slug

How does a slug differ from the URL structure?
The slug is just the final segment of an address, such as contact in /contact. The URL structure describes the whole system of paths, levels, and folders. In CMS collections, an address often combines a fixed path prefix with the slug of the individual item. Both should be planned together.
Should a slug include the primary keyword?
Yes, as long as it describes the content accurately. A readable slug helps people and search engines classify a page, yet it is only one hint among many. Repeated keywords or very long addresses add nothing. Stability matters more: a good slug still fits the content years later.
What happens when a slug is changed after publication?
Without countermeasures, the old address returns a 404 error, and inbound links and ranking signals are lost. Every change therefore needs a 301 redirect from the old URL to the new one. Internal links and the sitemap must be updated as well. Ideally, a slug stays unchanged for good.
What makes a good slug?
Short, lowercase, separated by hyphens, and free of special characters. It names the topic in a few words, such as headless-cms rather than a full headline. Filler words and dates can go if they add no meaning. Umlauts and accents are usually transliterated so the address works reliably everywhere.