What is a Permalink?

Permalink: the address you expect to keep working

A permalink is the full permanent URL for a resource. Blog platforms popularized the term because posts need addresses that survive homepage churn. In SEO, permalink stability is a foundation: external links, bookmarks, sitemaps, and canonical tags all assume the permalink you published yesterday still resolves today.

Permalinks are contracts with the web. Breaking them without redirects wastes years of accumulated references.

Permalink vs slug vs canonical

The slug names the page; the permalink is the whole address. The canonical URL may match the permalink—or point to it when parameters create duplicates.

Parts of a permalink

https://www.example.com:443/blog/on-page-seo/permalink-guide/
└scheme┘ └────host────┘└port┘└─────────── path ──────────────┘
                              └── slug segments may nest here ──┘

SEO decisions tied to permalinks:

• HTTPS by default
• Consistent www vs non-www host
• Lowercase paths
• One trailing-slash policy
• No session IDs or tracking params in the canonical permalink

Why permalink stability matters

Permalink patterns by content type

Document templates early:

Mixed patterns without redirects—/post/123 and /blog/title for the same template—create duplicate permalink clusters.

Pretty permalinks vs ugly permalinks

Ugly default:

https://example.com/index.php?p=4421&cat=7

Pretty permalink:

https://example.com/glossary/permalink/

Both can be crawlable, but pretty permalinks improve sharing, readability in SERPs, and pattern-based analytics. Migration requires mapping every old query-based URL to its new path with 301 redirects.

Permalink settings in CMS platforms

WordPress, Webflow, Shopify, and others expose "permalink structure" or "URL handle" settings. Common pitfalls:

• Changing structure site-wide without redirect tables
• Auto-updating handles when titles change
• Staging domains leaking into production permalinks
• Trailing slash mismatch between CDN and origin

Lock production permalink rules in runbooks. Test migrations on a crawl clone first.

Permalink governance checklist

• Publish one canonical permalink per indexable resource—no parallel paths.
• Never append session IDs or internal tracking params to indexable permalinks.
• Use 301 redirects when retiring permalinks; update internal links the same week.
• Regenerate XML sitemaps with new permalinks only after redirects are live.
• Align permalink topic with page intent—misleading paths hurt CTR and engagement.
• Audit external backlinks before permalink changes on high-authority URLs.

Permalinks and on-page SEO

Permalinks sit alongside title tags, headings, and body copy as orientation signals. They do not replace content quality or search intent alignment. A keyword-stuffed permalink with thin content still fails.

Align permalink, slug, and primary topic so users who see the URL in SERPs or Slack previews know what to expect.

Permalink myths

• Myth: "Changing a permalink is fine if you update the canonical tag." Reality: users and links still request the old URL—redirect.
• Myth: "Permalinks must mirror the title tag word for word." Reality: stable, descriptive paths beat brittle mirroring.
• Myth: "Query-string permalinks are always bad." Reality: ugly for humans, but redirect beats leaving orphans during migration.
• Myth: "Short permalinks rank better by default." Reality: clarity and stability matter more than arbitrary length.

How Crawlox helps with permalinks

Crawlox crawls declared permalinks, compares them to canonicals and redirects, and highlights duplicate paths, chains, and parameter variants. Find when a CMS plugin invents a second permalink for the same content before indexation splits.

The practical takeaway

A permalink is the full permanent URL—not just the slug. Treat it as infrastructure: choose clear patterns, avoid churn, redirect when you must change, and keep one authoritative address per page.