URL slug
A URL slug is the readable part of a web address that identifies a specific page, typically the segment that comes after the domain name, such as website in bebranded.xyz/services/website. It is what a visitor, and a search engine, reads to understand what a page is about before ever opening it.
What is a URL slug?
A slug is the human-readable identifier assigned to a page, post or CMS item, usually derived from its title. Where a full URL includes the protocol, domain and full path, the slug is just the final, descriptive segment a content editor typically controls directly. In most content management systems, including Webflow, the slug is generated automatically from the item's name when it is created, and can then be edited independently of that name.
A good slug lets someone glance at a URL and understand the page's topic without clicking it, which matters for trust, sharing and search engine understanding alike.
How a slug is structured
A slug is built from lowercase words separated by hyphens, with punctuation, accents and stop words stripped out. A CMS typically slugifies a title automatically:
"SSL Certificate: What It Is" → ssl-certificate-what-it-is → ssl-certificate
The final, edited version usually drops filler words the automatic process keeps, since a shorter slug focused on the core keyword serves both readability and search relevance better than a literal copy of the title.
Types of slugs
- Static slugs: fixed segments for pages that rarely change, such as
/aboutor/pricing. - CMS-generated slugs: dynamic, one per collection item (a blog post, a glossary term), generated from the item's name and editable per locale.
- Nested slugs: reflect a hierarchy, such as
/services/website, where the path itself carries structural meaning. - Parameter-based identifiers (not true slugs): query strings or numeric IDs such as
?id=482, which carry no readable meaning and should be avoided for public pages.
Good slugs vs bad slugs
| Aspect | Good slug | Bad slug |
|---|---|---|
| Length | Short, a few relevant words | Long, includes the whole title |
| Words | Lowercase, hyphen-separated | Mixed case, underscores or spaces |
| Content | Keyword relevant to the page | Random ID or auto-generated string |
| Stop words | Removed (the, a, and) | Kept, adding unnecessary length |
| Example | /services/website | /Page.aspx?id=48291&cat=svc |
Best practices and common pitfalls
Keep a slug short, lowercase and focused on the page's main keyword, dropping stop words like "the" or "and" that add length without adding meaning. The single most costly mistake is changing a slug after a page has been indexed and linked to: every external backlink and every internal link pointing to the old URL breaks unless a 301 redirect is set up, so a slug should be treated as close to permanent once published. Avoid dates in a slug for evergreen content, since /blog/2023-guide looks outdated within a year even if the content is still accurate.
Slugs and SEO impact
A slug containing the target keyword gives search engines an additional, lightweight relevance signal, though it is a minor factor compared to the actual page content. Its bigger impact is indirect: a clear, readable slug improves click-through rate in search results because it signals relevance before the title even loads, and it makes a link worth sharing or citing look trustworthy rather than like a database export.
URL slugs at BeBranded
We define slug conventions as part of the information architecture of every website we build in Webflow, so URLs stay short, consistent across the site and safe to keep unchanged for years without a redirect plan.