---
title: "WordPress 404 Errors: Causes and Fixes by Type"
url: https://hostmy.blog/wordpress-404-errors/
date: 2026-10-30
modified: 2026-10-30
lang: en
author: "Aditya Sharma"
description: "The kinds of 404 error a WordPress site produces, which ones cost traffic and which to ignore, what Google says a 404 does, and how to find and fix them."
categories:
  - "WordPress"
image: https://hostmy.blog/wp-content/uploads/2026/10/hmb-card-2667-1024x538.jpg
word_count: 1427
---

# WordPress 404 Errors: Causes and Fixes by Type

A 404 means the server could not find what was asked for. On a WordPress site it is the most ordinary error there is, and most of the ones you will see are harmless. A few cost you traffic, and telling the two groups apart is the whole job of dealing with WordPress 404 errors.

This post sorts them by type. For each type it says what causes it, whether it matters, and what to do. It leans on what Google says a 404 does to a page. The fear around the error is out of proportion to its effect, and the cases that do matter are not the ones people usually worry about.

![Numbered outline of this post, WordPress 404 Errors: Causes and Fixes by Type: 1 What Google says a 404 does; 2 A moved or renamed post; 3 A deleted page; 4 Missing files; 5 The soft 404; 6 What to ignore.](https://hostmy.blog/wp-content/uploads/2026/10/hmb-diagram-2667.png)The route through this post.

## What Google says a 404 does

Google's documentation on HTTP status codes is plain about this. URLs that are already indexed and return a 4xx status are removed from the index, and it treats a 410 the same as a 404. Newly encountered 404 pages are not processed, and the crawling frequency gradually decreases. The page gives no timeframe for either. It also describes a soft 404, which Search Console reports when a page returns a success status but its content suggests an error, such as an empty page or an error message. You can read it in Google's [guide to HTTP status codes and network errors](https://developers.google.com/search/docs/crawling-indexing/http-network-errors).

Two things follow. A 404 on a page that never mattered costs you nothing, and Google stops asking for it. And a 404 on a page that had traffic removes that page from search, so the question for each error is whether anyone was using the address.

## The types, sorted by whether they matter

| Type | What causes it | Does it matter? |
| ---- | -------------- | --------------- |
| A moved or renamed post | A slug was edited, or a category or folder changed, with no redirect | Yes, if the old address had traffic or links |
| A deleted page | Content was removed on purpose | Only if people still arrive at it |
| Broken permalinks | Pretty permalinks stopped working across the site | Yes, and it affects every post |
| Missing files | An image, stylesheet or script moved after an update | Yes, because pages look or work wrong |
| A soft 404 | The error page returns a 200 status | Yes, because search engines see an empty page as real |
| Bots probing | Scanners ask for login pages and files you never had | No, though a spike is worth noticing |
| Typos in outside links | Someone linked to a wrong address | Rarely, and a redirect can recover it |

The first four are the ones to chase. The last two are background noise, and the fifth is a technical fault that is easy to miss, so it gets its own section below.

## A moved or renamed post

The most common costly 404 is one you created yourself. Someone edits a post's slug in the editor to tidy it, and the old address stops working. Anything that linked to it, including search results, now lands on an error page. WordPress core can redirect an old post slug in simple cases, but not reliably for a moved folder, a changed category base or a page that is not a post.

The fix is a permanent redirect from the old address to the new one, and where to put it is the subject of [WordPress redirect plugin or server rule: which to use](/wordpress-redirect-plugin-or-server-rule/). Prevent the next one by changing slugs only when you have to, and adding the redirect in the same sitting. If the cause is a whole new permalink structure, [how to safely change WordPress permalinks](/change-wordpress-permalinks/) covers it.

## A deleted page

When you remove a page on purpose, a 404 is the honest answer, and a 410 says the same thing more firmly. Google treats them alike. The decision is only whether to redirect. If the page has a close replacement, redirect to it. If it has none, let the address return an error, and do not send it to the homepage. [Content pruning for AI: what to delete, redirect or refresh](/content-pruning-for-ai/) sets out how to choose.

## Broken permalinks across the whole site

If every post returns a 404 but the homepage loads, the rewrite rules have stopped working. This happens after a move to a new host, a change of web server, or an edit to the server configuration. In the dashboard, open the permalink settings and save without changing anything, which makes WordPress rebuild its rules. If that does not fix it, the server is not passing requests through to WordPress, and the cause is in the server configuration or the host's rewrite settings. This is the one 404 that is a site-wide emergency, and it is worth testing right after any move.

## Missing files

A 404 on an image, stylesheet or script rarely shows up as an error page. It shows up as a page that looks broken. A plugin update that changes an asset path, a cache that served an old reference, or images missing after an import can each cause it. The posts that suffer are often old ones nobody visits. [What a WordPress maintenance month actually contains](/wordpress-maintenance-service/) lists a 404 review as a monthly check for this reason. It finds the stylesheet that has been returning an error on every page for a week.

## The soft 404

A soft 404 is the one that surprises people. The page says it was not found, and the server says everything is fine. Test your own error page, because some themes and plugins return a 200 status for it. This command asks for an address that cannot exist and prints the status line.

`curl -sI https://yourdomain.com/this-page-does-not-exist-12345/ | head -1`

You want to see a 404. A 200 means your error page is reporting success, and Search Console may flag those addresses as soft 404s. The fix is in the theme's 404 template or in the plugin that replaces it, so that the status code is sent with the page.

## Finding the 404s you have

There are three places to look, and each shows something different. Search Console's Page indexing report lists URLs Google found that returned a 404. Your SEO plugin or a redirect plugin may keep a log of 404s on your own site. And the server's access log records every one, including the ones from bots. This reads the log and prints the addresses that returned 404 most often.

`grep ' 404 ' /var/log/nginx/access.log | awk '{print $7}' | sort | uniq -c | sort -rn | head -20`

The log path varies, as [reading your server log by hand](/read-server-log-ai-crawlers/) explains, and the field number assumes the common log format. Look at the top of the list. Addresses ending in .php that you do not have are bots probing. Addresses that look like your content are the ones to redirect or restore.

## What to ignore

A scanner asking for /wp-login.php variants, backup files or an admin panel you do not run produces a steady trickle of 404s, and the right response is nothing. Blocking them one by one is a waste of time. What deserves attention is a sudden change: a spike in one pattern, or a rise in errors on addresses that look like your real posts. [What breaks on a WordPress site when nobody is watching](/what-breaks-when-nobody-is-watching/) describes that pattern.

If pages that you want are being reported as not indexed, that is a different problem from a 404, and [crawled, currently not indexed](/crawled-currently-not-indexed-wordpress/) covers it. And a sitemap that lists addresses returning 404 is worth fixing at the source, which [WordPress sitemap: where it is and how to fix it](/wordpress-sitemap/) explains.

## A routine for 404s

`1. Open the Page indexing report once a month and note any new 404 URLs.
2. Check whether each address ever had traffic or links.
3. Redirect the ones that did, to the closest replacement.
4. Leave the rest as 404s.
5. Test your error page returns a real 404 status.
6. Check the access log for spikes after any update or move.`

The routine takes about fifteen minutes. The point is to catch a changed address before the traffic it carried is gone, because the cost of a 404 is mostly the traffic you stopped getting and did not notice.

## Where Host My Blog fits

On the blogs we look after, 404 and redirect review is a standing part of the month. It is where quiet losses such as a changed slug or a broken asset get caught. If you would rather have someone read the log and fix the real ones, [our care for bloggers](/for-bloggers/) includes it.

If you opened your 404 log today, how many of the top ten addresses would be pages you once cared about?