You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The RecipeJsonLd component currently does not support the nutrition field from schema.org/Recipe. This makes it difficult to include structured nutritional data for recipes, which is important for both SEO and user experience
Describe the solution you'd like
I’d like to be able to pass a nutrition object to the RecipeJsonLd component, in line with the NutritionInformation structure. This would allow sites to include details like calories, fat content, protein, etc., as part of the structured data.
Describe alternatives you've considered
Right now, the only alternative is to create a custom JSON-LD script manually, outside of next-seo, which loses the benefit of having a centralized and typed SEO configuration.
Is your feature request related to a problem? Please describe.
The
RecipeJsonLd
component currently does not support thenutrition
field from schema.org/Recipe. This makes it difficult to include structured nutritional data for recipes, which is important for both SEO and user experienceDescribe the solution you'd like
I’d like to be able to pass a
nutrition
object to theRecipeJsonLd
component, in line with the NutritionInformation structure. This would allow sites to include details like calories, fat content, protein, etc., as part of the structured data.Describe alternatives you've considered
Right now, the only alternative is to create a custom JSON-LD script manually, outside of
next-seo
, which loses the benefit of having a centralized and typed SEO configuration.Additional context
Here’s the relevant schema.org documentation for Recipe and NutritionInformation.
This is also supported by Google as part of Recipe structured data.
The text was updated successfully, but these errors were encountered: