# What Is a Permalink? Full Guide With Examples (2026) > A permalink is the permanent URL for a specific page or post. Learn how permalinks work, best structures, permalink vs slug vs short link, and how to change one without breaking SEO. URL: https://u2l.ai/blog/what-is-a-permalink Published: 2026-08-18T22:21:55+05:30 Updated: 2026-08-18T22:21:55+05:30 Author: Team U2L Category: explainers Tags: permalink, seo, url structure, explainers --- You publish a blog post, share the link on X, and someone bookmarks it. Two years later they click that bookmark. It still works. That's a permalink doing its quiet job in the background - the URL didn't move, and the person who saved it two years ago wasn't punished for trusting it. Now flip the scenario. You publish the post, rank on Google, and six months later you rename the URL because you didn't like how it read. Every backlink pointing at the old address breaks. Your Google ranking drops overnight. Your careful analytics history splits into a "before" and "after" version of the same article. That's a permalink failing at its one job. This guide covers what a permalink actually is, why the word "permanent" matters more than most publishers realise, how permalinks differ from URLs, slugs, and short links (a lot of confusion here), the best permalink structure for SEO in 2026, how to change one without wrecking your traffic, and the practical tricks pros use to make permalinks work harder. If you run a blog, an e-commerce store, or any content site, this is one of the smallest technical decisions that has the biggest long-tail impact. A **permalink** (short for "permanent link") is the stable, unchanging URL that points to a specific page, post, or piece of content on a website. Once a permalink is published, it should stay the same forever so that bookmarks, backlinks, search-engine rankings, and shared links keep working. A typical permalink looks like `https://example.com/blog/what-is-a-permalink` - a protocol, a domain, and a slug that identifies the specific piece of content. A **permalink** is a permanent URL that points to a specific web page, blog post, or piece of content. It is designed to stay the same over time so that links to that content continue to work even after the content is edited, republished, or moved between categories. ## Table of Contents - [What a Permalink Actually Is](#what-a-permalink-actually-is) - [Why the Word "Permanent" Matters](#why-the-word-permanent-matters) - [Anatomy of a Permalink](#anatomy-of-a-permalink) - [Permalink vs URL vs Slug vs Short Link](#permalink-vs-url-vs-slug-vs-short-link) - [Types of Permalink Structures](#types-of-permalink-structures) - [The Best Permalink Structure for SEO in 2026](#the-best-permalink-structure-for-seo-in-2026) - [How Permalinks Work Under the Hood](#how-permalinks-work-under-the-hood) - [How to Change a Permalink Without Killing SEO](#how-to-change-a-permalink-without-killing-seo) - [Common Permalink Mistakes](#common-permalink-mistakes) - [Permalinks and Short Links: How They Work Together](#permalinks-and-short-links-how-they-work-together) - [Frequently Asked Questions](#frequently-asked-questions) ## What a Permalink Actually Is A permalink is the unchanging web address of a specific piece of content. When you publish a blog post at `https://example.com/blog/permalink-guide`, that URL is the permalink. Update the article, change the title, edit the featured image - the permalink stays the same. That stability is the whole point. The word comes from "permanent" plus "link," coined in the early 2000s by blogging pioneers who noticed a problem. Blogs at the time listed posts on the homepage, and when the homepage refreshed, the URL for an individual post kept shifting further back in the archive. Linking to something was pointless if the address changed every week. **Permalinks solved that** by giving every post its own dedicated URL that lived at the same address forever. That original problem is mostly solved on modern platforms - WordPress, Ghost, Squarespace, Shopify, Webflow, and every serious CMS assigns a permalink at publish time and keeps it stable by default. But the underlying idea still shapes how modern web publishing works. Bookmarks, backlinks, RSS feeds, social shares, Google's index, and internal analytics all assume the URL you saw last month is the URL you'll see today. Here's a fun bit of trivia most people don't know: permalinks predate the modern web design pattern of "clean URLs" by several years. Early WordPress installations had permalinks that looked like `example.com/?p=123`. The `123` was the post ID in the database. That was still a permalink - stable and pointing to one specific post - it just looked ugly. The move to human-readable slugs (`example.com/what-is-a-permalink`) came later, and once Google made it clear that descriptive URLs helped rankings, everyone switched. ## Why the Word "Permanent" Matters The "permanent" part isn't a suggestion. It's the entire contract you make with the internet when you publish something. Break it, and you're punishing everyone who trusted your URL. Every time a permalink changes, three things break at once: 1. **Backlinks die.** Anyone who linked to your page from their blog, newsletter, or social post now points at a 404. All the SEO value they were passing dries up. 2. **Bookmarks fail.** Every reader who saved the URL loses their bookmark. Some will hunt for the new page. Most will just leave. 3. **Rankings drop.** Google has to reindex the new URL from scratch. Your carefully-earned position on page one gets reset, and the crawl budget you spent building authority on the old URL is wasted. Google's own documentation on [URL structure best practices](https://developers.google.com/search/docs/crawling-indexing/url-structure) is direct on this: keep URLs stable. Every URL change should be treated as a small emergency and mitigated with 301 redirects. Doing it casually is expensive in ways that don't show up in your dashboard until three months later when your traffic quietly sinks. The counterintuitive part is that permalinks are meant to survive their own content. You can rewrite the article, replace the author, change the publish date, swap the featured image, or even repurpose the page for something new. As long as the URL stays the same, all your accumulated SEO equity stays with it. Big publishers exploit this deliberately - they'll refresh an old article every year while keeping the same URL, because Google treats the URL as the addressable asset, not the version of the content sitting at that URL today. ## Anatomy of a Permalink Look at `https://example.com/blog/what-is-a-permalink` and break it down piece by piece: **Protocol** (`https://`). The transport scheme. In 2026 there is no good reason to serve permalinks over `http://` - HTTPS is table stakes for SEO, security, and every modern browser will warn users about non-HTTPS pages anyway. **Domain** (`example.com`). The host that owns the content. This is the part that stays constant across every permalink on the site. **Subdirectory** (`/blog/`). Optional grouping. Some sites nest posts under `/blog/`, `/articles/`, or `/news/`. Others skip the subdirectory entirely and put every post at the root (`example.com/what-is-a-permalink`). Both are valid. Nesting adds a small amount of context for both users and search engines but also makes URLs longer. **Slug** (`what-is-a-permalink`). The unique identifier for this specific piece of content. Slugs are the part most publishers actually get to control day to day. Get slugs right and your permalinks read cleanly. Get them wrong and you end up with something like `example.com/2024/03/14/post-8471-final-v3-copy`. A good permalink reads like a table of contents entry. You can look at it and roughly know what page you're about to open. `example.com/pricing`, `example.com/blog/seo-checklist`, `example.com/products/leather-wallet` - each of those is telling you something before you even click. ## Permalink vs URL vs Slug vs Short Link These four words get mixed up all the time. They're related but distinct. | Term | What It Is | Example | |---|---|---| | **URL** | Any web address, anywhere on the internet | `https://example.com/blog/permalink-guide?ref=twitter#comments` | | **Permalink** | The stable, canonical URL of a specific page or post | `https://example.com/blog/permalink-guide` | | **Slug** | Just the identifying end portion of the URL | `permalink-guide` | | **Short link** | A shortened URL that redirects to the permalink | `u2l.ai/permalink` | Every permalink is a URL, but not every URL is a permalink. A URL with tracking parameters (`?utm_source=newsletter`), a fragment (`#section-2`), or a session ID is still a URL, but it's not the canonical permalink of the page - it's a variation of it. Search engines are supposed to [consolidate all those variations back to the canonical permalink](https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls) via `rel="canonical"` tags. The slug is a subset of the permalink. When someone says "change the slug," they mean edit the last part of the URL. The rest of the permalink (protocol, domain, subdirectory) stays the same. Slugs are where most editorial and SEO judgement gets applied because they're the piece publishers actually type themselves. Short links are different creatures entirely. A short link is a redirector that points at a permalink. You paste `example.com/blog/permalink-guide` into U2L AI and get back `u2l.ai/permalink`. Clicking the short link fires an HTTP redirect (301 or 302) and lands you on the permalink. The short link is not a replacement for the permalink - it's a wrapper around it, useful for social posts, QR codes, podcast reads, and any place where the full permalink is too long or ugly to share. If you're new to this, our [what is URL shortening guide](/blog/what-is-url-shortening) walks through how the redirect layer actually works. The mental model that helps: the permalink is the address of your house. The slug is the house number. A short link is a card someone hands you that says "call this number to get directions to the house." All three point at the same building. Only the first one is the actual location. ## Types of Permalink Structures Different platforms and different content models call for different permalink patterns. The most common ones, roughly in order from cleanest to messiest: **Post name only** (`/post-name/`). The cleanest option. Just the slug after the domain. Perfect for blogs where content is evergreen and not tied to a date. **Category and post name** (`/category/post-name/`). Adds a category subdirectory for hierarchy. Nice for sites with strong topic clusters (a cooking blog might use `/recipes/carbonara/` and `/techniques/knife-skills/`). The trade-off: if you move a post to a new category, its permalink changes. **Date and post name** (`/2026/07/post-name/`). Common on news sites where the publish date is part of the identity of the content. Great for daily news. Terrible for evergreen content, because it visually ages the URL and makes it look stale even when the content is still current. **Numeric or ID-based** (`/?p=123` or `/post/123`). The old default and still used by some CMSs for admin URLs. Fine internally, awful for SEO and unreadable to humans. **Nested subdirectories** (`/blog/2026/category/subcategory/post-name/`). What you get when you don't think about permalinks and just accept every CMS default at once. Deeply nested URLs are harder to remember, worse at click-through in search results, and offer no real SEO benefit over a shallow structure. A permalink structure isn't just cosmetic. It's the shape of the URL tree Google will crawl, the address bar users will look at, and the string every backlink to your site will contain. Pick it once, deliberately, and don't second-guess yourself six months later. ## The Best Permalink Structure for SEO in 2026 The consensus across every major SEO publication and platform is that **post name (`/post-name/`) is the best default for most sites**. Yoast, Rank Math, WPBeginner, Kinsta, WP Engine, and every serious SEO plugin all recommend it. There are real reasons for that. Post-name permalinks: - Put keywords right in the URL where Google can see them - Stay evergreen (no visible year decays the perceived freshness) - Are short and memorable - Look clean in social shares (the entire URL fits inside a tweet without eating your character budget) - Match user intent, which nudges click-through rate up in search results There are legitimate exceptions. **News sites** with time-sensitive content often use `/YYYY/MM/post-name/` because the date is part of the story's identity. **Publishers with massive archives** sometimes use `/category/post-name/` to help both crawlers and users navigate. **E-commerce stores** typically want `/product/slug/` or `/category/product-slug/` because product pages benefit from being visibly grouped. For every other site - blogs, marketing sites, personal portfolios, SaaS content marketing - the answer is post name. Set it once at launch, never touch it again. The rare times you actually need to change a permalink after that (typo, brand rename, restructure), do it with a 301 redirect from the old URL and treat it as a real event, not a routine edit. One thing worth calling out: keep the slug short. Two to five words is the sweet spot. Anything longer than that gets truncated in Google search results and starts looking spammy. `example.com/blog/what-is-a-permalink` reads clean. `example.com/blog/the-complete-ultimate-2026-guide-to-what-a-permalink-is-and-why-it-matters-for-seo` reads like keyword stuffing (because it is). ## How Permalinks Work Under the Hood When you click a permalink, a straightforward chain of events plays out in a fraction of a second. 1. Your browser resolves the domain to an IP address via DNS. 2. It opens an HTTPS connection to the server at that IP. 3. It sends an HTTP GET request for the specific path (`/blog/what-is-a-permalink`). 4. The server matches the path to a piece of content in its database. 5. It returns the HTML for that page with a `200 OK` status. 6. Your browser renders the page. That's the happy path. The interesting stuff happens when a permalink changes or gets shared through a wrapper. If a permalink was moved and a 301 redirect was set up, the server returns a `301 Moved Permanently` status with a `Location` header pointing at the new permalink. Your browser silently follows the redirect and loads the new URL. Search engines see the 301 and pass essentially all the SEO equity from the old URL to the new one. Our [301 vs 302 redirects guide](/blog/301-vs-302-redirects) breaks down when to use each. If a short link is in the middle, the flow adds one hop. You click `u2l.ai/permalink`, the short link resolves at the edge, U2L AI's server returns a 301 or 302 pointing at your permalink, your browser follows the redirect, and now you're on the destination. From the user's perspective it looks like a single click. Under the hood there are two round trips, but on a proper edge network the whole thing wraps up in a small number of milliseconds. The point of understanding the flow is that a permalink isn't a static file sitting on a server. It's a routing rule. The server sees a URL come in and decides what to serve. That flexibility is exactly what makes permalinks valuable - and also exactly what makes them dangerous when publishers casually change the URL structure of a site without thinking about the routing consequences. ## How to Change a Permalink Without Killing SEO Sometimes you genuinely have to change a permalink. Maybe you renamed your brand, restructured your blog, or realised the original slug was a typo you can't unsee. The move is the same in all three cases: change the URL and set up a 301 redirect from the old address to the new one. The step-by-step: 1. **Decide on the new permalink.** Pick something you'll be happy with in five years, not just this quarter. Keep it short, descriptive, and free of dates unless the date is genuinely part of the identity. 2. **Update the permalink in your CMS.** In WordPress, that's the "URL" field in the block editor. In Ghost, Webflow, Shopify, etc., the field name varies but the concept is the same. 3. **Set up a 301 redirect** from the old permalink to the new one. Most CMSs have plugins or built-in tools for this (Redirection for WordPress, native 301s in Ghost, redirect rules in Webflow). If you're on Cloudflare or Vercel, you can add page rules there too. 4. **Update internal links** across your site to point at the new permalink directly. Redirects work, but chained redirects are slow and dilute SEO equity slightly. 5. **Submit the new URL** in Google Search Console and request re-indexing. 6. **Test** by loading the old URL in a private browser window and confirming the redirect fires cleanly with the right status code. The gotcha most people miss: 301 redirects are not free. Each redirect adds a hop and a small amount of latency to the first click. On a global edge network the cost is negligible. On a slower server it can add hundreds of milliseconds. Don't stack redirects - always redirect from the original old URL directly to the final new URL, never through an intermediate. The other gotcha is that redirects need to live forever. If you set a 301 today and remove it in two years because you assume everyone's moved on, the old links stop working overnight. Treat 301 redirects as permanent infrastructure, not temporary Band-Aids. ## Common Permalink Mistakes We've seen every one of these. They're all avoidable. **Including the date in slugs on evergreen content.** `example.com/blog/2019/03/seo-tips-for-beginners` visually decays. The article might have been updated last week, but the URL screams "2019." Use `/blog/seo-tips-for-beginners` and update the visible publish date in the content instead. **Slugs full of stop words.** `example.com/blog/how-to-write-a-great-blog-post-that-people-will-actually-want-to-read`. Cut it to `/how-to-write-a-blog-post`. Google's crawler doesn't need articles and prepositions. **Automatic numeric suffixes.** When two posts share a slug, some CMSs auto-add `-2` or `-copy`. Fix the base slug instead. `example.com/pricing-2` looks like a leftover draft. **Special characters in slugs.** Emojis, accented characters, spaces (URL-encoded as `%20`), and other non-ASCII in slugs will technically work but scan badly across email, chat, and PDF links where the encoded characters render as gibberish. **Deep nesting for the sake of it.** `example.com/blog/marketing/seo/on-page/technical/2026/what-is-a-permalink`. Just make it `example.com/blog/what-is-a-permalink`. Google doesn't reward deep hierarchies over shallow ones for the same content, and users find shallower URLs more trustworthy. **Changing permalinks casually.** The single biggest one. Every URL edit needs a 301 redirect. No exceptions. **Ignoring canonical tags.** If the same content lives at multiple URLs (paginated archives, query-parameter variations, tracking URLs), point them all at the canonical permalink with `rel="canonical"`. This is one of the underrated levers for consolidating SEO signal. ## Permalinks and Short Links: How They Work Together Permalinks are the destination. Short links are the delivery mechanism. They're not competing formats - they solve different problems. Publish a blog post at `example.com/blog/what-is-a-permalink`. That's the permalink and it's what Google indexes. Now you want to share the same post in a tweet, a podcast script, a printed flyer, and a QR code on packaging. A raw permalink works for the tweet. But for the podcast ("point your browser to example dot com slash blog slash what dash is dash a dash permalink") it's awkward. For the flyer with limited space, it eats too much room. For the QR code, a longer URL creates a denser pattern that scans worse. **Short links wrap the permalink** with something like `u2l.ai/permalink`. The short link redirects (301 or 302) to the actual permalink. Every click still ends up at the same canonical page. Nothing about the SEO changes. But you gain trackability (every click is logged with geo, device, browser, referrer data), memorability (the podcast host can just say "u2l.ai slash permalink"), and QR code compatibility (the shorter URL scans cleaner). U2L AI runs the short link layer on a global edge network with 330+ locations, so the redirect step adds a very small amount of latency. The permalink is still the SEO surface. The short link is the marketing surface. Real teams use both. A subtle point that trips people up: never treat a short link as a canonical URL. Search engines should always index the permalink, not the redirector. If you're linking from your own blog post to another article on your site, use the raw permalink. Save short links for external channels where length and trackability actually matter. For getting your own short URLs set up, our [how to create a custom short URL guide](/blog/how-to-create-custom-short-url) walks through the process step by step, and [what is a branded link](/blog/what-is-branded-link) covers why swapping the generic short domain for your own brand's domain lifts click-through rate by roughly a third. You can also skip the setup entirely and generate a short link with no login at the [U2L AI URL shortener](https://u2l.ai/url-shortener) - paste a permalink, get back a clean short link in a second. ## Frequently Asked Questions ### What is a permalink in simple terms? A permalink is the permanent web address of a specific page or post on a website. It's designed to stay the same forever, so bookmarks, backlinks, and shared links keep working even after the content is edited or updated. ### What is the difference between a permalink and a URL? Every permalink is a URL, but not every URL is a permalink. The permalink is the canonical, stable URL of a page. A URL might include tracking parameters (`?utm_source=email`) or a session ID that make it a variation of the permalink rather than the canonical version itself. ### What is the difference between a permalink and a slug? The slug is only the last piece of the permalink - the identifier that comes after the domain. For example, in `https://example.com/blog/permalink-guide`, the permalink is the full URL and the slug is just `permalink-guide`. Slugs are the part of the permalink you usually edit directly in your CMS. ### What is the best permalink structure for SEO? The `/post-name/` structure is the standard recommendation for blogs and content sites. It's short, descriptive, doesn't age the URL with a visible date, and puts keywords right where search engines look for them. News sites often add the date, and e-commerce stores usually use a `/product/slug/` pattern. ### Can I change a permalink after publishing? Yes, but only carefully. Every permalink change should include a 301 redirect from the old URL to the new one so backlinks and bookmarks keep working. Otherwise you'll lose search rankings, break external links, and confuse loyal readers. ### Do permalinks affect SEO? Yes, in two ways. Descriptive permalinks with keywords in the slug can slightly boost rankings and click-through rate. And stability matters even more - changing a permalink without setting up a proper 301 redirect can wipe out months of SEO effort in a weekend. ### What is a permalink in WordPress? In WordPress, a permalink is the permanent URL of a post, page, category, or other content type. You set the site-wide structure under Settings → Permalinks (most sites should pick "Post name"), and you can edit individual post slugs from the block editor. ### Are short links and permalinks the same thing? No. A permalink is the canonical URL of the actual page. A short link is a redirector that points at the permalink and is useful for sharing (social posts, QR codes, podcasts). Search engines should index the permalink, not the short link. ### How long should a permalink be? Aim for 3 to 5 meaningful words in the slug. That keeps the URL under about 60 characters, which fits cleanly in Google search results without truncation. Longer than that starts looking like keyword stuffing. ### What happens if I change a permalink and don't set up a redirect? Every external link to the old URL breaks. Google eventually deindexes the old URL and reindexes the new one from scratch, so you lose accumulated ranking authority. Bookmarks fail. Analytics history splits. It's an entirely avoidable disaster. ## Get Permalinks Right Once and They'll Work Forever Permalinks are a small piece of technical hygiene with an outsized impact on how well a site holds up over time. Pick the right structure (`/post-name/` for most blogs), keep slugs short and descriptive, treat every URL change as a real event that needs a 301 redirect, and use short links for the places where the raw permalink is awkward to share. Do that consistently and the permalink layer of your site quietly compounds SEO value in the background for years. Ready to give your permalinks a proper short-link wrapper for social, podcasts, print, or QR codes? [Sign up free at U2L AI](https://u2l.ai/app/signup) and you'll get branded short links, dynamic QR codes, link-in-bio pages, and analytics that show you every click your permalinks earn. No credit card, no forced upgrade, no login required if you just want to shorten a link on the way out. If you want to go deeper on adjacent topics, [what is URL shortening](/blog/what-is-url-shortening) explains how the redirect layer works, [what is a branded link](/blog/what-is-branded-link) covers the CTR lift from custom domains, and the [301 vs 302 redirects guide](/blog/301-vs-302-redirects) unpacks the SEO trade-offs behind every URL change. For the practical setup side, [how to create a custom short URL](/blog/how-to-create-custom-short-url) walks through the three steps end to end, and [do URL shorteners hurt SEO](/blog/url-shorteners-seo-impact) settles the argument on whether short links quietly leak ranking authority (they don't, when configured properly). The rule to live by: permalinks are permanent by design. Once you publish one, treat it like the address of a building you built - other people will start using that address, and you don't get to move the building without a lot of expensive paperwork.