A soft 404 does not automatically mean your SaaS post should be deleted. If the article is meant to exist but its public page is empty or shows an error, restore the article. If you intentionally removed it with no suitable replacement, return a real 404 or 410. If it moved, redirect to the matching page. Google’s soft 404 guidance makes the choice depend on what happened to the content—not on the report label alone.
Check the public page before changing its status
Start with the exact URL listed in Search Console. Open it as a visitor and note whether the intended article appears, an error message replaces it, or the page is nearly empty. Have your developer check the HTTP response for that same URL. A page can return HTTP 200 while its content looks like a missing page; Google also says a valid page may be classified as a soft 404 when important resources fail to load and its rendered content is empty, sparse, or dominated by an error.
Then inspect the URL in Search Console. Compare its last crawl date with any recent fix, and run Test live URL to examine the current response and rendered page, including the screenshot and loaded resources where available. The URL Inspection tool separates information about Google’s indexed version from its live test; the Page indexing report may still reflect a crawl that happened before your change.
Choose the fix that matches the article’s fate
Use the editorial decision—keep, remove, or move the article—to choose the response. Google recommends restoring a still-valid page that renders incorrectly, returning 404 or 410 when content is gone without a similar replacement, and using a 301 redirect when it moved or has a suitable replacement. A useful-looking error page still needs a real error status if the article is gone; redirecting every removed post to the blog homepage is not a substitute for identifying a matching destination.
For example, suppose the fictional URL https://example.com/blog/integration-guide returns 200 but displays only its heading because the article body fails to load. The team still wants that guide online, so the developer’s job is to repair the content-loading failure and confirm that the public URL returns the full guide with a 200 response—not change it to a 404. If the team instead retired the guide without a replacement, it should serve 404 or 410. If the guide now lives at the fictional URL https://example.com/blog/integrations, a 301 to that matching article is the appropriate choice.
| What happened | What to ask your developer to ship | What to check afterward |
|---|---|---|
| The article should still exist, but its body is missing or broken. | Restore the intended article and fix the loading or rendering failure. | The public URL returns 200 and displays the substantive article. |
| The article was removed with no similar replacement. | Return HTTP 404 or 410 instead of a 200 error page. | The old URL returns the chosen error status. |
| The article moved or has a suitable replacement. | 301 redirect the old URL to the matching new page. | The redirect reaches a working destination with the expected content. |
Give your developer a testable request
Send the exact affected URL, its observed HTTP status, what a visitor sees, what Search Console’s live rendering shows, and the decision from the table. For a retained article, provide the intended copy or its source and identify the missing body or loading error. For a removed article, say explicitly that no replacement exists. For a moved article, provide the exact new URL and confirm that it answers the old page’s purpose. This lets the developer change the page or response you actually need, rather than adding arbitrary text to satisfy a report.
Ranks says its articles live on your own blog and that you can review and edit them before publishing. If the affected post came from Ranks, the intended article is a useful reference for checking what the public page ought to show. The response, routing, and live rendering still need to be checked on your website; Ranks does not decide how Google classifies the URL.
Verify the release, then check Search Console again
After the change is deployed, open the old public URL and verify its actual response and visible result. For a restored article, confirm the body loads and run Test live URL again to see what Google’s inspection tool can render. For a redirect, check both the old URL’s redirect and the destination. For an intentional 404 or 410, confirm the status rather than expecting the old URL to become indexed: Google considers a 404 for a removed page without a replacement a legitimate reason for that URL to remain out of its index.
Only after the live site is correct should you judge the next Search Console finding. A successful live test checks the page now; it does not prove Google has indexed the change. For a restored article you want indexed, an eligible Search Console property owner or full user can request indexing, but Google says recrawling can take days to weeks and a request does not guarantee inclusion. Revisit the URL Inspection crawl date and report after Google has had time to recrawl.
If production already returns a genuine 404 for a post that should exist, use the Next.js post-404 guide if that is your site’s framework. If the article works but you are diagnosing search visibility more broadly, use the blog indexing guide.



