WordPress 404 Permalink Checklist: Routes, Rewrites and Real Missing Pages

Check whether a WordPress 404 is a missing page or a routing failure before changing permalinks. A deleted article, a stale internal link and a server rewrite problem need different corrections. Treating them all as a reason to change the URL structure can create a much larger migration.

Define the affected pattern

Save several failing URLs and a working comparison. Check whether the homepage works, whether only posts fail and whether the problem is limited to a custom post type or one directory. Record when the problem started and any hosting or plugin change nearby.

Confirm that the content exists, is published and has the expected slug. Look at the actual permalink shown in the editor. A draft or renamed page may be unavailable at the old address even when its content still exists.

Check links before server settings

Compare the failing address with the published permalink character by character. Look for an old path, spelling difference or stale menu link. If the correct address works, fix the referring link and decide whether the old URL needs a relevant redirect.

If many valid pretty permalinks fail after a move, ask the maintainer to inspect rewrite handling. WordPress’s common-error documentation discusses permalink and custom-post-type 404 cases. Use the site’s current server configuration rather than pasting a generic Apache snippet into an Nginx environment.

Refresh routing deliberately

A maintainer may refresh rewrite rules through WordPress permalink settings when appropriate. Preserve the existing structure; refreshing rules and choosing a new structure are different actions. Ask the host whether the server needs an additional supported change.

For custom post types, check the plugin or theme registering the routes and any recent changes to its slug or availability. Repeatedly saving settings will not restore a disabled component or correct missing content. Test one hypothesis and record what changed.

Handle genuinely missing content

If a page has a relevant replacement, use an approved redirect to that destination and update internal links. If there is no suitable replacement, a real missing-page response can be correct. Sending every removed page to the homepage does not make the original content available.

Use the redirect mapping checklist for moved pages. Keep your custom error page helpful, with clear navigation, while preserving the appropriate response behavior; an attractive error screen alone does not establish that the server reports a genuine 404.

Verify public routes after repair

Test normal posts, relevant custom post types and representative pagination or archive routes. Use a logged-out browser as well as administrator access. Check key internal links and any sitemap entries that point to the affected content.

Retain the failure examples and the corrected configuration in the change record. Close the task when the intended routes work and legitimately absent content is handled accurately. Do not label every 404 as an SEO emergency or assume a sitemap entry can repair the routing.

Use a known published page as a routing comparison

If a hypothetical published page’s intended friendly URL returns 404, confirm the page’s current permalink and status before editing server rules. If the same content is reachable through another supported route, give that comparison to the maintainer as evidence. If the content genuinely moved, use redirect mapping rather than repeatedly refreshing permalink settings for a removed URL.

Sources and scope

Official documentation checked October 6, 2026: WordPress: Common errors; Google: Crawling errors. This is HRL’s general diagnostic workflow, not a diagnosis of your website. Server and security changes belong with the authorized administrator and the host’s supported procedures.

Related guides

Investigate plugin routing changes · Check sitemap URLs · Plan hosting migration