← Back to Blog

WordPress Permalink Settings

Plan the global URL structure for posts and taxonomy bases before publishing, and use redirects when existing URLs change.

Veyra Admin

4 min read

  • Guide
  • Beginner
  • 4 minutes read
  • Reviewed August 5, 2026
  • WordPress administration and configuration

Permalink Settings control the global URL structure used for standard WordPress posts and selected taxonomy bases.

A permalink is intended to remain stable. Changing an established structure can create broken links, redirect chains, lost analytics continuity and search disruption.

Plain URLs identify content through query parameters. Pretty permalinks use readable paths generated through rewrite rules.

Readable URLs improve usability and make content structure easier to understand. Their operation depends on suitable web-server configuration.

Common Structures

WordPress provides options such as Plain, Day and name, Month and name, Numeric, Post name and Custom structure.

Date structures can suit time-dependent publications. Post name is common for evergreen content. The shortest URL is not automatically the best; the structure should be stable and compatible with the editorial model.

Custom Structure Tags

A custom structure can include year, month, post ID, category and post name.

Complex structures can introduce ambiguity, long paths, route conflicts and expensive migrations. Use only components with a clear purpose.

Category and Tag Bases

The screen can change base paths for built-in category and tag archives. Custom post types and taxonomies define rewrite behavior elsewhere.

Coordinate routes across the complete content model.

Saving the screen refreshes WordPress rewrite rules. This is often useful after registering a post type or taxonomy.

Plugin code should not flush rules on every request because repeated flushing is expensive.

Changing a Live Structure

  1. Crawl existing URLs.
  2. Map old patterns to new destinations.
  3. Configure permanent redirects.
  4. Test pagination, feeds and archives.
  5. Update internal links.
  6. Update sitemaps and canonical URLs.
  7. Monitor 404 logs and search tools.

Do not rely on search engines to discover new locations without redirects.

Server Requirements

Pretty permalinks require the web server to route matching requests to WordPress. Apache, Nginx and managed platforms use different configuration.

If saving the screen does not resolve a 404, investigate server rules, caching, permissions and route conflicts.

Frequently Asked Questions

Is Post name always the best structure?

It is common, but the best structure depends on the publication model and existing URLs.

No. It refreshes WordPress rules but cannot fix every server or registration problem.

Should I change URLs only for SEO?

Only when the long-term benefit justifies migration risk.

Record the current value, the reason for the change and the expected result. Make important configuration changes in a controlled window, test the affected workflows and document settings that another administrator will need to understand.

A connected concept is Fixing WordPress Permalink and 404 Problems. Reading the two together helps separate the immediate task from the wider WordPress responsibility.

A useful implementation begins by writing down the current state, the intended outcome and the evidence that will prove the change worked. This prevents a configuration screen, plugin recommendation or code snippet from becoming the entire strategy.

A Practical Example

Imagine a team making this decision for a production WordPress site. The useful question is not only “Can WordPress do this?” but “Which layer owns it, who maintains it, what data does it affect and how will we verify it after an update?”

Write the answer in operational terms. Name the content, user, setting, file, API or service involved. Then identify what should remain true if the theme changes, a plugin is replaced or the site is migrated.

Questions to Ask

  • What user or system problem does this solve?
  • Which WordPress layer owns the behaviour?
  • What data is created or changed?
  • Who may perform the action?
  • What can fail, and how will that failure be visible?
  • How is the result tested after updates?
  • What is the migration or removal path?

Official Reference Context

The Plugin Handbook is the primary version-specific reference for this topic. Use the current documentation to verify interface labels, supported APIs and behaviour before applying instructions to a production site.

How to Verify the Result

  • Record the previous setting and the expected change.
  • Test frontend, administration, email, scheduled tasks and affected integrations.
  • Confirm that the configuration is documented for handover and recovery.

Editorial and Operational Review Checklist

  • The article answers its primary question in the opening paragraphs.
  • Terms are defined before advanced detail is introduced.
  • Examples use realistic WordPress objects, users or workflows.
  • Version-sensitive behaviour is linked to an official source.
  • Security, accessibility, performance and maintenance implications are acknowledged where relevant.
  • The reader has a clear way to validate the result.
  • Internal links lead to prerequisites and deeper related material.
  • The final implementation can be handed to another person without relying on undocumented knowledge.

Sources and Further Reading

Continue Learning