-
-
Notifications
You must be signed in to change notification settings - Fork 481
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generated canonical links do not point to main language, but to current language #2925
Comments
Would you be able to provide a reproduction? 🙏 More infoWhy do I need to provide a reproduction?Reproductions make it possible for us to triage and fix issues quickly with a relatively small team. It helps us discover the source of the problem, and also can reveal assumptions you or we might be making. What will happen?If you've provided a reproduction, we'll remove the label and try to reproduce the issue. If we can, we'll mark it as a bug and prioritise it based on its severity and how many people we think it might affect. If How can I create a reproduction?We have a couple of templates for starting with a minimal reproduction: 👉 Reproduction starter (v8 and higher) A public GitHub repository is also perfect. 👌 Please ensure that the reproduction is as minimal as possible. See more details in our guide. You might also find these other articles interesting and/or helpful: |
X2 Also happen to me |
Closing due to inactivity. Thanks! |
X2 我也遇到过这种情况 |
I guess I have a reproduction for this at #3099 |
Environment
"@nuxtjs/i18n": "^8.3.0"
"nuxt": "^3.11.2"
Reproduction
N/A
Describe the bug
Given the config below, the generated canonical link for the page in the default lang
en
onhttp://localhost:3000
will be correct:<link rel="canonical" href="http://localhost:3000/" data-hid="5cca6f5">
However, switching to the
nl
locale, the generated canonical link will point to the URL with /nl appended:<link rel="canonical" href="http://localhost:3000/nl" data-hid="5cca6f5">
The canonical link should point to the main language link as these pages are considered the same for SEO purposes, only have different language.
Using the
prefix_except_default
strategy.Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered: