Why am I getting a 404 error for a WordPress page that exists?

Business Tech & Tools

Why am I getting a 404 error for a WordPress page that exists?

The short answer

The page can exist in the dashboard while its public URL, permalink rules, publication state, redirect, cache, or server route is wrong. Start by copying the exact public permalink from WordPress and testing it in a private window.

Do not rebuild the page until you know whether the content is missing or the route to it is broken.

Identify the pattern

Pattern What it suggests
One page returns 404 Wrong slug, parent path, status, redirect, or conflict
All pretty URLs return 404 Permalink or server rewrite problem
Admin sees page but logged-out visitor does not Draft/private status, visibility, cache, or access rule
Old URL fails after slug change Missing redirect
Works on one network only Cache, DNS, or security layer
WordPress 404 page appears Request reached WordPress but no matching public route was found
Host/server 404 appears Request may not be reaching the intended WordPress installation

Save the full URL and a screenshot. The style of the error page can help identify which system produced it.

Check the page itself

Open the page in WordPress and verify:

  • status is Published.
  • visibility is Public.
  • publication date is not scheduled for the future.
  • permalink matches the address you are testing.
  • parent page and language settings are correct.
  • no duplicate page uses the same slug.
  • any membership or access rule is intentional.

Click View Page from the editor instead of typing the address from memory.

Refresh permalink rules safely

If many ordinary pages suddenly return 404, visit Settings > Permalinks, record the current structure, and save it without casually changing the structure. This can refresh WordPress rewrite rules on many setups.

WordPress’s troubleshooting documentation notes that 404 errors with pretty permalinks can involve the web server’s rewrite configuration and may require host assistance. See WordPress’s troubleshooting FAQ.

Do not edit .htaccess or server rules blindly. Preserve the current file and ask the host to confirm the correct configuration for its server.

Check redirects, caches, and conflicts

Search the redirect plugin, host redirects, CDN rules, and SEO plugin for the exact path. A stale redirect can send the page into a missing destination or loop.

Clear the relevant WordPress, host, CDN, and browser caches after fixing the route. Then test logged out.

If one slug consistently fails, try a temporary unique slug on staging. A plugin, custom post type, taxonomy, attachment, or server directory may be claiming the same path.

Preserve search value when the URL changed

If the page intentionally moved, redirect the old URL to the closest true replacement and update internal links. Do not send every missing page to the homepage.

Google explains that permanent redirects signal the destination as the canonical location. See Google’s redirect guidance.

If the page was intentionally removed and has no replacement, an honest 404 or 410 may be correct. A custom helpful 404 page can offer navigation and search without pretending the missing content still exists.

Send support a complete evidence packet

Include the exact failing URL, editor URL, page status, when it last worked, error-page screenshot, permalink setting, recent plugin or server changes, and whether other pages fail. That is enough for a host or developer to begin at the right layer.

Sources and further reading

A free next step

Not sure which business fits you yet?

The free Freedom Path Assessment can help you compare your strengths, schedule, income goals, and preferred way of working before you commit to a business direction.

Take the Freedom Path Assessment Free

Related Questions

Related WAHMN resource

If you want to turn this website task into a service or build a stronger process for your own site, this system walks through the work in more depth. See Website & Landing Page Build System.

← All questions