404 WordPress Error – Complete Guide (2026)

404 WordPress error is one of the most common issues website owners and visitors encounter. Instead of seeing your content, users are greeted with a “404 Not Found” page that can damage user experience and hurt SEO rankings. This 404 WordPress error guide covers 8 proven methods to diagnose and fix this issue permanently. According to WordPress developer documentation, 404 errors in WordPress are often caused by misconfigured permalinks, missing .htaccess files, or broken server rewrite rules. This comprehensive 404 WordPress error guide walks you through every step needed to restore your site’s functionality.

When you search for 404 WordPress error solutions, you are likely dealing with a site where pages that once worked now return “404 Not Found.” According to WordPress support documentation, the most frequent cause is a .htaccess file not being generated when you change permalink settings, preventing WordPress from properly routing requests. This 404 WordPress error guide helps you identify the root cause and apply effective fixes, regardless of your hosting environment.

1. Understanding 404 WordPress Errors

A 404 WordPress error occurs when the server cannot find the requested page or resource. According to WordPress developer documentation, 404 errors in WordPress can be caused by misconfigured permalinks, missing .htaccess files, broken server rewrite rules, or database inconsistencies.

Common causes of 404 WordPress error include:

• Permalink structure changes: Changing the permalink structure without properly updating rewrite rules.
• Missing or corrupted .htaccess file: The .htaccess file contains the rewrite rules that WordPress uses to serve pages.
• Nginx configuration issues: Nginx servers require specific rewrite rules in the site configuration file.
• Plugin conflicts: SEO, caching, or redirection plugins can interfere with rewrite rules.
• Theme issues: Some themes may introduce custom rewrite rules that conflict with WordPress defaults.
• File permission problems: Incorrect file permissions can prevent WordPress from accessing or writing the .htaccess file.
• Database inconsistencies: Missing or corrupted post data in the database can cause 404 errors.

According to WordPress support documentation, if your .htaccess file contains incorrect rules or is missing entirely, WordPress cannot route requests to the correct pages.

2. Refresh Permalinks from Settings

The simplest and most effective fix for a 404 WordPress error is refreshing your permalink settings. According to WordPress support documentation, you can fix 404 errors by going to Settings → Permalinks and clicking “Save Changes” — this regenerates the .htaccess file and refreshes rewrite rules.

Step 1: Log in to your WordPress admin dashboard

Step 2: Navigate to Settings → Permalinks

Step 3: Look at the current permalink structure (it should be set to something like "Post name")

Step 4: Click the "Save Changes" button at the bottom of the page

Step 5: Do not change anything — simply saving will regenerate the .htaccess file and refresh rewrite rules

Step 6: Visit your site and check if the 404 error is resolved

Step 7: If the issue persists, try changing to a different permalink structure, saving, and then switching back to your preferred structure

According to WordPress support, this is the first thing you should try when facing 404 errors after moving a site, changing hosts, or updating WordPress.

Outcome: Permalink rewrite rules are regenerated, and the 404 error is resolved in most cases.

3. Restore or Recreate .htaccess File (Apache)

If you are using an Apache server, the .htaccess file is essential for WordPress permalinks. According to WordPress developer documentation, the .htaccess file contains rewrite rules that map URL requests to WordPress’s index.php file.

Step 1: Connect to your server using FTP (FileZilla) or cPanel File Manager

Step 2: Navigate to the root folder of your WordPress installation (where wp-config.php is located)

Step 3: Look for the .htaccess file (it may be hidden — enable "Show Hidden Files" in your FTP client)

Step 4: If the file exists, rename it to .htaccess_old (as a backup)

Step 5: If the file does not exist, create a new .htaccess file

