"Not found (404)": what it means and how to fix it
The page shows a 404 Not Found error.
By Bruno Amorim · ·
What it means
Google asked for the page, and the server said it does not exist.
The fix, in short: If the page moved, add a 301 redirect to the new address. If it is gone, take it out of your sitemap and your links.
Which of your pages have this problem? Find out for free.
Get my free reportCommon causes
- The page was deleted or moved, with no redirect.
- A typo in a link or in your sitemap.
How to fix it
- If the page moved, add a
301redirect to the new address. - If the page is gone, take it out of your sitemap and your links.
When you can ignore it
You removed the page on purpose, and nothing links to it.
If "Validate fix" failed
Validation fails here when the addresses still return 404. Check that each redirect runs on the exact address in the report, with the same slash at the end and the same www. See what each validation result means.
Fixes by platform
On WordPress
404 errors on every post after a move usually mean the permalink rules are missing. Go to Settings > Permalinks and click Save Changes, which writes the rules again. If the old domain still appears in links, replace it with a search-and-replace tool such as WP-CLI's wp search-replace. WordPress's own guide warns not to change the guid column. More in WordPress site not showing on Google.
On Shopify
Draft products, and products removed from every sales channel, return 404. After a move to Shopify, add redirects in Content > Menus > View URL Redirects > Create URL redirect. Redirects work only from addresses that are broken. More in Shopify store not showing on Google.
On Next.js
notFound() returns 404 only when it runs before streaming starts. Build sitemap.ts from the same data your routes use, so it never lists a page that no longer exists. More in Next.js pages not indexed.
On Squarespace
Squarespace's help calls this the most common error. It happens when you remove a page or change its URL slug without a redirect. Add a 301 redirect from the old address. More in Squarespace website not showing on Google.
On GitHub Pages
The entry file must be index.html, in lowercase, at the top of your publishing source. Adding or removing a custom domain without a new build breaks links. Push a commit to rebuild. More in GitHub Pages site not showing on Google.
How to find these pages
In Search Console, open Indexing > Pages and click the "Not found (404)" row. Search Console shows up to 1,000 example pages. CrawlCoach checks up to 50,000 pages per site and sorts them by reason, so you know which pages to fix first.
Questions
Do 404 errors hurt my site?
Not by themselves. A 404 is the right answer for a page that should not exist. Google drops those pages and visits them less. Fix only the addresses that should work.
Why do I see 404 errors after moving my site?
The old addresses no longer exist, and nothing sends visitors to the new ones. Add a 301 redirect from each old address that had visitors or links to its new address.
Related guides
- "Page fetch: Failed" in URL Inspection: each reason and its fix
- "Sitemap could not be read" and General HTTP error: how to fix it
- Bing "URLs with crawling issues (deadlinks)": 404 and 410 pages
- The best Google index checker tools
Sources
- Search Console Help: Page indexing report
- Google Search Central: How HTTP status codes affect Google's crawlers
- WordPress Developer Resources: Moving WordPress
- Shopify Help: URL redirects
- Next.js docs: notFound
- Next.js docs: loading.js, status codes
- Squarespace Help: Understanding Google SEO emails and console errors
- GitHub Docs: Troubleshooting 404 errors for GitHub Pages sites
Which of your pages have this problem?
Get my free reportFree for up to 500 pages. No card needed. Sign in with the Google account you use for Search Console.