You see a 404 File Not Found error when you try to open a SharePoint page that was working yesterday. The page still exists in the site pages library, but SharePoint returns a 404 error instead of displaying the content. This problem occurs because the page reference in the navigation or a direct link points to a path that SharePoint can no longer resolve. This article explains why a valid page triggers a 404 error and provides the exact steps to fix the broken link and restore access.
Key Takeaways: Fixing a 404 Error for an Existing SharePoint Page
- SharePoint site pages library > Check Out and Republish: Resolves 404 errors caused by corrupted page metadata or broken version history.
- SharePoint admin center > Site collection > Navigation settings: Corrects 404 errors from orphaned navigation links that point to deleted or moved pages.
- SharePoint site > Site Pages > Restore from Recycle Bin: Fixes 404 errors when the page was accidentally deleted but the link still exists.
Why a Valid Page Returns a 404 Error in SharePoint
The 404 File Not Found error in SharePoint does not always mean the page file is missing. The error can appear when the page exists in the site pages library but SharePoint cannot resolve the URL correctly. This happens for three primary reasons:
Orphaned Navigation Links
When a page is moved or deleted, the navigation link that pointed to it still exists. SharePoint tries to follow the old URL, finds no matching page, and returns a 404 error. The link is orphaned: the page is gone, but the link remains active in the navigation menu.
Corrupted Page Metadata or Version History
A page can become corrupted if its metadata, such as the file name or content type, is altered outside the normal editing workflow. Version history can also break if a page is overwritten with an incomplete version. SharePoint then fails to render the page and shows a 404 error instead.
Broken Permissions or Inherited Security Settings
If the page inherits permissions from a parent site or folder and that parent's permissions are changed or removed, the page becomes inaccessible. Users see a 404 error even though the page file exists. This is a permission issue, not a missing file issue.
Steps to Diagnose and Fix the 404 Error for an Existing Page
Follow these steps in order. Start with the simplest fix and move to more advanced steps only if the error persists.
- Verify the Page Exists in the Site Pages Library
Open the site pages library by navigating to Site Contents > Site Pages. Look for the page file. If the page is not listed, check the site recycle bin by clicking Recycle Bin in the left navigation. If the page is in the recycle bin, restore it. If the page is not in the recycle bin, check the second-stage recycle bin in the SharePoint admin center. - Check the Page URL in the Browser
Copy the page URL from the navigation link or the link that returns the 404 error. Open a new browser tab and paste the URL. If the URL contains a space or special character, replace spaces with %20. If the URL ends with a file extension like .aspx, verify that the file name matches exactly. - Check Out and Republish the Page
In the site pages library, select the page. Click the ellipsis (three dots) and choose Check Out. After the page is checked out, click Check In. Select Publish Major Version. This resets the page metadata and version history, which often resolves 404 errors caused by corruption. - Remove and Recreate the Navigation Link
If the page works when you open it directly from the site pages library but fails from a navigation link, the link is orphaned. Go to Site Settings > Navigation. Find the link that points to the broken page. Delete the link. Then add a new link that points to the correct page URL. Click OK to save changes. - Reset Page Permissions to Inherit from Parent
If the page is accessible only to certain users but not others, permissions may be broken. In the site pages library, select the page. Click the ellipsis and choose Manage Access. Click Advanced Permissions Settings. Click Inherit Permissions. This breaks the unique permissions and reverts to the site's default permissions. After inheriting, test the page. - Clear Browser Cache and Cookies
An outdated browser cache can cause a 404 error if the cached version of the page is corrupt. In Chrome, click the three dots > More tools > Clear browsing data. Select Cached images and files and Cookies and other site data. Click Clear data. In Edge, click the three dots > Settings > Privacy, search, and services > Choose what to clear. Select Cached images and files and Cookies and other site data. Click Clear now.
If SharePoint Still Shows a 404 Error After the Main Fix
The page works for some users but not others
This indicates a permissions issue. Go to the page library, select the page, and click Manage Access. Verify that the user or group has at least Read permission. If the page inherits permissions from a folder, check the folder's permissions. If the page has unique permissions, grant the user direct access.
The page works in one browser but not another
Clear the browser cache and cookies in the problematic browser. If the error persists, disable browser extensions that modify page content, such as ad blockers or script blockers. Test the page in an InPrivate or Incognito window.
The 404 error appears only on mobile devices
SharePoint pages have separate mobile views. If the page was created with a modern template that does not support mobile rendering, SharePoint shows a 404 error on mobile. Edit the page and ensure the mobile layout is enabled. Go to Page settings > Layout and select the mobile-friendly option. Republish the page.
The page was restored from the recycle bin but still shows 404
A restored page may retain a corrupted version history. Check out the page, then check it in without making changes. This creates a fresh version. Then publish the page as a major version. If the error continues, delete the page and restore it again from the recycle bin.
Page URL vs Navigation Link: Key Differences When Troubleshooting 404 Errors
| Item | Page URL (direct link) | Navigation Link (menu or quick launch) |
|---|---|---|
| Source | Site pages library file path | Site settings > Navigation |
| Common 404 cause | Page deleted, moved, or corrupted | Orphaned link pointing to old or deleted page |
| Fix method | Restore or republish the page | Delete and recreate the navigation link |
| Permission impact | Direct permission changes affect access | Link itself has no permissions; the target page's permissions apply |
| Cache dependency | Browser cache can cause false 404 | Navigation cache in the site can cause stale links |
When you see a 404 error, first determine whether the error occurs when you use the direct page URL or only when you use a navigation link. This tells you whether the problem is with the page itself or with the link that points to it.
You can now identify whether the 404 error comes from an orphaned navigation link, a corrupted page, or a permissions issue. Start by checking the page URL directly. If the page works from the library but not from the menu, delete and recreate the navigation link. If the page itself fails, check it out and republish it. For persistent errors after a restore, always check the page's version history and permissions inheritance.