Does the hreflang x-default affect the outcome in linkedin post inspector?

[Michkael]

Hi guys,

General Info
I have a website with two set languages: default (en) and italian (it).
I have used the multi-language field.
Moreover I am using the awesome new module "SEO maestro" to populate the metadata.
At the moment I have not set any auto-redirect code based on the browser language.

Problem on linkedin
I was trying to share a new post I wrote but when I test the url on linkedin post inspector I get:
We detected a redirect loop while following the redirect trail from https://brightnode.io/, so we will not scrape this content.

The website appears twice, with the same language.

What I see on the source code of the page
So when I look at the source code I see that both x-default and "en" exist:

<link rel="alternate" href="https://aaa.io/en/blog/the-future-o.../" hreflang="en">
<link rel="alternate" href="https://aaa.io/en/blog/the-future-o.../" hreflang="x-default">
<link rel="alternate" href="https://aaa.io/it/blog/il-futuro-o.../" hreflang="it">  <meta name="viewport" content="width=device-width, initial-scale=1">

Now i am wondering if the hreflang is affecting the outcome of linkedin or what do I have to change to avoid this mistake.

I hope I gave all the details necessary.
Thank you for your help.

Michael

[dragan]

I don't know anything about the linkedin post inspector. But I find it strange that you don't use a lang attribute in your html tag.

Also, when I go to your sitemap.xml and view e.g. https://brightnode.io/it/projects/cosquare/ in my browser, I see this in the html head:

<link rel="alternate" href="https://brightnode.io/en/projects/cosquare/" hreflang="en">
<link rel="alternate" href="https://brightnode.io/en/projects/cosquare/" hreflang="x-default">
<link rel="alternate" href="https://brightnode.io/it/projects/cosquare/" hreflang="it">

The last one is not needed. I am already on the Italian page, so why does it generate a superfluos hreflang="it" on that page?

The same is true for that page's English counterpart: https://brightnode.io/en/projects/cosquare/

As for the 301 redirect, I don't know what's causing this. And with all these issues, it's hard to tell what exactly is caused by the SEO Maestro module, or your own code-bits in your template (or some module configs).

If you find issues with the module, you should post it in the module's support forum thread.

btw, the explanation of what hreflang=x-default is supposed to be, and how it's meant to be used seems quite clear, according to this Google article: https://webmasters.googleblog.com/2013/04/x-default-hreflang-for-international-pages.html

 

[wbmnfktr]

 

[Michkael]

@dragan thank you for your answer.

Can you suggest me what and in what order should I check?

I can say that those lines are generated by the Seo Maestro because when I have removed the field from a page, the lines disappeared.

On its page I have found that the hrelang are common metadata that are generated automatically and they cannot be managed by the field.
I managed to only load the opengraph and metadata I am interested in, but now I have a question: How important are hreflang for a multilanguage website? How can I manually populate them?

Thank you

[Michkael]

Now if you check the hreflang does not appear anymore on the metadata but the 301 redirect is still there....
 

[Michkael]

This morning it was working, just before I set the sitemap.xml using the SEO Maestro. Before I was using the XML markup sitempa module.
The fact that the sitempa is fed to search console could affect anway?

[Wanze]

2 hours ago, dragan said:

The last one is not needed. I am already on the Italian page, so why does it generate a superfluos hreflang="it" on that page?

 The same is true for that page's English counterpart: https://brightnode.io/en/projects/cosquare/

That is not true: https://support.google.com/webmasters/answer/189077?hl=en

Quote

Each language version must list itself as well as all other language versions.

@Michkael

The meta tags added by SeoMaestro do not perform any redirects, there must be another issue either on server level or some code in ProcessWire performing the redirects.

[Michkael]

Thank you @Wanze.

Could it be that I haven't taken any precaution passing from a single to a multi-language website? Could it be that the previous url redirect to the new and it starts looping?