Step 6: Add the default WordPress rewrite rules to the file:

    # BEGIN WordPress
    RewriteEngine On
    RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
    RewriteBase /
    RewriteRule ^index\.php$ - [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    # END WordPress

Step 7: Save the .htaccess file and ensure its permissions are set to 644

Step 8: Go back to Settings → Permalinks and click "Save Changes" again

Step 9: Clear any caching plugins and browser cache

According to WordPress developer documentation, if the .htaccess file is missing or corrupted, WordPress cannot properly route requests.

Outcome: The .htaccess file is restored, allowing WordPress to route requests correctly.

4. Configure Nginx Server Rewrite Rules

If you are using Nginx instead of Apache, you need to add rewrite rules directly to your Nginx configuration. According to WordPress Nginx documentation, you must add specific location blocks to handle WordPress permalinks.

Step 1: Access your Nginx server configuration file:
    - Usually located at /etc/nginx/sites-available/your-site.conf

Step 2: Look for the location block for your WordPress site

Step 3: Add or ensure the following rewrite rules are present:

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

    location ~ \.php$ {
        include snippets/fastcgi-php.conf;
        fastcgi_pass unix:/var/run/php/php-fpm.sock;
        fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
        include fastcgi_params;
    }

Step 4: Save the configuration file

Step 5: Test the Nginx configuration:
    sudo nginx -t

Step 6: If the test passes, reload Nginx:
    sudo systemctl reload nginx

Step 7: Clear any caching plugins and test your site

According to WordPress Nginx documentation, the try_files directive is essential for WordPress permalinks to work correctly on Nginx.

Outcome: Nginx rewrite rules are configured, enabling WordPress permalinks.

5. Check and Fix File Permissions

Incorrect file permissions can prevent WordPress from writing or reading the .htaccess file, leading to a 404 WordPress error. According to WordPress file permissions documentation, proper permissions are essential for WordPress to function correctly.

Step 1: Connect to your server via FTP or cPanel File Manager

Step 2: Ensure the .htaccess file has permissions set to 644:
    - Right-click the .htaccess file → File Permissions
    - Set to 644 (Owner: Read/Write, Group: Read, Public: Read)

Step 3: Ensure the wp-content folder has permissions set to 755:
    - Right-click wp-content → File Permissions
    - Set to 755 (Owner: Read/Write/Execute, Group: Read/Execute, Public: Read/Execute)

Step 4: Ensure the wp-includes folder has permissions set to 755

Step 5: If you have recently moved the site or changed hosts, verify that file ownership is correct:
    - Files should be owned by the web server user (e.g., www-data, apache, or your hosting user)

Step 6: After fixing permissions, go to Settings → Permalinks and click "Save Changes"

Step 7: Clear any caching plugins and browser cache

According to WordPress documentation, incorrect permissions can prevent WordPress from writing the .htaccess file, causing permalink-related 404 errors.

Outcome: File permissions are corrected, allowing WordPress to manage .htaccess files properly.

6. Disable and Re-enable Plugins

Plugin conflicts are a common cause of 404 WordPress error. According to WordPress plugin troubleshooting documentation, security, SEO, and caching plugins can sometimes modify rewrite rules incorrectly.

Step 1: Log in to your WordPress admin dashboard

Step 2: Navigate to Plugins → Installed Plugins

Step 3: Select all plugins using the checkbox at the top

Step 4: From the "Bulk actions" dropdown, select "Deactivate"

Step 5: Click "Apply" to deactivate all plugins

Step 6: Visit your site and check if the 404 error is resolved:
    - If the error disappears, one of your plugins is the cause

Step 7: Reactivate plugins one by one, testing your site after each activation

Step 8: When you find the plugin that causes the 404 error, keep it deactivated and look for alternatives or contact the plugin developer

Step 9: If you cannot access the admin dashboard, deactivate plugins via FTP:
    - Rename the /wp-content/plugins/ folder to /wp-content/plugins_deactivated/
    - This will deactivate all plugins
    - Rename it back after testing

According to WordPress documentation, disabling plugins is a standard troubleshooting step for identifying conflicts.

Outcome: The problematic plugin is identified and removed, resolving the 404 error.

7. Switch to a Default Theme

Your theme might be causing a 404 WordPress error, especially if it introduces custom rewrite rules or template redirects. According to WordPress theme troubleshooting documentation, switching to a default theme helps isolate whether the issue is theme-related.

Step 1: Log in to your WordPress admin dashboard

Step 2: Navigate to Appearance → Themes

Step 3: Activate a default WordPress theme:
    - Twenty Twenty-Five (or latest default theme)
    - Twenty Twenty-Four
    - Any other default WordPress theme

Step 4: Visit your site and check if the 404 error is resolved:
    - If the error disappears, your original theme is the cause

Step 5: If the error persists with the default theme, the issue is not theme-related

Step 6: If the theme is the cause:
    - Check the theme's functions.php file for custom rewrite rules
    - Contact the theme developer for support
    - Consider switching to a different theme

Step 7: After testing, you can reactivate your original theme

According to WordPress documentation, switching to a default theme helps determine if the issue is caused by your active theme.

Outcome: Theme-related issues are identified and isolated.

8. Set Up Custom 404 Redirects

If you have individual pages that are returning 404 errors, setting up custom redirects can provide a user-friendly experience. According to Redirection plugin documentation, you can use the Redirection plugin to manage 404 errors and set up custom redirects.

Step 1: Install and activate the Redirection plugin:
    - Go to Plugins → Add New
    - Search for "Redirection"
    - Click "Install Now" and then "Activate"

Step 2: Navigate to Tools → Redirection

Step 3: Go to the "404s" tab to see all 404 errors on your site

Step 4: For each 404 error, you can:
    - Redirect the URL to the correct page
    - Redirect to a relevant category or archive page
    - Redirect to the homepage

Step 5: To add a manual redirect:
    - Go to the "Add New" tab
    - Enter the source URL (the broken URL)
    - Enter the target URL (where you want to redirect)
    - Click "Add Redirect"

Step 6: For common 404 issues, you can set up regex patterns to redirect multiple URLs at once

Step 7: Monitor the 404 logs regularly to catch and fix new 404 errors

According to Redirection plugin documentation, proper redirect management improves user experience and preserves SEO value.

Outcome: Individual 404 errors are redirected to relevant pages, improving user experience.

9. Create a Custom 404 Page Template

While creating a custom 404 page doesn’t fix the underlying 404 WordPress error, it improves user experience and keeps visitors on your site. According to WordPress theme developer documentation, you can create a custom 404.php template in your theme.

Step 1: Connect to your server via FTP or cPanel File Manager

Step 2: Navigate to your active theme folder:
    /wp-content/themes/your-theme/

Step 3: Check if a 404.php file already exists:
    - If it exists, you can edit it
    - If not, create a new file called 404.php

Step 4: Add the following basic structure to 404.php:

    
    
    

        
404 - Page Not Found
        
We couldn't find the page you were looking for.
        
Return to Homepage
        
    
    
    

Step 5: Customize the 404 page to match your site's design

Step 6: Add relevant navigation links and a search form to help users find what they need

Step 7: Save the file and test by visiting a broken URL on your site

According to WordPress theme developer documentation, a well-designed 404 page can reduce bounce rates and improve user experience.

Outcome: A custom 404 page improves user experience when visitors encounter broken links.

10. Frequently Asked Questions

What causes a 404 error in WordPress?

According to WordPress developer documentation, 404 errors in WordPress are often caused by misconfigured permalinks, missing .htaccess files, broken server rewrite rules, plugin conflicts, or theme issues.

How do I fix a 404 error in WordPress?

The fastest fix is to go to Settings → Permalinks and click “Save Changes” to regenerate rewrite rules. If that doesn’t work, check your .htaccess file (Apache) or Nginx configuration.

Why does my WordPress site show 404 for all pages except the homepage?

According to WordPress support documentation, this usually happens when rewrite rules are broken, typically due to a missing or corrupted .htaccess file or incorrect server configuration.

How do I restore the .htaccess file in WordPress?

According to WordPress developer documentation, you can restore the .htaccess file by going to Settings → Permalinks and clicking “Save Changes.” If that doesn’t work, manually create the file with the default WordPress rewrite rules.

Can a plugin cause 404 errors in WordPress?

Yes. SEO, caching, and security plugins can modify rewrite rules and cause 404 errors. According to WordPress documentation, disabling all plugins and reactivating them one by one helps identify the problematic plugin.

What is the default .htaccess file for WordPress?

The default .htaccess file contains the WordPress rewrite rules that enable permalinks. It should include the # BEGIN WordPress and # END WordPress markers with the appropriate rewrite rules.

How do I fix 404 errors on Nginx?

According to WordPress Nginx documentation, you need to add the try_files directive to your Nginx configuration: try_files $uri $uri/ /index.php?$args; to handle WordPress permalinks correctly.

What are the correct file permissions for WordPress?

According to WordPress documentation, directories should be 755 and files should be 644. The .htaccess file should have 644 permissions.

How do I create a custom 404 page in WordPress?

According to WordPress theme developer documentation, you can create a 404.php file in your theme folder to customize the 404 error page.

Where can I find more WordPress troubleshooting guides?

Explore our Internet & Online Services Hub, Software and Web Apps Hub, and guides on clearing cache and permission errors.

11. Conclusion

404 WordPress error can be frustrating for site owners and visitors alike, but most cases are fixable with systematic troubleshooting. This guide has covered 8 proven methods: refreshing permalinks, restoring .htaccess, configuring Nginx, fixing file permissions, disabling plugins, switching themes, setting up redirects, and creating custom 404 pages. According to WordPress developer documentation, the most common fix is simply saving your permalink settings, which regenerates the .htaccess file and refreshes rewrite rules. According to WordPress support documentation, if the .htaccess file is missing or corrupted, WordPress cannot properly route requests.

Start with the simplest fix — refreshing permalinks — and escalate to more advanced solutions only if needed. For ongoing WordPress and web troubleshooting, explore our Internet & Online Services Hub, Software and Web Apps Hub, and guides on clearing cache, permission errors, and Gmail loading issues.

With the right approach from this 404 WordPress error guide, you can restore your site’s functionality and provide a seamless experience for your visitors.