Permalink
Definition
A permalink is a URL chosen on the understanding that it will keep resolving to the same resource indefinitely. Blogs popularised the word for the canonical address of a single post, as distinct from a front page or a category listing whose contents shift as new posts arrive. Nothing in HTTP enforces permanence; a permalink is simply an address its owner has decided not to move. In practice that means a short, descriptive path with no query string that carries state and nothing in it that will date, and it means replacing the content behind the address rather than publishing a second address alongside. Where a resource genuinely has to move, a 301 redirect keeps the promise intact.
Why It Matters
Everything downstream of an address depends on that address holding. Printed QR codes, slide decks, email archives, bookmarks, citations, search rankings and other people's links all break together the day a permalink moves. Nothing appears in your logs when it happens — the failure is entirely on somebody else's screen. The discipline costs nothing at the moment of publishing and is close to impossible to retrofit, which is why the time to choose a good address is before you give it to anyone.
How It Works
A permalink is assembled from parts that will not change: a domain you control, a path describing the thing rather than its position or its version, and no query string that carries state. The host maps that path to a file, so updating the file leaves the mapping untouched and the address serves new bytes without moving. If the resource does have to relocate, a 301 response with a Location header tells browsers and crawlers to follow, and search engines pass the accumulated ranking across. A canonical URL tag in the page markup declares which address is the real one when several point at the same content. Version history at the host is the safety net: you can change what a permalink serves and still go back.
Real-World Example
A software team publishes its changelog as one page at ridgeway-changelog.99helpers.site and puts that address in the app's help menu, in every release email and in the README. Each release replaces the file; the address never moves. Two years and forty releases later, the link in the very first email still opens the current changelog. A bad upload is undone with a rollback rather than a rebuild.
Common Mistakes
- ✕Encoding the year or a version number into the path — the address dates itself and you end up minting a new one every cycle
- ✕Treating a preview or staging address as permanent — those are built to be thrown away, and usually are
- ✕Moving content and deleting the old path — without a redirect, every existing link fails and the search ranking is lost rather than transferred
Related Terms
Link Rot
Link rot is the slow decay of working links into dead ones as pages move, domains lapse and services shut down. A large share of links published a decade ago no longer resolve.
URL Anatomy
URL anatomy is the set of parts a web address is built from: scheme, host, path, query string and fragment. Knowing which part is which explains most link problems in seconds.
301 Redirect
A 301 redirect is a response telling the browser that a page has moved permanently and giving the new address. The old URL keeps working for anyone who follows the old link, but everything that matters now lives at the new one.
Canonical URL
A canonical URL is the one address you nominate as the real home of a piece of content when several addresses serve it. You declare it with a rel=canonical link in the page head, and search engines use it to decide which version to index.
URL Slug
The readable, hand-picked part of a web address that names one particular thing — the 'acme-pitch' in acme-pitch.99helpers.site. It is chosen, short and made only of lowercase letters, digits and hyphens.
Put a file online in seconds
Drop in a document, an image, a page or a whole static website and share the link — free, with no build step and no server to set up.
Host a file free →