WordPress Pages Giving 404 Error? Here is the 2-Minute Fix

One of the most common and confusing issues WordPress site owners encounter is when the homepage loads perfectly, but clicking on any blog post, page, or product link results in a 404 Not Found Error.

This issue usually happens due to a desynchronized permalink structure or a corrupted .htaccess file. The good news is that you don’t need coding knowledge to fix it.

In this step-by-step guide, we will walk you through the reasons why WordPress permalink 404 errors happen and how to resolve them quickly.

What Causes the WordPress Permalinks 404 Error?

The 404 error occurs when your web server cannot find the page requested by the URL. In WordPress, common causes include:

1. Unsaved Permalinks Settings: Rules inside WordPress get out of sync after updating plugins, themes, or core files.
2. Corrupted .htaccess File: The file responsible for rewrite rules on Apache/LiteSpeed servers is missing or lacks proper write permissions.
3. Domain Migration or SSL Installation: Moving your site to a new domain, staging site, or enabling HTTPS without updating rewrite rules.
4. Plugin or Theme Conflicts: A plugin (such as a custom post type or redirection plugin) breaking rewrite rules.
5. Nginx Rewrite Configuration Issues: On Nginx servers, missing directive rules inside the server block configuration.

How to Fix WordPress Permalinks 404 Error (Step-by-Step)

Method 1: Reset WordPress Permalinks (The 2-Minute Fix)

In 90% of cases, simply saving your permalink settings forces WordPress to flush and regenerate rewrite rules.

1. Log into your WordPress Admin Dashboard.
2. Go to Settings > Permalinks.
3. Scroll down without making any changes and click Save Changes.
4. (Optional) If it still fails, select a different structure (e.g., switch from Post name to Plain), click Save Changes, then switch back to Post name and click Save Changes again.
5. Open your site in an incognito window and check if inner pages load properly.

Method 2: Regenerate the .htaccess File

If saving permalinks didn’t work, your .htaccess file might be corrupted or write-protected.

How to replace .htaccess via cPanel / FTP:

1. Connect to your site using cPanel File Manager or an FTP Client (like FileZilla).
2. Locate the root directory (usually public_html).
3. Find the .htaccess file. (Note: Make sure “Show Hidden Files” is enabled).
4. Rename .htaccess to .htaccess_old.
5. Create a new file named .htaccess in the same directory.
6. Paste the following default WordPress rewrite code into it:

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress

Method 3: Fix File Permissions for .htaccess

If WordPress doesn’t have write access to your .htaccess file, saving settings from the dashboard won’t update rewrite rules.

1. Right-click the .htaccess file in cPanel File Manager or FTP.
2. Select File Permissions.
3. Set the numeric value to 644 or 640.
4. Return to WordPress Dashboard > Settings > Permalinks and click Save Changes.

Method 4: Enable mod_rewrite on Apache Server

If you are running a local server environment (like XAMPP, WAMP, or MAMP) or a VPS server, Apache’s mod_rewrite module might be disabled.

1. Open your Apache configuration file (httpd.conf).
2. Search for the line: #LoadModule rewrite_module modules/mod_rewrite.so
3. Remove the # at the beginning to uncomment it. AllowOverride All
4. Search for AllowOverride None under your site directory and change it to:
5. Restart your Apache server.

Method 5: Configure Nginx Rewrite Rules

Nginx servers do not use .htaccess files. Instead, rewrite rules must be added directly to the server configuration file (nginx.conf).

Ensure your Nginx server block contains the following directive inside the location / block:

location / {
    try_files $uri $uri/ /index.php?$args;
}

After adding this rule, reload Nginx using sudo systemctl reload nginx.

Conclusion

A WordPress Permalinks 404 Error can be intimidating, but it is almost always solved by flushing permalink settings or restoring a default .htaccess file. By following these steps sequentially, you can bring your site’s inner pages and posts back online without losing traffic or ranking positions.