How to Fix 404 Errors and Use 301 Redirects Correctly

Every website collects broken URLs over time. A service page gets renamed, a promotion ends, a product is discontinued, or a new theme changes how addresses are built. Then Google Search Console starts listing “Not found (404)” pages, a customer taps an old link on WhatsApp and lands on an error screen, and someone on the team asks whether the website is “being penalised”.

The good news is that most 404 errors are harmless, and the ones that matter are easy to fix once you know which is which. This guide explains how to fix 404 errors properly: when a 404 or 410 is the right answer, when a 301 redirect is the right answer, how to spot soft 404s and redirect chains, how to handle redirects on WordPress, and a step-by-step plan your team can follow in an afternoon.

What a 404 error actually tells Google and your visitors

When a browser or crawler requests a URL, your server replies with an HTTP status code before any content. 200 means “here is the page”. 404 means “nothing exists at this address”. 410 means “this existed once and has been removed on purpose”. 301 and 308 mean “this has moved permanently, go here instead”.

Google’s documentation on how HTTP status codes affect its crawlers says that 4xx errors (other than 429, which signals rate limiting) are treated the same way: the content does not exist, and if the URL was indexed, it is removed from the index. Google also states these errors do not affect how fast it crawls the rest of your site. In other words, a 404 on a page that should not exist is the system working correctly, not a ranking penalty.

The real costs of 404s are more practical:

• Lost visitors. Someone who clicks an old link from a Facebook post, a directory listing or a forwarded WhatsApp message hits a dead end and often leaves.
• Wasted links. If other websites link to a URL that now returns 404, the value of those links is no longer pointing at a live page on your site. Our guide to inbound links and why they matter explains why those references are worth keeping.
• Lost rankings for moved pages. If you changed a URL without redirecting it, the old address drops out of the index and the new one has to earn its place from scratch.

When a 404 or 410 is the right answer

Not every missing page needs a redirect. Google’s guidance is straightforward: if you have removed a page and there is no equivalent replacement, return a 404 or 410. Google has said for years that it treats the two in much the same way, so do not lose sleep over which one you pick. Use 410 if your platform makes it easy and you want to be explicit that the removal is permanent.

A 404 or 410 is usually correct for:

• Expired one-off promotions, such as a Great Singapore Sale or Chinese New Year landing page you will never reuse.
• Discontinued products with no close substitute.
• Old tag, author or archive pages your CMS created automatically and you deliberately removed.
• Junk URLs that never existed, such as random strings from spam bots or mistyped links on another site.
• Test or staging pages that were accidentally made public.

What you should not do is redirect every missing URL to your homepage. Google treats a redirect to an irrelevant page as a soft 404 in many cases, and visitors find it confusing: they wanted a specific article or product and landed somewhere generic with no explanation. A helpful custom 404 page, with a search box, links to your main services and a WhatsApp or contact button, serves visitors better.

When to use a 301 redirect instead

Use a permanent redirect when the content has moved or has a clear successor. Google’s page on redirects and Google Search explains that permanent server-side redirects (301 or 308) are a strong signal that the destination should become the canonical URL. Google’s site-move guidance also states that permanent redirects do not cause a loss of PageRank, which is the old worry many owners still have.

Typical cases where a 301 is the right fix:

• You renamed a page, for example from /services/aircon-servicing-singapore-2023/ to /aircon-servicing/.
• You merged two thin articles into one stronger guide. Redirect the weaker URL to the merged one.
• A product has been replaced by a newer model that genuinely serves the same need.
• You moved from http to https, changed domain, or switched between www and non-www. These belong in a full SEO migration checklist rather than ad hoc fixes.
• A popular page was deleted by mistake and you have since recreated it at a new address.

The test is simple: would a visitor who wanted the old page be satisfied with the new one? If yes, redirect. If you have to stretch to justify it, let the old URL return a 404.

301, 302, 307, 308 and meta refresh compared

A common mistake is leaving a temporary 302 in place for a permanent change, often because a plugin defaulted to it. Google may eventually treat a long-standing 302 as permanent, but there is no reason to rely on that. Choose the code that describes what actually happened.

Soft 404s: the error that hides behind a 200

A soft 404 is a page that looks like an error to users (“Sorry, this product is no longer available”, an empty search results page, a blank category) but returns a 200 success code to crawlers. Google’s crawling errors troubleshooting guide asks site owners to return a real 404 or 410 for pages that no longer exist, or to add useful content if the page should exist.

