Permalinks

A permalink is the full URL of a specific web page — designed to remain stable and unchanged over time. Permalinks are how content is referenced, shared, bookmarked, and indexed.

Designing them well is a one-time investment that provides a cornerstone for a good website; getting them wrong can be detrimental long-term and set you up for a headache of a migration task to resolve them when eventually addressed.

What makes a good permalink

Readable

A user (or a search engine) should be able to guess what's at a URL just by reading it.

• Good: /blog/canonical-tags-explained
• Bad: /?p=1234
• Bad: /article/cat=12&id=8754

Stable

The URL doesn't change when content is updated, recategorised, or republished. If a URL has to change, a 301 redirect is permanent and chained correctly.

Short

Shorter URLs are easier to read and tend to perform marginally better in search results. Strip filler words ("a", "the", "and") that don't add meaning.

Descriptive

Use real words that describe the content, not numbers or codes.

Lowercase

Mixed-case URLs (/About-Us) cause case-sensitivity issues on some servers. The standard convention is all lowercase.

Hyphen-separated

Use hyphens (-) between words. Underscores are interpreted as part of a word by Google, not as a separator between words. Spaces should never appear in URLs (they encode to %20 creating messy URLs).

No file extensions

/about is cleaner than /about.php or /about.html. File extensions also tie URLs to specific technologies and make migrations harder.

No tracking parameters in the canonical URL

?utm_source=newsletter is fine for tracking, but the canonical URL should be the parameter-free version.

Common permalink structures

Flat structure

/article-name

Simple, short, no hierarchy. Works well for small sites without categories. The drawback is that there is no implicit grouping. Every page lives at the root level, which becomes unwieldy at scale and is not suitable for large sites.

Categorised structure

/category/article-name

Adds context. Useful for blogs, news sites, and resource libraries. Note: changing categories breaks URLs and requires adding redirects, so proper consideration should be given to what categories are required before publishing content begins.

Date-based structure

/2026/01/article-name

Common for news sites. Signals content freshness in the URL. Drawback: makes evergreen content look outdated, and redirects are needed if URLs need to be updated for accuracy when significant corrections or modifications are made.

A date-based structure should typically be avoided unless the date is specifically required, e.g. a news and current events website.

Hierarchical structure

/services/seo/local-seo

Reflects the site's information architecture. Useful for service businesses, large product catalogues, and technical documentation. Overkill for small sites with few pages.

Why permalinks matter for SEO

Keyword signals

URLs are a minor ranking signal but a clear one. A URL containing the target keyword reinforces topical relevance. Avoid keyword stuffing (/best-cheap-affordable-running-shoes-for-men), but do include the primary term naturally.

Click-through rate

URLs appear in search results beneath the title. A clean, readable URL typically results in more clicks than a string of numbers and parameters.

Link equity

When external sites link to a page, they link to the URL. If the URL changes, those links break unless redirects are in place. Stable URLs accumulate link equity over time; volatile URLs lose it with every change.

How to change permalinks safely

Ideally, permalinks should never change. If a change is required due to a CMS migration or unavoidable restructure, some key things to consider are:

• Plan the new structure in full before making any changes. Map existing URLs to their new counterparts.
• Build a redirect map — a list of old URL → new URL pairs.
• Implement 301 redirects at the server or CMS level. Test or monitor that every old URL is redirecting correctly.
• Update internal links to point directly to new URLs. Don't rely on redirects for internal linking — direct links are cleaner and faster, and are best practice.
• Update the sitemap to reflect new URLs only.
• Submit the new sitemap in Search Console.

Issues to avoid

• Letting CMSs auto-generate slugs from long page titles. "How to choose the best running shoes for flat feet in 2026 — a complete guide" becomes a 90-character URL that will be truncated in search results. Edit slugs to a clean version.
• Trailing slash inconsistency. A URL that resolves on /about and /about/ creates duplicate URLs. Pick one and enforce it via redirects.
• Special characters in URLs. Apostrophes, ampersands, accented characters all encode as %XX and look ugly. Strip them.
• Changing URLs without redirects. Every link to the old URL becomes a 404. Backlink equity is lost. Rankings drop.
• Stuffing keywords /seo-services-best-seo-agency-melbourne-australia/ is spammy and counterproductive.
• Versioning in URLs. /blog-v2/article is clunky and won't survive future changes.

Permalink policy

For any site:

• One URL per piece of content.
• Lowercase, hyphen-separated, descriptive slugs.
• Trailing slash convention enforced site-wide.
• File extensions hidden.
• HTTPS only, single hostname (with or without www, but consistently).
• Categories used sparingly and stably.
• Permanent redirects in place for any URLs that change.
• Keep redirects in place permanently.

Bots, crawlers, and linking

Disclaimer: All information contained herein is for informational purposes only. It is not advice or instructional.