next-intl-setRequestLocale-ssg-fix

Incorrect SSG locale rendering happens when getMessages runs before the static context has a defined locale. You fix this by calling setRequestLocale before getMessages in your Next.js server components to enforce the correct language context.

To use setRequestLocale with generateStaticParams, call the function at the start of your server component layout before fetching messages. This ensures the static generation build correctly locks the requested locale context for each generated page.

Yes, next-intl v4 requires explicit locale setting for static site generation. Server components must call setRequestLocale to establish the rendering context, otherwise SSG pages will default to English despite generating correct build output.

Static pages default to English when the locale context is missing during server component rendering. Applying setRequestLocale before retrieving messages resolves this by explicitly binding the intended locale to the static generation request lifecycle.

The limitation of setRequestLocale for static generation is that it must strictly precede getMessages in server components. If called out of order or omitted, the static rendering context fails to apply the intended locale, reverting pages to the default language.