In Search Console, soft 404s appear in the Page indexing report under “Soft 404”. Common causes on Singapore SME sites include:

• Empty e-commerce category pages after stock runs out.
• Internal search result pages with no results that are linkable and crawlable.
• Very thin location pages (for example, an “Ang Mo Kio” page with one sentence and nothing specific).
• Redirects from removed pages to an unrelated page such as the homepage.
• Pages that rely on scripts or resources that fail to load, so Google renders a near-blank page.

For the last case, use the URL Inspection tool in Search Console to view the rendered page and the status code Google received. If Google sees a blank page that real visitors see properly, the problem is technical (blocked resources, a broken script or a timeout), not content.

Redirect chains and loops

A redirect chain happens when URL A redirects to B, which redirects to C, and so on. Chains build up quietly: a 2019 rename, a 2022 https move and a 2025 restructure can leave the original link three hops away from the live page. Google says its crawlers follow a limited number of redirect hops, and its site-move guidance recommends pointing each old URL directly at its final destination. Each hop also adds delay for visitors on mobile data.

A redirect loop (A to B, B back to A) is worse: the browser gives up with an error and no one reaches the page. Loops often appear after someone adds a redirect in a plugin and a conflicting rule in the hosting panel or a CDN.

To fix chains, export your redirect list, find any rule whose destination is itself redirected, and update the original rule to point straight to the final URL. Then update internal links so your own pages link to final URLs directly. Our article on internal links in SEO covers why clean internal linking matters beyond redirects.

How to find 404s, soft 404s and redirect problems

You do not need expensive software to get a clear picture. Combine three sources:

Google Search Console

The Page indexing report groups excluded URLs by reason. Look at “Not found (404)”, “Soft 404” and “Page with redirect”. Remember that “Not found (404)” often lists URLs Google discovered from old links or guesses; Google states that listing them is informational, and many need no action. Focus on URLs you recognise as real pages, or ones that still receive clicks or external links.

A site crawler

A crawler visits every link on your site and reports status codes. This finds the 404s that matter most: broken links on your own pages, which you fully control. It also reveals chains and internal links that pass through redirects. This is a core step in any SEO audit.

Analytics and server logs

In Google Analytics 4, filter page views by your 404 page’s title to see which broken URLs real people are actually landing on. If your host provides access logs, they show every request that returned 404, including from bots. Prioritise the URLs with real human traffic.

Fixing redirects on WordPress

WordPress has some redirect behaviour built in. When you change a post’s slug, core WordPress usually remembers the old slug and redirects it to the new address. That is helpful, but it does not cover changed page parents, deleted pages, category restructures or URLs from an old non-WordPress site.

Common approaches, from simplest to most technical:

• A redirect plugin. Lets you add old-to-new rules in the dashboard, choose 301 or 410, and often log 404 hits. Check that it defaults to 301, not 302, and review its 404 log regularly.
• Your SEO plugin’s redirect module. Several popular SEO plugins include a redirect manager, sometimes only in paid tiers. Avoid running two redirect tools at once.
• Hosting panel or CDN rules. Useful for domain-wide moves (http to https, www to non-www). Keep page-level rules in one place so you do not create loops.
• Server configuration (.htaccess or Nginx). Fast and reliable, but a typo can take the whole site down. Leave this to someone experienced and keep a backup.

Whatever tool you use, keep a single spreadsheet of every redirect: old URL, new URL, code, date and reason. Google recommends keeping redirects in place for a long time (at least a year for site moves); in practice, many businesses keep them indefinitely because they cost very little. Also update your XML sitemap so it lists only final, 200-status URLs; see why your sitemap matters for SEO.

A step-by-step plan to fix 404 errors

Here is an implementation plan a small team can follow. Timings are rough planning ranges for a typical SME site of under a few hundred pages.

