WordPress: How to Redirect 404 to Home Page in .htaccess

In 2026, maintaining a seamless user experience on your mybox server is vital. When a visitor hits a “Page Not Found” error, redirecting them to the homepage can keep them on your site. However, doing this via the .htaccess file requires precision to avoid breaking WordPress core functions like the REST API or the admin dashboard.

Requirements and Backup

Before touching your configuration, perform these safety steps:

• Backup: Download your current .htaccess file via FTP.
• Server Check: Ensure your server is running Apache (Standard on mybox) and that mod_rewrite is active.
• Text Editor: Use a plain text editor (like Notepad++ or VS Code) to avoid adding hidden formatting characters.

Where to Insert Rules in .htaccess

WordPress automatically manages the code between # BEGIN WordPress and # END WordPress. Never place your custom rules inside this block, as WordPress will overwrite them during updates.

Place your code at the very top of the file:

Apache

# CUSTOM 404 REDIRECT START
<IfModule mod_rewrite.c>
RewriteEngine On
# Your rules go here
</IfModule>
# CUSTOM 404 REDIRECT END

# BEGIN WordPress
... existing code ...
# END WordPress

The Safest Redirect Script (with Exceptions)

A “blind” redirect can break your site’s ability to log in or update. Use this version, which includes 2026-standard exceptions for the WordPress REST API, Sitemaps, and Admin panels:

Apache

<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /

# 1. Do not redirect the homepage itself (prevents loops)
RewriteCond %{REQUEST_URI} !^/$

# 2. Exclude Admin and Login areas
RewriteCond %{REQUEST_URI} !^/wp-admin [NC]
RewriteCond %{REQUEST_URI} !^/wp-login\.php [NC]

# 3. Exclude REST API and Feeds (Critical for blocks/plugins)
RewriteCond %{REQUEST_URI} !^/wp-json [NC]
RewriteCond %{REQUEST_URI} !/feed/?$ [NC]

# 4. Exclude Sitemap and Robots.txt (Crucial for SEO)
RewriteCond %{REQUEST_URI} !sitemap [NC]
RewriteCond %{REQUEST_URI} !robots\.txt [NC]

# 5. Only redirect if the file or directory actually DOES NOT exist
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d

# 6. Perform the 301 (Permanent) Redirect to homepage
RewriteRule ^.+$ / [R=301,L]
</IfModule>

301 vs. 302: Which Should You Use?

• 301 (Permanent): Tells Google the old page is gone forever and the homepage is the new destination. Use this once you are sure the code works.
• 302 (Temporary): Use this for testing. Browsers won’t “cache” a 302, so if you make a mistake, it’s easier to fix without clearing your visitors’ browser history.

SEO Note and Best Practices

While a 404-to-home redirect is “clean,” Google often treats these as “Soft 404s.” This means Google knows the page is missing and may not pass the “SEO juice” of the old link to your homepage.

Better Alternative: If you deleted a specific page (e.g., old-product), it is better to redirect that specific URL to a similar current product rather than the generic homepage. Use a 404-to-home redirect only as a “catch-all” for random mistyped URLs.

Summary

Redirecting 404s via .htaccess is the fastest method because it happens at the server level before WordPress even loads. By using the “Exceptions” version of the script, you ensure your site remains fast and functional while keeping lost visitors engaged on your homepage.