Disable streaming rendering for google bots and clients that do not support http2 streaming

[Fredkiss3]

Describe the feature you'd like to request

Referencing this discussion on the documentation https://beta.nextjs.org/docs/api-reference/notfound#thread-id=qPXdO, when we use notFound on a server component and inspect the result on google bot or a simple crawler the response returned is a 200 OK, while it should maybe return a 404.

Describe the solution you'd like

Before serving the request, Nextjs could inspect the user-agent of the request and if the agent cannot support streaming :

• notFound should return a 404 Not Found response code
• And redirect should return a 302 Found response code

Describe alternatives you've considered

No alternatives yet.

[balazsorban44]

Hi, this is just not implemented yet. 👍

[Fredkiss3]

It's is the roadmap i suppose ?

[Sharpiro]

Are there any issues tracking this yet?

[Fredkiss3]

I think the canonical solution here is to use notFound & redirect in generateMetadata() there it sets the correct HTTP codes.

The redirect() and notFound() Next.js methods can also be used inside generateMetadata.

from the docs : https://nextjs.org/docs/app/api-reference/functions/generate-metadata#returns

[steebchen]

This is a great temporary workaround but I don't believe it is the proper solution. My biggest concern is that server errors aren't caught this way, and could even go completely unnoticed. Say google scrapes your site, but your data fetching fails; it would always return 200 OK with an error being rendered there which Google would try to index. In this case it's important to return a 500 so Google doesn't index and re-tries instead. I think it would be better to re-open the discussion.

[steebchen]

Plus, it looks like this doesn't work in all cases right now: #60351

[steebchen]

Another issue is that any server error will not return a 500, but always a 200. I guess there's not really a fix as it's just how streaming works, but I wanted to add this here as a good-to-know. In my opinion, this feature request should be re-opened.

[guillaume-fr]

Agreed. Streaming can be nice and maybe you want that in some case but I'd like to have an option to enable:

• plain old SSR, typically for bots with no JS support
• separate requests for dynamic content so each may generate its HTTP response. Useful when your architecture requires interoperability with other solutions (security solutions, reverse proxy, observability/logs)

[zubkov7]

Hi! Is there any updates or plans to integrate in future versions?