-
-
Notifications
You must be signed in to change notification settings - Fork 55
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
Add an additional link tag with hreflang x-default to improve locale detection fallback #161
Comments
Thanks for submitting this feature request! I'm wondering how much control the user needs for this value. |
Glad you like the idea 🚀 ! I don't need the use case with a specific neutral page having language selector, but it should be done for sure. I'm not sure how to make good UI/UX. As global option seems good to choose between:
No need for per-bundle settings if so. What do you think? |
Yep that sounds like a plan. So that would be an extra select input (dropdown) in this section: And the values of that select input can be:
And when somebody selects the Other option an extra text input field should show in which the user can put the path of their choice. And yeah just have disabled be the default makes sense. That would make this backwards compatible as well. @RomainGueffier Do you want to make this contribution? |
@boazpoolman deal! I will create PR soon. Do you have any default |
The repo has eslint configured for all linting and code formatting. |
Hello, thank you for this really useful plugin !
Feature request
Summary
Add a
link
tag withhreflang="x-default"
Why is it needed?
Ahref SEO software rises advice to enable link tag with hreflang x-default value for default language fallback.
Google also mentions it: https://developers.google.com/search/blog/2023/05/x-default?hl=en
It is not necessary nor seems to penalise seo. But I would like to know your opinion on it?
Suggested solution(s)
Add the additional
link
tag withhreflang="x-default"
value from default locale pathname.I could contribute if needed 😃
The text was updated successfully, but these errors were encountered: