WordPress permalink settings define the URL structure used by your site’s posts, pages, categories and tags. That makes the Permalinks screen more than a minor dashboard preference: it is part of the site’s long-term architecture. A deliberate choice is especially important before a new website accumulates content, internal navigation and incoming links.
This guide explains how to compare the available WordPress permalink structure options, select a practical approach for your content model and change the settings with reasonable safeguards. It also presents a staged method for handling a WordPress 404 permalink error. The first step is usually a rewrite-rule refresh, but persistent failures may involve .htaccess, Apache configuration, hosting, migrations, custom post type conflicts or content that no longer exists.
What WordPress Permalinks Control
Permalinks are the URLs WordPress uses for different types of site content. The available settings cover posts and pages through the main structure, while the same screen also provides options for category and tag bases. WordPress offers predefined structures as well as a Custom structure field, so the configuration can reflect the way a site organizes and presents its content.
Changing this setting affects how visitors and other systems reach content. It should therefore be considered together with the site’s content model, publishing habits and long-term URL policy. There is no single structure that the supplied documentation identifies as universally suitable for every website, industry or SEO strategy.
Permalinks as a long-term URL policy
For a new site, choose a structure deliberately before significant content and links accumulate. A practical editorial guideline is to prefer a stable, content-focused structure without dates when the site is not organized around publication dates. This is a planning recommendation, not an official WordPress requirement and not a guarantee of better rankings, security, performance or compatibility.
Date-based structures can be more meaningful when the date is central to how visitors understand the content. The important question is not which option sounds most attractive, but whether the URL policy matches the site’s content model and can be maintained consistently over time.
Comparing WordPress Permalink Structures
The Permalinks screen includes several predefined choices. Each one represents a different way to construct URLs, and the choice should be made according to the role of dates, the site’s content organization and the desired long-term policy.
Predefined structures
WordPress provides the following standard options:
- Plain uses a basic query-based URL format.
- Day and name includes the publication day and the content name.
- Month and name includes the publication month and the content name.
- Numeric uses a numeric URL structure.
- Post name uses the content name as the central part of the URL.
- Custom structure lets the site owner define a different pattern using the available configuration field.
Date-based formats may suit a site where publication timing is an important part of the content model. A stable structure focused on the post name can be a practical choice for a site whose content is not organized around dates, but it should not be presented as the official best option for every project.
Custom structures and taxonomy bases
Custom structure is separate from the optional category and tag bases. The main structure determines how relevant post and page URLs are formed, while custom bases influence the URL wording used for categories and tags. These settings should be considered as one coherent URL policy rather than chosen independently without checking the resulting addresses.
Before using a custom structure, document the intended format and test representative content. Do not assume that changing the pattern automatically preserves every previous URL or creates redirects from all earlier addresses. URL preservation and redirect mapping require separate consideration.
How to Change WordPress Permalink Settings Safely
A controlled change begins before opening the dashboard. Record the current structure, note important URLs and create a current backup or staging copy. These steps reduce the risk of making an irreversible change directly on a live site. If file-level configuration will be involved, make a reversible backup of the existing .htaccess file and do not overwrite it blindly.
Dashboard change procedure
- Open Settings > Permalinks in the WordPress dashboard.
- Review the current structure and choose the intended predefined option or configure the available custom fields.
- Click Save Changes to store and apply the new permalink settings.
Selecting an option without saving does not apply the change. When .htaccess is writable, WordPress can update the required rewrite rules automatically. When it is not writable, WordPress displays rules that may need to be handled manually. That is a file and server configuration task, not a reason to replace existing rules without first preserving them.
Immediate verification
After saving, test more than the homepage. Check representative posts and pages, then review category and tag URLs, media URLs and custom post type URLs where the site uses them. A successful dashboard save confirms that the setting was stored, but it does not prove that every URL type works correctly in the current hosting environment.
Separate expected changes from unexpected failures. Content that was intentionally removed or a slug that was deliberately changed is different from a URL that should exist but now returns a 404 response.
Why Pretty Permalinks Produce 404 Errors
A pretty-permalink 404 can indicate a failure in the rewrite path between WordPress and the web server. It is not, by itself, proof that the permalink selection is wrong. The timing of the problem is useful, but diagnosis should also consider the server environment, recent migrations, content changes and plugins that register custom post types.
Server and hosting causes
On Apache-based hosting, missing or inactive mod_rewrite can prevent the server from rewriting pretty URLs as required. An incomplete or non-writable .htaccess configuration can create a similar symptom. If the problem started after a site migration or server move, review what changed in the hosting environment rather than repeatedly changing the WordPress setting.
Shared hosting and Multisite are also documented contexts in which pretty-permalink 404 problems may occur. The appropriate investigation depends on the server stack. Apache guidance should not be treated as a universal procedure for Nginx, because the supplied documentation does not provide a complete Nginx configuration method.
Content and naming conflicts
Not every 404 is a rewrite-rule failure. A deleted item, changed slug or incomplete migration can produce a missing URL even when rewrite rules work correctly. Sites using plugins that register custom post types should also check for naming conflicts between a custom post type and a page. Duplicate names can affect how WordPress resolves the URL.
Use the sequence of events as evidence: identify which content types fail, compare working and failing URLs, and check whether the issue appeared after a structure change, migration or content rename. This avoids treating every 404 as a reason to edit server files.
Refreshing Rewrite Rules: The First Troubleshooting Step
The lowest-risk first action is to open Settings > Permalinks. WordPress documentation states that visiting this screen triggers a flush of rewrite rules, so saving changes is not required solely to perform that refresh. This makes the dashboard an appropriate first checkpoint when previously working pretty permalinks stop resolving.
Dashboard flush
Open the Permalinks screen and then test the affected URLs again. For a persistent custom post type problem, the documented troubleshooting procedure is to select a different permalink structure, save it, select the preferred structure again and save once more. This can refresh the rules associated with the custom post type.
A flush has limits. It cannot restore content that was deleted, correct a changed slug by itself or repair every server configuration issue. If only one content type fails, investigate naming conflicts and the registration context. If many pretty URLs fail, give greater attention to hosting and rewrite configuration.
When Dashboard Fixes Do Not Work
Persistent 404 errors after the dashboard refresh indicate that the investigation should move beyond the setting itself. On Apache-based hosting, check whether mod_rewrite is active and whether the required rules are present in .htaccess. If WordPress could not write the file, it may display the rules that require manual handling.
Recognizing a server-level escalation
Manual editing should be treated cautiously. Preserve the existing .htaccess file, make a reversible backup and use appropriate hosting access. Do not remove existing rules simply to insert new ones. If file permissions, FTP access or web-server configuration are outside your expertise, contact the hosting provider or a qualified administrator.
When the site uses Nginx or another server configuration not covered by the dashboard procedure, consult the hosting provider or the relevant server documentation rather than applying Apache instructions. The same escalation path applies after a migration or server move when the hosting configuration is uncertain.
Post-Change Testing Checklist
Testing should be systematic and representative. Do not limit the review to the front page or one recent post. The purpose is to confirm that the selected structure and rewrite path work across the content types actually used by the site.
Representative URL checks
- Open several representative post URLs.
- Open page URLs from the site’s main navigation.
- Check category and tag URLs.
- Test relevant media URLs.
- Test custom post type URLs when applicable.
- Review internal navigation and important incoming URLs.
- Record unexpected 404 responses separately from content intentionally removed or renamed.
If a URL fails, record its content type, slug and the point at which the failure appeared. Compare that information with the change history: a permalink update, migration, server move, naming conflict or content edit may each lead to a different next step. A successful rewrite refresh is useful evidence, but it is not proof that every address is valid.
WordPress permalink settings are best handled as a deliberate URL policy, not as a casual option to change repeatedly. For a new site, compare the available structures with the content model and choose a stable approach that can be maintained. Before changing a live site, preserve the current state, apply the setting through Settings > Permalinks and test representative URLs. When 404 errors appear, refresh rewrite rules first, then investigate .htaccess, Apache mod_rewrite, hosting, migrations, custom post type conflicts and genuinely missing content. Keep server-file changes reversible and obtain appropriate support when configuration access or expertise is unavailable. Explore our WordPress plugins, WooCommerce extensions, themes and membership plans to find the right tools for your website.