Skip to content

"Soft 404": what it means and how to fix it

The page loads, but Google thinks it looks like an error or an empty page.

You can fix this

By Bruno Amorim · ·

What it means

The server says 200 OK, but the page looks like a "not found" page, an empty search result, or a page with almost nothing on it. Google treats it as an error and leaves it out.

The fix, in short: If the page is gone, return a real 404 or 410. If the page is real, add content so it no longer looks empty or like an error.

Which kind of soft 404 is it?

Open three or four of the example pages in your browser. Each kind has its own fix.

What the page isWhy Google reads it as an errorThe fix
A page that is gone but still loads a "not found" messageThe page says it doesn't exist while the server says 200 OK.Return 404 or 410. If the page moved, 301 redirect it to the new address.
An empty category, tag, or search results pageWith nothing to list, the page is a header, a footer, and "no results".If it fills up again soon, show related items in the meantime. If not, return 404 and take it out of your menus and sitemap.
A sold-out or discontinued productThe page says little besides "out of stock" or "no longer available".Keep the full description and link to similar products. If it won't come back, 301 redirect to the closest product, or return 404.
A real page that shows blank or a spinner to GoogleThe content loads with JavaScript that failed for Google, or a bot blocker served Google an empty page.Compare the Screenshot tab with your browser. Send the main content in the HTML from your server.
A "coming soon" or "under construction" placeholderThere is no content to index yet.Publish the real page first, and keep the placeholder out of your sitemap.

See the page the way Google does

In Search Console, open Indexing > Pages, click the Soft 404 row, and inspect one example address. Click Test live URL, then View tested page. The Screenshot tab shows how Google rendered the page. The HTML tab shows the HTML Google got.

In Search Console: URL Inspection > Page indexingExample
URL
https://example.com/products/blue-rain-jacket
Page indexing
Page is not indexed: Soft 404
Page fetch
Successful
Indexing allowed?
Yes

Page fetch says Successful because your server answered 200 OK. Google got the page, then judged what was on it.

Illustration, not a screenshot. Your addresses, dates, and counts will differ.

Fix it without making it worse

Check the status code your server sends

What matters is the code in the response, not the words on the page. Run this in a terminal, or open your browser's developer tools and read the status on the Network tab. A page that is gone should answer 404 or 410.

Check the status of a page that is gone
curl -I https://example.com/old-page

HTTP/2 404

Keep error words small on real pages

A full page can still read as an error when its biggest words say "no longer available" or "not in stock". Keep that message short, and keep the product details, photos, and links to similar items on the page.

Make sure Google gets the content

If the screenshot is blank, open the HTML tab. If the main text isn't there, render it on the server or prerender the page. CarScout ran into this. In April 2026, it fixed a rendering problem that could show search engines a loading screen instead of the page. Also check that your firewall or bot protection isn't serving Google a challenge page.

Read the CarScout case study

Take gone pages out of your sitemap and links

Google's crawl budget guide says soft 404 pages keep getting crawled, while a 404 is a strong signal not to crawl the address again. On a large site, that difference adds up.

What Google has said

"If the content suggests an error for Google Search, an empty page or an error message, Search Console will show a soft 404 error."
Google crawling docs, How HTTP status codes affect Google's crawlers. Source
"soft 404 pages will continue to be crawled, and waste your budget."
Google crawling docs, Optimize your crawl budget. Source
"those pages would probably get caught by the soft error page detection thing that we have"
Gary Illyes, Google, on Search Off the Record (June 22, 2023), about "under construction" pages on new domains. Source

A placeholder has nothing to index. Publish the real page, then ask Google to look.

For the soft 404 pages you track, CrawlCoach's fix list reads the HTML your server sends and counts the words in its main text. If there are almost none, it says so, and notes that the content may still load with JavaScript, because Google runs JavaScript and CrawlCoach does not.

See which of your pages Google reads as errors, and the 3 to fix first.

Get my free report

How long it takes, and what to measure

Google decides again the next time it crawls the page. Google's recrawl guide says crawling can take a few days to a few weeks. Here the live test helps early: Google's help doesn't list Soft 404 among the reasons Test live URL can't check, so the Screenshot tab tells you right away whether Google now gets your content.

  • The page count on the Soft 404 row.
  • Pages you changed to 404. They move to Not found (404). That is the fix working, not a new problem.
  • Pages you kept. Run Test live URL, and click Validate fix once the screenshot shows your content.

If "Validate fix" failed: Validation fails here when the pages still look empty or like errors to Google. Run Test live URL and open View tested page to see the screenshot and HTML Google gets. Words such as "not available" or "out of stock" can make a real page look like an error. See what each validation result means.

Fixes by platform

On Next.js

A route that shows a "not found" message without calling notFound() returns 200, which is a soft 404. Calling notFound() after the page starts streaming also keeps the 200 status. Next.js adds a noindex tag in that case, and its docs say some crawlers label these responses as soft 404s. Call notFound() before streaming starts, outside <Suspense> and loading.tsx, or check the slug in Proxy, so the route returns a real 404. More in Next.js pages not indexed.

On Squarespace

Squarespace's help says a good page can get this when Google reads its text as an error message. Look for phrases such as "no longer available", "item not available", "not in stock", or "does not exist", and reword them. More in Squarespace website not showing on Google.

On Wix

Wix's help says pages without enough content may be reported as soft 404s, and suggests at least 250 to 400 words. Add real text to thin pages, or delete pages you don't need. More in Wix website not showing on Google.

Also common on

This reason is one of the most common on Lovable, Bolt.new, Replit, and Base44. Each guide shows the cause and the fix in that platform's own settings.

Questions

Can an out-of-stock product cause a soft 404?

Yes, when the page says little besides that the item is gone. Keep the full description on the page, and link to similar products. If the product won't come back, redirect it to the closest product or return 404.

How do I see the page the way Google sees it?

In URL Inspection, click Test live URL, then View tested page. You get a screenshot, the HTML, and any JavaScript errors. If the screenshot is empty, your content loads in a way Google can't run.

Related guides

Sources

Checked on October 8, 2026.

Which of your pages have this problem?

Get my free report

Free for up to 500 pages. No card needed. Sign in with the Google account you use for Search Console.

Related problems