Skip to content
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

Closed
vibonacci opened this issue Apr 18, 2024 · 5 comments

Comments

@vibonacci
Copy link

vibonacci commented Apr 18, 2024

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 on http://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.

  i18n: {
    vueI18n: './i18n.config.ts',
    baseUrl: process.env.FRONTEND_URL,
    langDir: 'translations',
    lazy: true,
    locales: [
      // https://i18n.nuxtjs.org/docs/guide/seo#feature-details
      {
        code: 'en',
        iso: 'en-US',
        file: 'en.js',
        isCatchallLocale: true,
      },
      {
        code: 'nl',
        iso: 'nl-NL',
        file: 'nl.js',
      },
    ],
    defaultLocale: 'en',
    // https://i18n.nuxtjs.org/docs/guide#strategies
    strategy: 'prefix_except_default',
}

Additional context

No response

Logs

No response

Copy link

Would you be able to provide a reproduction? 🙏

More info

Why 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 needs reproduction labeled issues don't receive any substantial activity (e.g., new comments featuring a reproduction link), we'll close them. That's not because we don't care! At any point, feel free to comment with a reproduction and we'll reopen it.

How can I create a reproduction?

We have a couple of templates for starting with a minimal reproduction:

👉 Reproduction starter (v8 and higher)
👉 Reproduction starter (edge)

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:

@carlosvaldesweb
Copy link

X2 Also happen to me

@kazupon
Copy link
Collaborator

kazupon commented Jun 24, 2024

Closing due to inactivity.
Please open a new issue with a reference to this one if you can follow up with more information.

Thanks!

@kazupon kazupon closed this as completed Jun 24, 2024
@WooHoo-Wu
Copy link

X2 我也遇到过这种情况

@WaldemarEnns
Copy link

I guess I have a reproduction for this at #3099

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants