-
SummaryI am using Next.js version 14.1.4 with the "app router" feature. In my project, I need to dynamically generate meta tags such as title, description, and keywords for dynamic pages. I am using the "generateMetadata" function for this purpose. On the main page, I manage the meta tags statically within a "metadata" object. When listing products, I update the SEO information for the category using the "generateMetadata" function. Using console.log statements, I have confirmed that the data is being fetched server-side, so there is no issue with that. Problem: When I navigate from the main page to subpages using soft navigation (i.e., using the component), I notice that the meta tags in the browser do not update. Instead, the meta tags from the main page remain persistent. However, if I perform a hard refresh (F5) on any dynamic page, the meta tags are correctly updated. The issue seems to be that the meta tags do not update during soft navigation.
Could anyone help me understand why the meta tags are not updating during soft navigation and how to resolve this issue? Thank you! Additional informationNo response ExampleNo response |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 4 replies
-
Hello Next.js community, I wanted to follow up on the issue I posted yesterday. I was able to resolve it by updating to a newer version of Next.js. When I started the project, I was using version 14.1.4. After investigating whether there were any changes in the newer versions that could address the issues I was experiencing, I found that updating from version 14.1.4 to 14.2.0 resolved the problem. I observed that the issue was fixed without needing to make any changes to my code related to this matter. Thank you for your support! |
Beta Was this translation helpful? Give feedback.
-
@ekiyak I am also facing the same issue and I am using the version 14.2.5. Is there any other fix you did? |
Beta Was this translation helpful? Give feedback.
Hello Next.js community,
I wanted to follow up on the issue I posted yesterday. I was able to resolve it by updating to a newer version of Next.js. When I started the project, I was using version 14.1.4. After investigating whether there were any changes in the newer versions that could address the issues I was experiencing, I found that updating from version 14.1.4 to 14.2.0 resolved the problem.
I observed that the issue was fixed without needing to make any changes to my code related to this matter.
Thank you for your support!