OUTRANK · PUBLISHED Nov 15, 2026

How to Create a Permalink: Rules, Steps and Redirects

Learn how to create a permalink that lasts: pick the slug, set it on WordPress, Shopify, Webflow or Ghost, and redirect any change safely.

You publish the post, then paste the link into Slack and it reads /?p=4821. Or the CMS gives you /2024/11/uncategorized/draft-final-v3/. Nobody clicks that, and the fix gets harder every day the URL stays live, because links, bookmarks and search results start pointing at the ugly version.

A permalink is a stable URL that identifies one specific piece of content over time. The slug takes about two minutes to get right. The commitment around it, which covers platform settings, redirects, duplicate checks and the identifiers leaking through query strings, is what decides whether the address still resolves in three years.

Table of Contents

How to Create a Permalink Step by Step

The draft is approved, the featured image is set, and the last unchecked field is the slug. That field is the address people will paste, cite and expect to resolve later, so decide it while edits are still cheap. Keep this lookup open while doing it; every step below applies one row.

Element Keep this Avoid this Why it matters
Slug /blog/how-to-create-a-permalink /blog/post-1 A readable slug tells people and search engines what the page covers
Separators how-to-create-a-permalink how_to_create_a_permalink Hyphens separate words clearly for users and search engines
Date folders /guides/create-permalink /2024/11/create-permalink Dates make evergreen pages look outdated and break when the date structure changes
Categories /guides/create-permalink /guides/seo/tools/create-permalink Deep category nesting breaks when the category tree is reorganised
Query strings /guides/create-permalink ?utm_source=newsletter on the canonical URL Tracking values create alternative URLs for the same content
Fragments /guides/create-permalink Using #examples as the page address A fragment points to a section within the page, not a separate page

The seven steps in order

  1. Start with the topic, then shorten it. Take the working title "How to Create a Permalink" and cut it to how-to-create-a-permalink. Three to five words is the useful range. People scanning a link and search engines parsing it both read the topic words first, and filler like "the", "a" or "your" carries nothing.

  2. Lowercase everything and join words with hyphens. Mixed case invites typos when someone retypes the link, and underscores vanish under some link underlines. Hyphens make the boundaries between concepts visible.

  3. Cut filler, never the topic word. create-permalink beats how-to-create-a-permalink-for-your-blog, and both beat create-the-thing. Read the slug back to yourself: if a stranger couldn't guess the page's subject, you cut too far.

  4. Remove dates, numeric IDs and category layers. Each one ties the address to a structure you might reorganise next quarter. When that structure changes, every URL under it has to move or break.

  5. Strip tracking values and session IDs. The RFC 3986 URI standard splits an address into scheme, authority, path, query and fragment. The path is the stable part to publish; the query begins with a question mark and supplies extra, non-hierarchical data, which is exactly what ?utm_source=newsletter is. Hand out the clean path and nothing else.

  6. Save the slug before publishing. The common slip is publishing on the default address and fixing the slug a week later, once a newsletter and three internal links already point at the old string. From that moment the old address needs a redirect to keep working.

  7. Open the live URL and copy that exact string into internal links. Paste from the address bar, and delete any query string that appears because you arrived from a campaign. A link built from a tracked URL spreads the tracking value into the next page's referrer data.

Where fragments fit

#examples is not an address. Under RFC 3986, a fragment begins with a number sign and identifies a secondary location inside the primary resource, so /guides/create-permalink#examples is the page plus a jump. Keep the fragment out of sitemaps, citations and canonical tags, and keep the anchor from being treated as a page of its own.

Addresses have had a formal framework since the IETF published RFC 1738 as a proposed standard in December 1994, defining URL syntax so a link points at a specific resource. The historical lesson is worth keeping: a URL identifies a resource's location, and staying reachable is a separate maintenance job.

One number keeps the length debate in proportion. An SEO-Kreativ analysis of 27,000 search results found the top three results had a median URL path length of 30 characters, against 32 for positions 4 to 10. Two characters is noise. Readability is what you control. If you're building the blog out, run this slug rule alongside the rest of the blog SEO guide for founders so the address, title and internal links get decided in the same pass.

Setting Permalinks on WordPress, Shopify, Webflow and Ghost

The setting lives somewhere different on each platform, and so does the damage when you change it.

Platform Where to set it Default pattern Change risk
WordPress Settings > Permalinks, then Post name /sample-post/ Changing the structure site-wide affects every existing post URL
Shopify Search engine listing, URL and handle, on the blog post /blogs/news/post-handle Changing the handle creates a redirect from the old handle
Webflow Page settings > SEO settings > Slug /page-slug Changing a published slug needs republishing and a 301 redirect
Ghost Post settings > Post URL /post-slug/ Edit the URL before publishing; later changes affect shared links

WordPress is the one that surprises people. Selecting Post name produces /sample-post/, but it's a site-wide setting: switching it rewrites the address of every existing post at once, so a site with three years of content needs a redirect for each one. Set it on day one or budget a careful afternoon for the map.

Shopify handles the common case well. The handle sits in the Search engine listing panel, and changing it generates a redirect from the old handle. Check anyway, because that redirect is invisible in the admin, and a second edit can leave the original address pointing somewhere you didn't plan.

Webflow stores the slug in Page settings > SEO settings. Editing a published slug does nothing until you republish, and Webflow won't create the redirect for you, so add a 301 for the old path in the project's publishing settings.

Ghost puts the Post URL in the post settings, prefilled from the title. Edit it before you publish. On a post that already earns search traffic, a later change costs you the shares and citations pointing at the old address.

Custom builds and the site builders

Hugo, Eleventy and Next.js take the slug from the file name or the route, so renaming the source file is the change, followed by a 301 in the host's redirect configuration. Wix and Squarespace expose the slug in the page SEO panel. After saving on any of these, check three things: the live URL resolves cleanly, the sitemap lists only the new address, and the old path returns a one-hop redirect.

A slug you change is a slug you have to maintain. On a 40-post blog that's a text file. On a 5,000-post catalogue it's a project with a spreadsheet, and it's worth asking whether the readability gain pays for it.

If you're still choosing rather than living with a platform, pick a CMS built for rankings before you commit to a URL structure, because migrating later costs more than the setting does today.

Redirects and Status Codes for Changed URLs

A URL change is an address change, not a rename: a product line is renamed, a section is merged, or a domain moves. The response code you send decides whether the old address keeps working or dies.

Situation Response Example
Page moved permanently 301 or 308 to the new URL /old-post to /articles/permalink-guide
Page replaced by a close match 301 to the closest equivalent /tools/slug-tool to /tools/slug-generator
Page deleted with no replacement 404 or 410 /retired-webinar with no successor page
Temporary change 302 or 307, then restore the original /sale-page during a promotion, then restored
Typo or never existed 404 /permalnk-guide

Inventory first, then redirect

Export every live URL from the CMS or the sitemap and map each one to its new address before you change anything. The map is the deliverable; the redirects are just its implementation. A page with no close replacement should return 404 or 410 rather than redirect to the homepage, because a blanket homepage redirect reads to search engines as a soft error and leaves the visitor stranded.

Then keep the chain short. Google's guidance on redirect chains treats Googlebot's ability to follow redirects as limited, so point the oldest URL straight at the final destination instead of stacking one rule on another. Each extra hop is another request that can fail, time out, or be abandoned by a stricter client.

Rebuild the path properly while you're in there. Google's URL structure guidance prefers hyphens to underscores for separating words, and asks for as few parameters as possible, specifically removing the ones that don't change what the page shows. During the same move, strip tracking parameters from the canonical target and make sure the redirected address doesn't expose a staging, filtered, or session version of the page. A move from /old_post?id=88 to /articles/permalink-guide fixes structure and address in one action, which is the cheapest moment to do it.

How long do redirects stay up: as long as the old address attracts links or traffic. In practice that means years. There's no maintenance cost to leaving a one-hop rule in place, and there's a real cost to removing it.

After the change, confirm that internal links, canonical tags, structured-data URLs and the sitemap all point at the new address, then test a sample of old URLs in a browser. A crawl will catch the rest, and the site health audit checklist gives you an order to work through so you're not chasing orphaned links one at a time.

Troubleshooting Broken and Duplicate Permalinks

