404 Not Found: restore a missing page

What does this mean?

A 404 means the requested resource was not found. The rest of the website may work normally. A deleted page, mistyped address, moved article or broken permalink can produce the same visible error, so the first task is to establish which URL should exist.

What should I check first?

Copy the exact failing address, including capitals, trailing slash and any query string. Open the homepage and follow its own navigation to the resource. If the page works through navigation, compare those addresses character by character. A search result can keep linking to an old address after a move.

How can I diagnose the cause?

Check whether the page still exists in your CMS and is published rather than draft or private. For a static site, verify that the uploaded folder contains its index file. If only WordPress permalinks fail, review the permalink settings and the host’s rewrite support; do not repeatedly replace all server rules.

How do I fix it safely?

If the resource moved, add a permanent redirect from the old address to the equivalent new page. Preserve useful query parameters where appropriate. Do not redirect every missing URL to the homepage: visitors need an accurate answer and a meaningful 404. If it was deleted intentionally, keep a useful 404 or use 410 where your publishing system supports that decision.

Verify the fix and know when to contact your provider

Retest the exact old URL, the new destination and one unrelated page. Update navigation, contextual links and the sitemap. Ask the host for help when a real uploaded file still returns 404 or all rewritten routes fail; include the path, file location and a redacted copy of the relevant routing rules.

Work through these checks in order

1. Open the working page through the site menu and copy that address. Compare it with the failing address, including letter case and any filename. This separates a stale link from a missing published page.
2. If a static page should exist at /guides/example/, verify that the deployed folder contains index.html. For a CMS page, confirm publication status and its current permalink in the editor.
3. If the page moved, test its old URL after a targeted redirect. It should reach the equivalent replacement, not an unrelated homepage. Then repair the link where visitors originally encountered it.

Which tool can help?

HTTP status checker · URL encoder / decoder

DNS tools show one resolver’s public answers. Record explainers do not authenticate a message, and calculators do not monitor a server. Use the evidence alongside your provider’s logs.