---
title: "Discussion on \"When Every URL Returns 200: How Single-Page Applications Create Soft 404s\" | Hashnode"
description: "Discussion on \"When Every URL Returns 200: How Single-Page Applications Create Soft 404s\". How incorrect status codes in single-page applications create soft 404s—and how developers can detect and fix them."
url: "https://hashnode.com/posts/when-every-url-returns-200-how-single-page-applications-create-soft-404s/6ac4e9442272a07ff9adf921"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [When Every URL Returns 200: How Single-Page Applications Create Soft 404s](https://logixercreatives.hashnode.dev/when-every-url-returns-200-how-single-page-applications-create-soft-404s?utm_source=hashnode&utm_medium=feed)

How incorrect status codes in single-page applications create soft 404s—and how developers can detect and fix them.

Oct 6 · 9 min read · logixercreatives.hashnode.dev  
Read the article

-   [#technical-seo](https://hashnode.com/tag/technical-seo)
-   [#javascript](https://hashnode.com/tag/javascript)
-   [#web-development](https://hashnode.com/tag/web-development)
-   [#http](https://hashnode.com/tag/http)
-   [#single-page-applications](https://hashnode.com/tag/single-page-applications)

## Written by

[Logixer reatives](https://hashnode.com/@logixercreatives)

@logixercreatives · Dubai, UAE

  
[View profile](https://hashnode.com/@logixercreatives)

Technical SEO, Web Development and Digital Growth Insights for UAE Businesses

Logixer Creatives shares practical insights on technical SEO, local SEO, web development, website performance, structured data, content marketing and ecommerce. We help businesses in Dubai and across the UAE improve search visibility, strengthen their digital presence and create better online experiences. Visit: https://logixer.in/

## Responses 1

Markdown supported · ⌘↵ to post

[Jonas](https://hashnode.com/@jonasb)

[Oct 8](https://hashnode.com/posts/when-every-url-returns-200-how-single-page-applications-create-soft-404s/6ac4e9442272a07ff9adf921/comment/6ac74a751f0b440f5fba9943)

I’d add a normal GET request alongside curl -I in the test. -I sends HEAD, so it checks the headers but doesn’t give you the page body.

Keep the GET status, redirect chain and returned HTML together for a valid page and a missing one. That catches cases where HEAD and GET are handled differently, and makes it easier to tell whether the 200 is actual page content or the fallback shell.

The existing route-state table is a good basis for that regression check.
