A missing webpage can be frustrating for both website owners and visitors. If you’re searching how to fix 404 error, the first thing to know is that the message does not always mean your entire website is broken. A 404 is an HTTP response indicating that the server cannot find the requested resource. Common causes include incorrect URLs, deleted pages, moved content, broken internal links, and configuration problems.
Which solution is best depends on why the URL is not working. If the page was moved permanently there might be a redirection to consider. If the page was deleted purposefully and there is no alternative or replacement, a true 404, or in some situations even a 410 response, would be the correct way to go. If an existing page suddenly gives a 404-then more than likely the solution doesn’t lie with the content, and more with the permalinks, configuration, a server problem, plugin interaction or caching.
This guide takes you through that decision instead of treating every 404 as the same problem.
What Is a 404 Error?
When a server returns a 404 Not Found response, it’s a sign that the requested resource does not exist. This could be anything from an actual web page (HTML file), a document, image, or something as complex as an API endpoint (all identified via their URLs).
For example, imagine your website contains:
example.com/blog/how-to-clean-shoes/
A visitor follows an old link to:
example.com/blog/how-to-clean-shoe/
If that second URL does not result in an available resource the server might throw a 404 back at you. It’s usually not evidence your server completely crashed though, it’s the server telling the browser, “I can’t find what you’re looking for.” That really is an important detail because the fix could range anywhere from a typo, to restructuring your entire website.
Why Do 404 Errors Happen?
Before trying random fixes, identify the likely cause.
Common causes include:
Incorrect URL
A visitor may type the address incorrectly or follow a link containing a spelling mistake.
For example:
/best-running-shoes/
instead of:
/best-running-shoe/
One character can create a completely different URL.
Deleted Content
If a page was deleted, its previous URL may continue appearing in search results, bookmarks, social posts, emails, or external websites.
A deleted page can legitimately return 404.
Changed URL
When a page slug changes and no redirect is created, the old URL can lead to an avoidable 404 error.
Suppose your original article was:
/blog/website-security-tips/
and you changed it to:
/blog/website-security-guide/
The old URL does not automatically become the new URL in every website setup.
Visitors following the old link may receive a 404 unless the old address is redirected.
Broken Internal Links
Some links may still exist for pages on your website that don’t now exist. This gives you a particularly valuable clue: if you can visit your website to click a link and encounter the same 404 error, the issue is likely on your side and not with the linked page.
Incorrect Server or Routing Configuration
If numerous pages have begun to return 404s – particularly pages that worked yesterday – the issue is bigger than single URLs. The issue of friendly URLs resulting in a 404 may occur server-side or on platforms like WordPress through conflicts with “pretty link” configuration or through mod_rewrite on WordPress servers.
Plugin or Theme Conflicts
A WordPress plugin, theme customization, or rewrite rule can sometimes interfere with URL routing.
If a 404 began immediately after a plugin, theme, migration, or configuration change, that timing is an important troubleshooting clue.
How to Fix 404 Error Step by Step
The most efficient approach is to diagnose the specific URL first.
Step 1: Check the URL Carefully
Start with the simplest explanation.
Look for:
- Misspelled words
- Missing characters
- Extra characters
- Incorrect capitalization where your server treats URLs as case-sensitive
- Incorrect folders
- Old URL slugs
- Accidental duplicate characters
- Incorrect file extensions
Copy the URL and compare it with the address of the page you intended to visit.
If manually correcting the URL takes you to the intended page, the 404 may simply be caused by an incorrect address.
Step 2: Determine Whether the Page Actually Exists
Try searching on your website for either the page title or some text from its content.
If the page simply exists at a different URL than expected, this may not be a missing content issue as much as a URL migration issue.
If the page has genuinely been removed and there is no useful replacement, you may not need to “fix” the 404 at all.
Google explains that when content has been removed and there is no replacement, returning a genuine 404 or 410 status code can be appropriate.
Step 3: Test the URL From a Fresh Session
If you believe the page exists, test it independently.
Try:
- A private/incognito browser window
- Another browser
- A different device
- A different network when practical
This can help determine whether the problem is local to your browser or reproducible for everyone.
Nevertheless, if you keep receiving a 404 from the server, then clearing out your cache will likely never help with a broken resource at the back-end. Take browser fixing as the next and NOT the go-to.
How to Fix a 404 Caused by a Changed URL
If the page has moved permanently to another relevant URL, use a 301 redirect from the old address to the new one.
For example:
/old-page/ → /new-page/
The redirect should point to the most relevant replacement, not automatically to the homepage.
Google recommends using a 301 redirect when a page has permanently moved to another location.
Why Redirects Matter
Allows visitors who still visit with the old URL to reach.
Allow search engines too as they realize they now know the real location was replaced by new.
However, do not redirect any nonexistent URL to the home page merely in an attempt to make a 404 count disappear. Google warns against deceptive redirects which suggest that a nonexistent URL actually has content (which it doesn’t). The target URL must genuinely address the searcher’s assumed intent.
When You Should Keep the 404
Every 404 does not need to go.
Let’s say an article detailing a product that no longer exists has been deleted from your blog and you do not have a comparable replacement. You may end up performing a random redirect just to eliminate the 404 which might frustrate users with the experience that you provided. Some real-404s are necessary. According to the official Google Search Console guide they recommend that you respond with 404 or 410 for content that has no viable replacement on your site.
The difference is that your 404 page itself should still be useful.
Instead of displaying only:
404 — Page Not Found
you can provide navigation, a search box, popular content, and relevant categories.
What Is a Soft 404?
A soft 404 is different from a normal 404.
When a 404 error appears, it means the requested content could not be retrieved from the website. However soft 404 is more deceptive since instead of showing a 404 like page it instead show contents like no result found, but will return successful 200 HTTP response. Google consider it as bad since on the HTTP response it says the content successfully loaded but the content actually says nothing is there.
For example:
example.com/does-not-exist/
might display:
“Sorry, we couldn’t find this page.”
But the server returns:
200 OK
That mismatch can create crawling and indexing confusion.
How to Fix a Soft 404
First decide what should happen to the URL.
If the content is gone and has no replacement: return a real 404 or 410.
For permanently relocated content, a 301 redirect is the appropriate way to guide users to the updated page.
If the content still exists: determine why the correct page is being rendered incorrectly and repair the underlying issue.
Google recommends using the URL Inspection tool to investigate pages reported as soft 404s and verify the returned HTTP status and rendered content.
How to Fix 404 Error in WordPress
WordPress websites have several additional troubleshooting steps.
Refresh Permalinks
If an existing WordPress page suddenly returns 404, one useful first step is to refresh the WordPress permalink rules.
In the WordPress dashboard, go to:
Settings → Permalinks
Then save the existing settings.
It doesn’t mean you must edit permalink structure always. However, it’s enough to save the changes to rewrite rules be rebuilt.
WordPress support document and its administration handbook list “Permalink and Rewrite Settings” as one of usual places where to search when beautiful permalink 404.
Check the Page’s Slug
Open the affected post or page and verify that its permalink is correct.
Look for:
- Unexpected slug changes
- Duplicate slugs
- Incorrect parent paths
- Draft or unpublished content
- Accidental URL edits
If only one page is affected while the rest of the site works normally, the individual page configuration deserves attention before you change server-wide settings.
Investigate Plugins
If the 404 started after installing or updating a plugin, consider whether that plugin changes:
- URL structures
- Redirects
- Custom post types
- Rewrite rules
- Security settings
- Caching behavior
When troubleshooting WordPress the advice normally given is to try turning off plugins, one by one. To see which one it is causing the issue. Don’t switch them all off without needing a reason- we’re trying to find what’s causing the issue.
Check the Theme
A custom theme or theme modification can also affect URL behavior.
If a plugin test doesn’t reveal the cause, testing with a default WordPress theme can help determine whether the theme is responsible.
What If Every WordPress Page Returns 404?
This situation is more serious than one broken article.
If the homepage works but most internal pages suddenly return 404, investigate:
- Permalink settings
- Rewrite rules
- .htaccess configuration on Apache
- Nginx configuration where applicable
- Recent hosting or migration changes
- Plugin conflicts
- Theme changes
- Server configuration
The WordPress codex states that pretty permalinks rely on URL rewrites and a misconfiguration of the rewrite rules can lead to 404 Not Found errors. Unless you’re willing to go ahead and tweak the server config, DO NOT play around with your live files until you confirm the changes. Contact your hosting company or another developer for assistance.n.
How to Fix 404 Errors After a Website Migration
Website migrations are a common time for URL problems to appear.
Imagine your old website uses:
/articles/topic-name/
while the new site uses:
/blog/topic-name/
Every old URL may suddenly become a potential 404 unless the migration includes appropriate redirects.
A good migration process should map important old URLs to their corresponding new destinations.
Create a URL Mapping
A simple spreadsheet can help:
| Old URL | New URL | Action |
| /old-guide/ | /new-guide/ | 301 redirect |
| /old-product/ | No replacement | 404/410 |
| /old-topic/ | /related-guide/ | Redirect if genuinely relevant |
This prevents redirect decisions from becoming guesswork.
Don’t redirect every old URL to the homepage. A redirect should make sense from the user’s perspective.
How 404 Errors Affect SEO
A 404 is not automatically an SEO disaster.
Google has explicitly explained that 404 responses themselves do not inherently damage a website’s search rankings.
The problem is unnecessary or poorly managed 404s that can become part of broader technical SEO problems.
For example, hundreds of internal links pointing to nonexistent pages create a poor user experience and indicate that the site’s link structure needs attention.
Likewise, important pages that accidentally return 404 can disappear from their intended role in search.
The aim is not to eliminate all 404 pages without considering whether they are necessary.
The goal is:
Correct URLs should work, moved pages should redirect appropriately, and genuinely unavailable pages should return accurate status codes.
That is a much healthier technical SEO strategy.
How to Find 404 Errors on Your Website
You can identify broken URLs through several sources.
Google Search Console
Google Search Console can help you investigate crawling and indexing problems.
If Google reports a URL as a 404, determine whether:
- The URL should exist
- The URL has moved
- The URL was intentionally deleted
- Internal links still point to it
- External websites still reference it
Don’t automatically redirect every URL reported by Search Console.
A URL can appear in reports even when you intentionally removed the content.
Website Crawlers
A site crawler can help you find internal links pointing to dead ends.
This is especially important on large sites where manually reviewing all the links is impossible.
After you have compiled the list of all dead URLs, separate them into groups according to the following criteria:
• The link leads to the incorrect resource.
• The resource has permanently moved to a new location.
• The resource has permanently disappeared and will not be replaced.
Common 404 Mistakes
Redirecting all the URLs to the homepage
While the homepage is a logical choice for a destination, it is not necessarily the best option. In most cases, the visitor will be disappointed not to find the information they were looking for on the homepage. A better choice would be to redirect the URL to a relevant page matching the original content.
Changing the URL without setting up redirects
While the new slug looks nice and short, you have created numerous broken links by changing the address. Before changing any URL, think about where to redirect the traffic, or decide to leave the resource be.
Treating all the 404 errors as an SEO emergency
If you deliberately deleted the page, it is not an error for Google to return a 404 code. Unless the resource was removed accidentally or it is a crucial page for your users, leave it as is. Do not waste your time on the minor issues if there are bigger problems to solve.
Installing another plugin to fix the 404 error before identifying the cause of the problem
If the WordPress site has a routing issue, installing another plugin will most likely make it more broken. Always follow the principle of Occam’s Razor when troubleshooting the code. If you are not certain how the problem can be solved, consult your server’s administrator or a professional developer.
Editing the files on the server directly without making a backup
The .htaccess file and the rest of the server configuration contain the critical information for your website to function correctly. If you are not certain how to edit the file, research the changes or ask for help from your hosting provider.
Practical Steps to Prevent Future 404s
Prevention is easier than repeatedly repairing broken URLs.
Keep a Record of Important URLs
When redesigning or migrating a website, maintain a list of important existing URLs.
This gives you a reference when planning redirects.
Avoid Unnecessary URL Changes
A URL does not need to be changed simply because another wording sounds slightly better.
Changing established URLs can create extra redirect and link-maintenance work.
Check Internal Links Regularly
Broken internal links can accumulate as a website grows.
Periodic crawling can identify them before visitors do.
Update Links After Content Changes
If you delete, merge, or rename an article, check other pages that linked to it.
This is especially important for high-traffic guides and cornerstone content.
Monitor Search Console
Search Console can provide useful information about how Google encounters URLs on your site.
Use the information diagnostically rather than trying to eliminate every reported URL automatically.
A Simple 404 Troubleshooting Decision Tree
When you encounter a 404, ask these questions in order:
Does the URL contain a typo?
If yes, correct it.
Does the intended content exist somewhere else?
If yes, use or create the appropriate redirect if you control the site.
Was the content intentionally deleted?
If yes, a genuine 404 or 410 may be appropriate when there is no relevant replacement.
Should the page still exist but doesn’t load?
Investigate CMS settings, routing, plugins, themes, server rules, and deployment changes.
Are many pages affected?
Investigate the site’s URL-routing or server configuration rather than editing individual URLs one at a time.
Is Google reporting a soft 404?
Inspect the URL’s HTTP status and rendered content and correct the underlying response.
This approach saves time because each answer narrows the possible cause.
Final Thoughts on How to Fix 404 Error
Learning how to fix 404 error problems starts with understanding that not every 404 requires the same solution.
A misspeltURL needsa fix. Abroken URL toamore than anever-existingnewpage needsa appropriate 301 permanent redirect. Ananactively removednewpageisoften rightly anintentionallostPAGE (404 or 410).
AWordPresssite havingmany404errorstodeserveinvestigationsinto theirpermaliinrg; rewrite rule configuration.
Asoft404willrequiresomeresolvingarounditsContentAS wellASitsHTTTPstatuscode. Aboveallistheessential habit of–before youdo anything– diagnose first. Lookat theURL,assessifthepageoughtto exist,considerwhat changeshave takenplace and then act appropriately. Whenitcomes toanSEO website, don’t try and achieve “zero 404s”.
Youneedto ensure that important pages are accessible,that all old pages,have the right redirects,and that no broken internal links are showing.
Don’tforget that allURLswhich should existanddon’t need tobe correctly flagged to the browser. There will naturally be pages that will always be 404 on an well-keptsite,yet It is whenever visitorsand/or search enginestargetan onlined page whichiswhere theyought, thattheproblem lies.
FAQs About How to Fix 404 Error
1. What is the best way to resolve a 404 error?
Initially, check if the URL is incorrect or the page exists in a different location. If the page was moved to a new location permanently, a 301 redirect should be implemented. If the page exists, analyze your CMS options, permalinks, routing configurations, or server misconfigurations.
2. Should I redirect all 404 pages?
No. If the resource is permanently deleted, a 410 response code, or if there is no suitable replacement page, a 404 response code. According to Google, it is advisable to use a proper response code for vanished content.
3. Does a 404 error affect SEO?
It does not cause a direct harm to your SEO score. Google says that 404 errors are an ordinary part of the web. However, having important pages returning 404 and a significant number of other broken links on your site may lead to usability and SEO issues.
4. How can I fix the 404 error in WordPress?
Check the page URL first, and if it is correct, go to Settings -> Permalinks and resave them. It should typically fix the 404 error in WordPress. If not, the problem might be in plugins, themes, rewrite rules, or .htaccess server configuration. WordPress recommends checking those areas in case of a 404 error.
5. What is the difference between 404 and 410 errors?
Both 404 and 410 HTTP status codes are related to missing content, but while 404 is a generic response, 410 is more specific and suggests that the resource is gone for good. Essentially, the main difference is that 410 is a special type of 404.
6. What is a soft 404 error?
Soft 404 is a type of 404 error when the server returns an OK 200 response code instead of an appropriate 404 response. Google says that such issues should be fixed by correcting the status and behavior of the URLs.
7. Why am I getting a 404 error after migrating the website?
After migrating your site, you may start getting 404 errors because of the changes to the URL structure. In case the page URL has permanently changed, a 301 redirect from the old address to the new one should be set up. On larger sites, it may be necessary to make a list of URL mappings in order to ensure that no important pages will remain unrecoverable in the future.
