Soft 404 Errors in WordPress: When to Restore, Redirect, or Remove a Page

A page can look perfectly normal to a visitor and still send the wrong message to search engines. One example is a soft 404: a URL that behaves like a missing page but responds as though everything is fine. For a small business website, that can leave obsolete service pages, removed products, or empty location pages lingering in search reports.

What is a soft 404?

A regular 404 response tells browsers and crawlers that a URL does not exist. A soft 404 is different: the server may return a successful 200 OK response even though the content says “page not found,” contains almost nothing, or redirects visitors to an unrelated destination. Google can classify such URLs as soft 404s based on what it sees.

A soft 404 report is not proof that the website is broken everywhere. It is a reason to inspect the specific URL and decide what that address should do.

Start with the page’s intended purpose

Before changing a redirect or creating replacement content, ask one question: Should this URL still represent a useful page? The answer determines the correct fix.

The page should exist

If the URL belongs to a real service, article, or location, restore useful content at the intended address. Check that the correct page template loads, the main heading describes the subject, and visitors can find the information promised by the link.

The page moved to an equivalent URL

Use a permanent 301 redirect to the most closely matching replacement page. For example, an old service URL can point to the new version of that same service. Avoid sending every missing page to the homepage or a broad state page simply because it is convenient.

The page was intentionally removed

If there is no suitable replacement, allow a genuine 404 response or use 410 Gone when removal is deliberate and permanent. A helpful branded error page can still include navigation and a search option; its HTTP status must remain correct.

How to investigate a reported soft 404

  1. Open the exact reported URL. Check the visible page, not only its title or redirect settings.
  2. Inspect its HTTP response. A working content page should normally return 200; a missing page should return 404 or 410; a genuinely moved page should redirect to a relevant replacement.
  3. Follow any redirects. Look for unrelated destinations, loops, and chains that pass through several URLs.
  4. Compare the content with the URL. A city page promising local website design but showing only a generic sentence may not satisfy the visitor’s intent.
  5. Check internal links and the XML sitemap. Update links to removed addresses and avoid advertising obsolete URLs in sitemaps.
  6. Recheck the final destination. Confirm the response code and rendered page match the intended outcome.

Common mistakes that make cleanup harder

Redirecting all errors to the homepage. This conceals the original problem without providing a useful substitute. Search engines may still regard the destination as irrelevant.

Publishing thin replacement pages. Adding a heading and two generic sentences does not automatically make a removed page worth restoring. The replacement needs a distinct purpose and helpful content.

Trusting a plugin setting without testing. A redirect entered in WordPress can be overridden by server rules, caching, or another plugin. Check what the browser actually receives.

Removing pages without updating links. Old navigation links, article references, and service-area directories can continue sending visitors to dead ends. Our guide to finding and fixing broken WordPress links explains how to prioritize those repairs.

What about service-area and city pages?

Location pages deserve special care because many can share similar wording. A city URL should have a clear reason to exist beyond changing the place name in a template. Describe relevant services, answer real customer questions, and provide a useful path to related information. If several URLs have no distinct purpose, assess consolidation carefully rather than automatically redirecting every one to a state hub.

For an example of how an actual location page fits into the site, see the Rochester, Minnesota website design page. The principle is broader than one city: visitors should reach content that matches the link they clicked.

After making the fix

Test the URL again and record the response code, destination, and page content. Then use Google Search Console’s URL Inspection tools when appropriate to see how Google currently understands the address. Reports may take time to reflect a correction; a successful browser test does not guarantee immediate reindexing.

If the soft 404 appeared after a redesign or domain change, also review the WordPress redirect troubleshooting guide before adding another redirect rule.

The practical rule

Keep useful pages as real pages, redirect moved content to genuinely equivalent replacements, and let removed content return an honest missing-page status. That simple distinction is more reliable than trying to make every old URL return 200.

651 Web Design helps businesses plan clearer WordPress site structures and address website issues that affect visitors. If you’re reviewing a larger redesign, start by identifying which existing pages should stay, move, or be retired.