This Page Doesn’t Exist Errors on WordPress: Common Causes and How to Fix Them

A blank “this page doesn’t exist” or “page not found” error on a WordPress site can look like a serious failure, but most of the time it comes down to one of six specific things. We’ve listed them below in the order it makes sense to check them, each with its fix. There’s also a section at the end on when it’s sensible to hand the diagnosis over to someone with more time or more experience.

The six most common causes

In almost every case, a “page doesn’t exist” error on WordPress traces back to one of these:

1. The permalink structure has broken or been changed.
2. A third-party widget or plugin is silently failing.
3. Theme file corruption or a missing template file.
4. DNS or hosting-level redirect misconfiguration.
5. A WordPress core update conflict.
6. Server-level rewrite rules in .htaccess or the nginx config.

Cause 1: Permalink structure has changed or broken

Permalink issues are the most common cause by a clear margin. WordPress stores a “permalink structure” that tells it how to build URLs, and if that structure has been changed, if the .htaccess file has been overwritten, or if something in the database options table has been touched, every URL on the site can suddenly start returning “page doesn’t exist” even though the underlying content is still there.

The fix in most cases is to log into wp-admin, navigate to Settings → Permalinks, and click Save Changes without altering anything, which regenerates the rewrite rules. If wp-admin is not accessible, the same fix can be applied manually by checking that .htaccess (on Apache or LiteSpeed hosting) contains the standard WordPress rewrite block. This step usually takes two to five minutes.

Cause 2: A third-party widget or plugin is silently failing

This one is easy to miss, even for a business owner who’s comfortable with the technical side. A widget or plugin that loads external content, for example an event booking calendar or a live stock feed, can fail silently and take a page down without any obvious PHP error: the page loads, but the widget won’t render, and sometimes a message reading “this page doesn’t exist” appears in place of the widget content.

Work out which widgets or plugins are active on the broken page, then temporarily disable each one in turn and reload the page. When the error goes away, the plugin you just disabled is almost certainly the cause. Usually the answer is to update it to the current version, replace it with an alternative, or roll it back to the previous version if the current one broke.

Cause 3: Theme file corruption or a missing template file

WordPress uses PHP template files to render pages, so if a required template such as single.php for blog posts or page.php for standard pages is missing or corrupted, WordPress will either fall back to a generic template or, when no fallback exists, throw an error. Checking the theme files via SFTP is usually enough to confirm whether anything is missing or truncated, and the fix is to reinstall the theme from a clean copy or, on a custom-built theme, to restore the affected file from your last known-good backup.

Cause 4: DNS or hosting-level redirect

Sometimes the “page doesn’t exist” message is coming from the DNS layer or a hosting-level redirect rule rather than from WordPress. If the domain’s A record has been changed, a CDN such as Cloudflare is misconfigured, or a redirect at the hosting level is pointing to a URL that no longer exists, WordPress never even receives the request. Use a DNS lookup tool to confirm the domain is pointing at the correct IP, then log into the hosting control panel and look for any URL redirect rules that could be intercepting traffic. If Cloudflare sits in front of the site, check Page Rules and Bulk Redirects as well.

Cause 5: WordPress core update conflict

When WordPress core updates, plugins or themes that were written for an earlier version can suddenly break, and the most visible symptom is often a missing page or a broken URL structure. This is more likely if several minor versions have been skipped and the site has jumped forward in one large update rather than being kept current. The fix is to identify which plugins or themes have not been updated since before the last WordPress core update, update them if patches exist, and roll WordPress core back to the previous minor version if the plugin developer has not yet caught up. Our guide to recovering from a WordPress update that broke your site covers the process in more detail.

Cause 6: Server-level rewrite rules

On Apache and LiteSpeed hosting, .htaccess controls URL rewriting before WordPress is even called, and on nginx-based hosts the nginx config does the same job. If a developer or the hosting provider changes those files, WordPress URLs can suddenly return “page doesn’t exist” even though the WordPress installation itself is fine. Back up the current server config file, then restore the standard WordPress rewrite block. If you can’t do that yourself, the support team on most managed hosts can do it in a few minutes.

A diagnostic order that works every time

If you do not know which of the six causes you are looking at, working through them in the following order rules out entire categories. First, save permalinks in wp-admin. Second, load the broken page in a private browsing window while logged out. Third, check whether the error appears on other pages or only on that one. If it is limited to a single page, look at which plugins render content on that page and disable them one at a time; if it appears on multiple pages, check DNS and hosting-level redirects next. If DNS is fine, check the theme files and .htaccess. If none of those surface the cause, the last thing worth checking is the server error log. If step seven turns up something you do not understand, that is usually the point to stop and get help, because reading PHP error stack traces and knowing which errors matter is a specialist skill.

When to stop DIY and call an expert

DIY diagnosis is realistic if you have wp-admin access, SFTP or SSH access to the file system, and the ability to read a server log. If any of those are missing, or you’ve worked through the six causes above without finding the problem, it’s usually sensible to get professional help. Carrying on changing things without a clear plan tends to introduce new errors, and it can leave the site much harder to fix afterwards.

One recent example from our own case work involved a stark “this page doesn’t exist” error on a UK client’s homepage that was eventually traced to a single third-party widget failing silently because of a change in a supplier’s API. The full detail is written up in this case study.