Permalinks

Two labeled URL displays side by side: on the left, a URL ending in a long opaque session ID, marked "Breaks once the session ends"; on the right, a short, readable URL built from a date and topic, marked "Still works a year later" A session-scoped URL breaks the moment the session ends; a permalink built from what’s actually permanent about the page keeps working a year later.

Background

Short, generic URLs are easier to remember and type but only work for pages meant to change; long, specific URLs preserve exact content indefinitely but are harder to share by hand. Most sites need both — generic permalinks for a small set of always-current pages, content-specific permalinks for everything meant to be revisited exactly as first seen.

Short, generic URLs are easier to remember and type but only work for pages meant to change; long, specific URLs preserve exact content indefinitely but are harder to share by hand.

Problem

Customers bookmark or share a page’s URL expecting to be able to return to the same content later — a day, a week, or a year afterward — but if the URL later shows different content, or leads to a Page Not Found error, that expectation is broken and the customer’s trip back is wasted.

Customers bookmark or share a page’s URL expecting to be able to return to the same content later — a day, a week, or a year afterward — but if the URL later shows different content, or leads to a Page Not Found error, that expectation is broken and the customer’s trip back is wasted.

Solution

Design URLs deliberately around what should and shouldn’t change over time.

Choose the right URL type for the content

Reserve short, memorable, generic URLs for pages that are supposed to update — a homepage or a category page that shows today’s top stories today and different stories tomorrow. Any page whose content should stay fixed once published — an individual article, a specific product — needs its own non-generic permalink, distinct from the generic page it may currently be featured on. Conflating the two is the most common permalink mistake: a customer who bookmarks a “Top Stories” URL expecting to revisit today’s top stories will instead see whatever is current when they return.

Conflating the two is the most common permalink mistake: a customer who bookmarks a “Top Stories” URL expecting to revisit today’s top stories will instead see whatever is current when they return.

Use temporary URLs for sensitive content

Some pages should deliberately not have a durable URL. Banking sites and other applications handling sensitive session data commonly generate temporary, session-scoped URLs so that a browser can’t cache or later re-access confidential information — a bookmark to one of these pages should simply fail once the session ends, redirecting instead to a stable, non-sensitive page like the homepage or sign-in page.

Design a durable naming convention

Identify what’s actually immutable about the page — a publication date, a fixed topic, a specific product — and build the URL pattern around those elements rather than anything that might change (an editorial category the content could later be reclassified under, for instance).
Include meaningful text in the URL, not just an opaque ID — a URL a customer can partially read (/2006/02/mayan-calendars) lets them guess the page’s subject before clicking, the same benefit descriptive link text provides.
Keep URLs short and readable. Short URLs are easier to remember, more likely to survive being manually retyped, and less likely to break when word-wrapped across lines in an email client that doesn’t handle long URLs gracefully — a common, avoidable cause of a customer hitting Page Not Found. Avoid spaces and punctuation that get encoded into unreadable escape sequences. See Search Engine Optimization for how the same short, hyphenated, human-readable URL convention also helps search ranking and click-through.
Apply the convention consistently, site-wide, so both visitors and whoever maintains the site can predict a URL’s shape without checking.
Plan a directory structure, not a flat list — permalinks with a natural grouping element (a date, a category) usually translate directly into a directory structure, which keeps a large site’s URLs organized and avoids the server-performance problems of dumping every page into one directory.

Allow dynamic content on a permanent page

A permalink doesn’t require every element on the page to be frozen — the parts that should remain identical when a customer returns (the article text, the product description) can be built with a page template and content modules that still update the parts that legitimately should change over time (ads, navigation, related-content modules) around that fixed core.

Patterns

Sources

The Design of Sites: Pattern Group K — Making Navigation Easy is this page’s source — Pattern K15, covering the generic-vs-content-specific URL distinction, temporary session-scoped URLs for sensitive content, and the durable-naming-convention rules (anchoring the URL to what’s actually immutable, meaningful text, short and readable, applied consistently, planned as a directory structure).