Overview
Default ?p=123 URLs hurt SEO and readability. Pretty permalinks use paths like /2024/03/my-post/.
Requires mod_rewrite on Apache or try_files on nginx.
Implementation
Settings > Permalinks > Post name > Save. WordPress writes .htaccess rules on Apache. nginx: try_files $uri $uri/ /index.php?$args; in the server block.
If 404s appear, check file permissions and flush rewrite rules by re-saving permalinks.
When implementing guidance from Enable Pretty Permalinks on WordPress, start in a controlled environment that mirrors production versions of operating systems, runtimes, and network policies. Capture a baseline before changes: export configs, snapshot VMs, or tag releases in source control so rollback stays straightforward if behavior regresses.
Document prerequisites, expected outcomes, and verification steps in a short runbook. Automated checks—smoke tests, health endpoints, or query validations—catch regressions early when platforms receive patches. Security belongs in every workflow: apply least privilege, rotate secrets, and review audit logs after deployment.
If results differ across machines, compare environment variables, permission models, time zones, and regional settings. Intermittent issues often trace to caching layers, stale DNS, or duplicated services bound to the same port.
Example
# nginx location /
try_files $uri $uri/ /index.php?$args;
# Apache (auto in .htaccess)
RewriteRule . /index.php [L]Tips
- Custom structures need unique slugs.
- Multisite has extra rules.
- Cache plugins may need permalink flush.
- Never block index.php in WAF.
- Re-verify after reboots, certificate renewals, or failover exercises.
- Align monitoring and alerts with the failure modes described in this guide.
- Keep vendor documentation links handy for breaking changes between versions.
- Pair automation with a manual spot check during initial production rollout.