Match the symptom, apply the fix, then confirm on the live URL before moving on.

  1. A new post returns 404 after a WordPress permalink change. Re-save Settings > Permalinks to rebuild the rewrite rules, then confirm the server rewrite configuration on Apache or Nginx passes requests to WordPress. Check: the post loads at its new address with no query string.

  2. A redirect loop stops the browser after several hops. Two rules point at each other. Trace the headers with a status checker, find the rule matching the target path, and delete it. Check: the URL resolves in one hop.

  3. Two URLs serve the same page, one with a trailing slash and one without. Pick one canonical form, set a canonical tag on it, and send the other form to it with a 301. Check: only one version returns 200.

  4. An old URL still shows in search results after redirecting. Confirm the response is a 301 rather than a 302, confirm the sitemap lists only the new address, and give the crawler time to revisit. Check: the search result updates after recrawling.

  5. Your browser keeps showing the old page. Clear the cache or test in a private window before you assume the redirect failed. Check: a fresh session shows the new destination.

  6. An audit surfaces a redirect chain. Rewrite the first rule so the old address points directly at the final destination, then retest. Check: one hop, correct destination.

Working through these in order is faster than guessing, and the step-by-step search optimization checklist keeps the verification pass from turning into a full site review.

Mistakes to Avoid and the Structure to Lock In

The costliest permalink mistake is changing a live slug without a redirect. Citations break, bookmarks 404, referral traffic lands on nothing and whatever search visibility the page had accumulated has to be rebuilt at a new address.

A person editing a blog post URL in a laptop browser to explain redirecting before renaming permalinks.

Stuffing keywords into one path makes the URL read as spam and gives you a slug nobody can retype. Keep it to the topic, then put the secondary phrases in the title and body where they belong. Creating two URLs through a trailing slash or a tracking parameter splits signals across duplicates. Choose one canonical form and redirect the other.

Using the raw URL as the visible link text is the mistake with the widest blast radius. The University of Washington accessibility guidance on links and buttons is blunt about it: raw URLs are difficult for screen-reader users to understand and hard for voice-input users to express. Write anchor text that describes the destination, and let the slug do its quieter job of staying recognizable when it gets copied.

Here's the operational version of that distinction, since it changes how you check a page before publishing.

Leaking identifiers through the path or query string is a privacy problem that often goes unaudited. Customer IDs, search terms, campaign names and internal workflow states all end up in shared links, analytics exports and screenshots. Keep them out of public URLs entirely, and pass state through a form or a session instead.

On multilingual sites, check transliteration before translating a title into a slug. A slug that becomes a string of percent-encoded characters is unusable in voice input and ugly in a chat window, so a short Latin-character identifier often serves better. The same logic applies to products, research documents and APIs: a stable identifier beats a keyword slug when the thing is likely to be renamed, because the identifier can survive the rename.

Then lock the structure. Choose one pattern, /blog/slug, write it as a three-line rule sheet, and audit existing URLs against it before the next post goes out. The SEO Agent's slug generator returns the canonical hyphenated slug plus underscore and dot variants, computed in the browser with no sign-in, which is a quick way to see the separators side by side before you commit.

The reason to commit rather than iterate is that addresses decay without anyone touching them. A 2024 longitudinal study of 27.3 million HTML URLs captured by the Wayback Machine between 1996 and 2021 reported a median page lifespan of 2.3 years, and deep links were far more fragile, with a median of 1.3 years against 8.8 years for root URLs; 41.92% of the sampled URLs produced errors, per the study published through ACM. A permalink isn't a descriptive URL. It's an operational commitment to keeping an address and its destination alive.

Write this into your style guide: every public URL is a long-term address, so change it only with a redirect in place.

Write the rule sheet today, then publish the first post under it. If you sell on Shopify, the SEO checklist for Shopify stores covers handle changes alongside the rest of the store setup.


The SEO Agent is built for the part that comes after the slug: it researches keywords, drafts articles in your voice with citations, wires internal links to pages you already have, and publishes into WordPress, Shopify, Webflow, Ghost, Wix, Notion or Framer with the slug, meta description and schema already set. If you'd rather ship product than maintain a redirect spreadsheet, you can try it for $1 for 3 days, then $99/month with one-click cancellation. Start at The SEO Agent and put your next post live under a URL you won't have to fix later.

create a permalinkpermalink structureSEO URLURL redirectsWordPress permalinks