SEO-friendly permalinks make WordPress posts and pages easier to recognize before the page loads. A slug-based path carries the topic of the content in the URL itself, so copied links and search results are clearer than the default ?p=123 form.
WordPress controls the global permalink pattern from Settings → Permalinks. The Post name structure uses each published post or page slug for its public path, while the optional category and tag base fields only affect category and tag archive prefixes.
Changing permalinks on an established site changes public URLs, so the cutover should be treated as a live URL change rather than a cosmetic toggle. On Apache, WordPress can update .htaccess only when the file is writable; otherwise the dashboard shows the rewrite rules to copy manually. On standalone Nginx, the server block for the site must already pass clean URLs to WordPress before slug URLs will resolve.
Related: How to back up a WordPress site
Steps to configure SEO-friendly URLs in WordPress:
- Log in to the WordPress dashboard with an administrator account.
If the site already serves public traffic, capture a current backup or snapshot before changing the public URL pattern.
- Open Settings → Permalinks.
- Select Post name under Common Settings.
The Category base and Tag base fields in Optional change category and tag archive prefixes only. Leave them unchanged unless those archive URLs are part of the planned URL change.
- Click Save Changes.
If WordPress can write .htaccess on Apache, the page shows Permalink structure updated. If it shows generated rewrite rules instead, copy that block into the site's .htaccess file before testing slug URLs.
On standalone Nginx, WordPress cannot write the server rewrite configuration for permalinks. Confirm the server block uses the standard WordPress front-controller pattern before expecting Post name URLs to work.
- Open a published post or page and confirm the browser address uses a readable slug such as /hello-world/ instead of ?p=123.
If the previous permalink structure was indexed, bookmarked, or hard-coded elsewhere, add redirects or plan the migration before switching production traffic to the new path format.
Mohd Shakir Zakaria is a cloud architect with deep roots in software development and open-source advocacy. Certified in AWS, Red Hat, VMware, ITIL, and Linux, he specializes in designing and managing robust cloud and on-premises infrastructures.
