veta-marketing-i18n-content

Bilingual SEO metadata for Next.js marketing pages requires generateMetadata to output localized canonical URLs and alternates.languages for both ES and EN locales. This ensures search engines correctly index the distinct public routes without duplicate content conflicts.

Structuring next-intl JSON translation files for ES and EN marketing content requires maintaining identical namespace and key structures in both locale message files. This synchronized mapping guarantees no marketing strings are left untranslated when rendering localized landing pages.

Correct i18n routing for Spanish and English marketing slugs uses internal route keys from the routing configuration instead of hardcoded locale slugs. This keeps URL formation consistent, applying no prefix for ES and a `/en` prefix for English pages.

You need to add rewrites or 301 redirects in next.config.ts when the public marketing slug does not match the internal folder name. This resilience mapping ensures users reach the correct localized page even if the route structure changes.

This approach supports automatic sitemap generation by requiring the sitemap configuration to explicitly include both ES and EN URL variants. This ensures complete search engine coverage for all indexable localized marketing pages.

Next.js internationalized pages serve untranslated marketing strings when the ES and EN JSON translation files have mismatched namespace or key structures. Synchronizing these keys ensures the rendering engine finds the correct localized content.