πŸ› οΈ Fixing Soft 404 Warnings on React Sites

Camilo Aponte

Camilo Aponte

Last updated on Nov 18, 2026

πŸ” What Is a Soft 404?

A soft 404 happens when a page that does not exist shows a "page not found" message to visitors, but the server still replies with a success status (HTTP 200). Search engines expect a real 404 status for missing pages. When they get a 200 instead, they flag the URL as a soft 404.

This is very common on React sites, and it usually does not mean something is broken in your content.

βš™οΈ Why React Sites Do This

Most React sites are single-page applications. The server sends the same basic HTML file for every URL, and React then decides in the browser what to display. If the URL does not match a known route, React shows a "Not Found" screen. By then, the server has already replied with 200.

So the page looks like an error to people, but the status code tells search engines the page is fine.

βœ… Step 1: Confirm the Problem

Before changing anything, check how your site responds to a made-up URL.

  1. Open your site and type a URL that should not exist, for example yourdomain.com/this-page-does-not-exist.
  2. Open your browser developer tools and go to the Network tab.
  3. Reload the page and click the first request (the page itself).
  4. Look at the Status value. If it says 200, the server is returning a soft 404. If it says 404, you are set.

You can also use the URL Inspection tool in Google Search Console to see how Google views the page.

πŸš€ Step 2: Make Unknown URLs Return a Real 404

The right fix depends on how your site is built and hosted. Share these options with your developer.

  • Server-side rendering frameworks (such as Next.js or Remix): Use the framework's built-in not-found handling so the server sends a 404 status along with your custom error page. In Next.js, this means calling the notFound function or using a custom 404 page.
  • Custom Node or Express server: When no route matches, set the response status to 404 before sending your app's HTML.
  • Static hosting (Netlify, Vercel, Cloudflare Pages, S3): Avoid a catch-all rule that sends every URL to index.html with a 200 status. Instead, list your real routes in the rewrite rules and let everything else fall through to a 404 page with a 404 status.
  • Nginx or Apache: Only fall back to index.html for known route patterns, and return a 404 for the rest.
  • Prerendering: Generate real HTML files for each valid page at build time. Any URL without a file then returns a natural 404.

If your site has many dynamic URLs, such as product pages loaded from an API, the server needs to check whether the item exists before responding. This is the most reliable fix, and it usually requires server-side rendering or an edge function.

πŸ’‘ Step 3: Use a Fallback If Server Changes Are Not Possible

Some setups cannot return a 404 for unknown URLs, for example a plain Create React App site on basic static hosting. In that case, you have two workarounds that Google supports:

  • Redirect to a real 404 page: When React detects an unknown route, send the visitor with JavaScript to a dedicated URL (such as /404) that the server does answer with a 404 status.
  • Add a noindex tag on the Not Found screen only: Use your React app to insert a robots meta tag with the value noindex when the Not Found component loads. This tells Google not to index that URL.

Important: Do not put noindex in your base index.html file. It would apply to every page on your site, including valid ones. It should only be added by the Not Found component.

These fallbacks work, but they depend on Google running your JavaScript. A true server-side 404 is always the more dependable option.

πŸ“Š How Serious Is This for SEO?

For most sites, soft 404s on genuinely nonexistent URLs are low to moderate in severity. Here is what to keep in mind:

  • No penalty: Google does not penalize a site for having soft 404s. It simply treats those URLs as errors and usually leaves them out of the index.
  • Crawl budget: On large sites, Google may spend time crawling junk URLs that return 200. This can slow down how quickly it finds your real pages.
  • Reporting noise: Soft 404 warnings can clutter your reports and make real issues harder to spot.
  • Higher risk: It becomes more important to fix if your site generates large numbers of nonexistent URLs, if internal links point to missing pages, or if bad URLs are being indexed.

If you only have a handful of test URLs flagged and your important pages are indexed normally, you can treat this as a low-priority cleanup.

⚠️ When a Real Page Is Flagged as a Soft 404

Sometimes Google marks a page that does exist as a soft 404. This is more urgent because the page may drop out of search results. Common causes include:

  • The page loads blank or nearly empty because content fails to load for crawlers.
  • An API call fails and the page shows an error or "no results" message.
  • The page has very little unique content.
  • Important scripts or data are blocked from crawlers.

To fix this, make sure the main content appears in the page after rendering, check that your data requests succeed, and add useful, unique content. Then use the URL Inspection tool in Google Search Console to request reindexing.

πŸ”„ Step 4: Verify the Fix

  1. Test your made-up URL again in the Network tab and confirm the status is now 404.
  2. Check that your valid pages still return 200.
  3. Re-run your site audit in Search Atlas to refresh the results.
  4. In Google Search Console, open the Page indexing report and use Validate Fix for the soft 404 issue.

Google can take several days to a few weeks to recheck all affected URLs, so the warnings will not disappear immediately.

πŸ’¬ Need Help?

If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Was this article helpful?