1. Export the data (owner: marketing lead, 30 minutes). Download the Not found, Soft 404 and Page with redirect lists from Search Console, plus a crawl of your site.
2. Triage (marketing lead, 1 hour). Label each URL: moved (needs 301), removed (leave as 404 or set 410), should exist (restore or fix), or junk (ignore).
3. Map destinations (content owner, 1 hour). For each moved URL, choose the single most relevant live page. Do not default to the homepage.
4. Implement redirects (web admin, 1–2 hours). Add rules in one tool, using 301. Collapse any chains to one hop.
5. Fix internal links (web admin, 1 hour). Update menus, buttons and in-text links so they point to final URLs, not redirects or 404s.
6. Fix soft 404s (content owner, ongoing). Return real 404s for empty pages, or add genuine content to pages that should stay.
7. Validate (marketing lead, 15 minutes). Test a sample of old URLs in a browser and with URL Inspection. In Search Console, use “Validate fix” for soft 404 issues.
8. Monitor monthly (marketing lead, 15 minutes). Recheck the reports and redirect plugin logs, and add rules for any new moved pages before you publish changes.

How AI can help with broken pages and redirects

AI tools are good at the repetitive parts of this work. A crawler combined with an AI assistant can group hundreds of 404s by pattern (for example, all URLs under an old /blog/2021/ structure), suggest the most likely replacement page for each by comparing titles and content, and draft a redirect map for a person to check. AI can also summarise Search Console exports and flag new spikes in errors.

The limits are important. AI can match a removed page to a destination that looks similar but serves a different intent, and a bad redirect can be worse than an honest 404. A person who knows the business should approve every mapping, and changes to live redirects should be tested before and after. Marketing2u’s AI SEO Agent checks status codes, redirects and broken links and reports them, but it deliberately does not change URLs or redirects itself; those decisions stay with you. The AI Website Agent monitors for broken pages and links and records changes with before/after history and undo where it has approved access.

Common mistakes to avoid

• Redirecting every 404 to the homepage.
• Using 302 for permanent changes because it was the plugin default.
• Leaving internal links pointing at redirected or broken URLs.
• Stacking rules in a plugin, the host and a CDN, creating chains or loops.
• Deleting redirects a few months later to “clean up”.
• Blocking old URLs in robots.txt. If Google cannot crawl a URL, it cannot see the 404 or the redirect.
• Panicking about every URL in the Not found report instead of focusing on pages with traffic or links.
• Changing URL structures for cosmetic reasons without a redirect plan.

Conclusion: fix 404 errors with a clear rule, not guesswork

To fix 404 errors well, apply one rule consistently: if the content moved or has a true successor, use a single-hop 301 redirect; if it is gone for good, let it return a 404 or 410 and give visitors a helpful error page. Keep one redirect list, update internal links, watch for soft 404s, and check Search Console monthly. That small routine protects the links and visitors you have already earned, and keeps Google focused on the pages that matter to your business.

Frequently asked questions

Do 404 errors hurt my SEO?

Not on their own. Google states that 404 errors for pages that genuinely do not exist are normal and do not affect how the rest of your site is crawled or ranked. They matter when a page that moved or still receives links and visitors is returning 404, because you lose that traffic and link value.

Should I redirect all 404 pages to the homepage?

No. Redirecting unrelated URLs to the homepage confuses visitors, and Google often treats such redirects as soft 404s anyway. Redirect only to a page that genuinely replaces the old one, and let the rest return a 404 or 410 with a helpful custom error page.

What is the difference between a 301 and a 302 redirect?

A 301 tells search engines the move is permanent, so the new URL usually becomes the canonical address. A 302 signals a temporary move, so the original URL tends to stay in the index. Use 301 (or 308) for permanent changes and 302 or 307 only for changes you plan to reverse.

How long should I keep 301 redirects in place?

Google recommends keeping redirects for site moves in place for at least a year, and many businesses simply keep them indefinitely. Old links on other websites, social posts and messaging apps can keep sending visitors for years, and a redirect rule costs very little to maintain.

What is a soft 404 in Google Search Console?

A soft 404 is a page that tells users it does not exist, or has almost no content, but returns a 200 success status code. Fix it by returning a real 404 or 410 if the page is gone, or by adding genuine content if the page should stay, then use Validate fix in Search Console.

Sources and further reading

• Google Search Central: Redirects and Google Search
• Google: How HTTP status codes affect Google's crawlers
• Google Search Central: Troubleshoot crawling errors (soft 404s)
• Google Search Central: Site moves with URL changes
• Search Console Help: Page indexing report

Related guides

• Soft 404 Errors: Why Google Flags Them and How to Fix Them
• 23-Step SEO Migration Checklist For A Seamless Website Migration
• How To Do An SEO Audit: 9 Things To Check For
• SEO-Friendly URL Structure: Best Practices for 2026
• How to Get Your Pages Indexed Faster by Google

Browse every article in our SEO guides.