WordPress Sitemap, Feed & Media 404 Error Fix

Flush WordPress Permalinks

This is the first and often simplest step to resolve rewrite rule issues. WordPress needs to regenerate its internal rewrite rules. Even if your posts and pages are working, flushing permalinks can resolve specific issues with sitemaps and feeds.

• Navigate to your WordPress admin dashboard.
• Go to Settings → Permalinks.
• Without making any changes, simply click the Save Changes button. This action forces WordPress to flush and regenerate the .htaccess file (if you're on Apache) and update its internal rewrite rules.

✓ ~1 minute. Safe to perform.

Inspect and Recreate .htaccess File

A damaged or missing .htaccess file is a primary suspect for wordpress sitemap 404 error and wordpress feed 404 error. You need to access your site's root directory via FTP/SFTP or your hosting file manager.

• Connect to your server using an FTP client (e.g., FileZilla) or your hosting control panel's file manager.
• Navigate to the root directory of your WordPress installation (where wp-config.php is located).
• Look for a file named .htaccess. If it's missing, create a new file with that name.
• If it exists, temporarily rename it to something like .htaccess_old.
• Go back to WordPress Settings → Permalinks and click Save Changes again. This should generate a fresh .htaccess file.
• Verify the contents of the new .htaccess file. It should typically look like this:

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

If your wordpress xml sitemap not found 404 persists, check if any SEO plugin (like Yoast or Rank Math) has added its own sitemap rules to .htaccess. Ensure they are correctly formatted.

✓ ~5-10 minutes. Renaming is safe; direct editing requires caution.

Verify File and Directory Permissions for Media

If you're facing wordpress 404 on media files or wordpress uploaded images returning 404, incorrect permissions are a prime suspect. The web server needs read access to serve these files.

• Using FTP/SFTP or your file manager, navigate to the wp-content/uploads/ directory.
• Check the permissions for the uploads directory and its subdirectories (e.g., 2023/, 01/). Directories should generally be 755.
• Check the permissions for individual media files within these directories (e.g., image.jpg). Files should generally be 644.
• If permissions are incorrect, change them. For directories, apply 755 recursively. For files, apply 644 recursively within the uploads directory.

✓ ~5-15 minutes. Incorrect permissions can cause security issues or prevent files from being served.

Diagnose Plugin Conflicts

Plugins, especially caching, security, or SEO plugins, can sometimes interfere with rewrite rules or file serving. This is particularly relevant if your wordpress sitemap 404 error appeared after installing a new plugin.

• Access your WordPress admin dashboard and go to Plugins → Installed Plugins.
• Deactivate all plugins.
• Check if your sitemaps, feeds, or media files are now accessible.
• If the issue is resolved, reactivate your plugins one by one, checking after each activation until the 404 returns. This will identify the conflicting plugin.
• Once identified, check the plugin's settings for any rewrite or file-serving options, or consider replacing it.

✓ ~10-30 minutes, depending on the number of plugins. Safe, but your site will temporarily lose plugin functionality.

Verify Server Configuration (Apache or Nginx)

If the above steps haven't worked, the problem might be at the web server level. This requires access to your server's configuration files (e.g., httpd.conf for Apache, nginx.conf for Nginx).

• For Apache: Ensure mod_rewrite is enabled. You can often check this via SSH with apache2ctl -M or httpd -M. Also, verify that your virtual host or directory configuration for your WordPress site includes AllowOverride All (or at least AllowOverride FileInfo) to allow .htaccess files to function.
• For Nginx: Nginx does not use .htaccess. All rewrite rules must be in your Nginx server block configuration. Ensure your Nginx configuration for your domain includes the standard WordPress rewrite rules:

  location / {
      try_files $uri $uri/ /index.php?$args;
  }
  # For sitemaps (if not handled by a plugin directly)
  location ~* /(sitemap_index\.xml|[a-z0-9_-]+-sitemap\.xml)$ {
      try_files $uri $uri/ /index.php?$args;
  }

  If you're using a specific SEO plugin like Yoast, it might generate sitemaps that need direct Nginx rules. Consult your plugin's documentation.
• After making any changes to server configuration, remember to restart your web server (e.g., sudo systemctl restart apache2 or sudo systemctl restart nginx).

✓ ~15-45 minutes. Requires root/sudo access and familiarity with server administration. Incorrect changes can break your entire site.

Check WordPress Site URL in Database

Especially after a migration or domain change, incorrect siteurl or home options in your WordPress database can cause pathing issues for all assets, including wordpress 404 on media files.

• Access your database using phpMyAdmin or a similar tool.
• Find your wp_options table (wp_ might be a different prefix).
• Look for option_name entries: siteurl and home.
• Ensure their option_value matches your current domain exactly, including http:// or https://.
• If they are incorrect, update them. For example:

  UPDATE wp_options SET option_value = 'https://yourdomain.com' WHERE option_name IN ('siteurl', 'home');

This is a common fix for WordPress 404 After Migration issues as well.

✓ ~5-10 minutes. Make a database backup before making direct changes.