Next 13 not-found page returns 200 status code
Unanswered
White-horned horntail posted this in #help-forum
White-horned horntailOP
When I use app router not-found.tsx page returns 200 status code for all dynamic routes. The most strange thing that if I remove loading.tsx it returns 404 status code as expected
6 Replies
Minskin
This seems to be intended behavior (See: https://nextjs.org/docs/app/building-your-application/routing/loading-ui-and-streaming#status-codes)
I would love to see a better description though since I don't understand how it should not affect SEO and also it kind of breaks our alert tooling since it never returns a non 200 code
I would love to see a better description though since I don't understand how it should not affect SEO and also it kind of breaks our alert tooling since it never returns a non 200 code
Minskin
I still don't really get why a 200 status code on a not-found page does not (negatively) affect SEO
Plott Hound
Why would it affect SEO?
Sun bear
I am curious too. Since crawlers are using http response when getting a page, doesn't this mean that receiving 200 status code means that the page is working and they can index it?