WordPress's permalink settings (Settings > Permalinks) determine the URL structure for posts and pages. The choice has long-term consequences because changing permalinks later requires URL redirects for every existing post, and the redirects affect SEO during the transition period.

The right permalink structure depends on the content type and editorial pattern. The default settings work for many sites but aren't optimal for all. The honest framing: pick the structure that matches how your content will actually be organized and consumed, and commit to it from day one.

The structure options

WordPress offers several permalink presets and a custom structure field. The common ones:

Post name: /sample-post/. The URL is just the post slug. This is the cleanest structure for content sites because URLs don't contain dates or categories.

Day and name: /2026/04/17/sample-post/. Includes the publish date. Standard for news sites and blogs where date relevance matters.

Month and name: /2026/04/sample-post/. Includes year and month but not day. Slightly less verbose than day-and-name.

Numeric: /archives/123. Uses just the post ID. Rarely recommended because URLs convey no information.

Custom structure: any combination of tags like /%category%/%postname%/. Allows category slugs in the URL.

The recommendations by content type

For content-focused sites (blogs, marketing sites, educational sites), the post-name structure is usually best. URLs are clean, transferable, and don't tie a post to a specific date.

For news sites where date is part of the article's identity, day-and-name is appropriate. An article from January 2024 explicitly says so in the URL, which helps users recognize stale content.

For category-driven sites where the category is a meaningful part of the URL (a hierarchical product catalog, a multi-section magazine), the custom structure with category can work. The trade-off is that moving a post between categories changes its URL, requiring redirects.

The case against including the category

The intuitive appeal of /%category%/%postname%/ is that URLs convey topic information. The downside is operational: every category change is a URL change. Articles get recategorized as the site's structure evolves, and each recategorization breaks the original URL.

For sites that frequently reorganize content, the category-in-URL structure creates maintenance burden. The post-name-only structure decouples URL from category, letting categories change without URL changes.

For sites where categories are stable and meaningful (a recipe site organized by cuisine type, where Italian stays Italian), category-in-URL works fine.

The post type considerations

Custom post types use the URL structure /custom-type-slug/post-slug/ by default. The /custom-type-slug/ portion is set when registering the post type.

For sites with multiple custom post types (recipes, courses, case studies), the URL structure produces clear semantic organization: /recipes/chocolate-cake/, /courses/intro-to-wordpress/, /case-studies/acme-corp/. This is one of the clean benefits of CPT use.

The custom post type slug should be chosen carefully because changing it later requires redirects for every URL.

The case study: changing permalinks on an established site

A site with 2,000 published posts on day-and-name structure decided to migrate to post-name structure to clean up URLs. The change required:

Setting up 301 redirects from every old URL to the new equivalent
Updating internal links throughout the site (many were absolute URLs to the old format)
Re-submitting the sitemap to Search Console
Monitoring for 4-6 weeks as Google re-crawled and re-indexed

The cost was about 40 hours of focused work and a temporary 15% traffic dip during the transition. Six weeks later, traffic had recovered to baseline. After three months, traffic was slightly higher than before because the cleaner URLs performed better in click-through testing.

The lesson: changing permalinks on an established site is possible but expensive. Make the right choice initially to avoid the cost.

The trailing slash question

URLs can end with a trailing slash (/sample-post/) or without (/sample-post). WordPress handles either form and redirects between them based on the site's configuration. The choice doesn't affect SEO directly; pick one and be consistent.

The pattern that's slightly more common: include the trailing slash for content URLs (/blog/post-name/), exclude it for file-like URLs (/sitemap.xml). The convention isn't strict and either is acceptable.

The non-English character question

Post slugs can include non-ASCII characters in some languages. The URL might be /artículos/mi-primer-post/ with the accented character preserved.

The browser handles these URLs correctly through percent-encoding (the URL bar shows the friendly characters; the actual HTTP request encodes them). Some older systems and shared links handle them less gracefully.

For sites in languages with non-ASCII characters, the choice is whether to preserve them in slugs or to use ASCII-only slugs. ASCII-only slugs are more compatible across systems; original-character slugs are more readable in the language.

WordPress defaults to ASCII slugs by transliterating most characters automatically. The result is usually acceptable but can produce odd transliterations (German umlauts become ue, oe, ae; Spanish accents disappear). For sites where original characters matter, configure WordPress or use a plugin to preserve them.

The honest summary

The post-name permalink structure is the right choice for most WordPress sites in 2026. It's clean, flexible, and doesn't lock URLs to dates or categories. Change to a different structure only if you have a specific reason (news site needing date in URL, hierarchical catalog needing category in URL).

Make the decision early and commit to it. The cost of changing later is high enough that "we'll fix it later" usually means "we'll live with it indefinitely."

WordPress Permalinks: The Structure Decision That Sticks