Olá Josivandro,
Thanks for getting in contact with us, my name is Fellyph and I will try to help with your query, I do speak Portuguese as well. If you prefer, we can talk in Portuguese as well.
On the plugin side, I have tested the AMP content and the structure data. They are valid, and the search is behaving as expected, showing the right titles:
https://recordit.co/wFGvpdn0mU
But there is one unusual item that is the canonical property inside your posts pointing to your homepage.
Have you installed any plugin that changes the canonical link property? I would check what is changing it and set the correct info for the non-AMP version from the related post, and check if Google News will update the listing. If not, I would get in touch with the Publisher Help Center, once the results are different between the app and web version.
If you have any questions, please let me know
The canonical property code was manually installed in the child theme’s header file, without using a plugin. This is because the site has a second parked domain that currently redirects to this site. At the moment I disabled this redirect at least on the other pages of the site and it may be that the error is there. Maybe he could be giving some kind of conflict that ends up giving rise to this problem.
Hi @josivandroavelar,
Thanks for getting back, canonical property is essential for making your content discoverable and linking duplicated content.
That is why it is important to link the related non-AMP URL(check here some guidelines).
The plugin will handle automatically, changing it manually can create some side effects how other tools fetch your content.
But related to the second domain, it has the same content as the website mentioned?
Yes, it has the same content.
Hi @josivandroavelar,
Let me see if I understand, you have:
1. https://josivandroavelar.com.br/post-1
2. https://josivandroavelar.com.br/post-1?amp=1
3. https://site2.josivandroavelar.com.br/post-1
If it is like the example above, I’m considering josivandroavelar.com.br to be the main content. I would do the following structure:
- The main version(1) point to AMP version(2)
- AMP version(2) point to the main version(1)
- Secondary domain(3) point to the main version(1)
The rel=canonical Indicates the main source, but Googlebot can choose a different page, based on different factors, more info on Consolidate duplicate URLs, also is important to reference the same content to avoid google search penalize your pages(Avoid creating duplicate content).
In some SEO plugins, for example, Yoast SEO you can set up the canonical property
I hope that would help you
More or less that. In this case, there is a parked domain, which is josivandroavelar.com (without br), so there are two distinct domains:
https://josivandroavelar.com.br/post-1
https://josivandroavelar.com/post-1
And the canonical URL, in this case, is josivandroavelar.com.br, so the results for josivandroavelar.com, in a way, don’t figure in the search – at least all the results pointed to a canonical URL.
Hi @josivandroavelar,
I have tested your domain .com, for example:
The address https://josivandroavelar.com/pesquisas-do-ano-no-google-o-quanto-fomos-curiosos-em-2021-parte-2/ does redirect to the https://josivandroavelar.com.br/pesquisas-do-ano-no-google-o-quanto-fomos-curiosos-em-2021-parte-2/
On this case 301 take care of it, you don’t need to use any custom canonical property just the default behavior from the plugin.
Pick one of those URLs as your canonical URL, and use 301 redirects to send traffic from the other URLs to your preferred URL. A server-side 301 redirect is the best way to ensure that users and search engines are directed to the correct page. The 301 status code means that a page has permanently moved to a new location.
I managed to solve the problem by adjusting the canonical tag and now the post titles have returned to appear normally from the next ones and the ones that are updated.
In fact, the one in the header conflicted with a canonical tag that already existed, which has already been fixed.
Olá @josivandroavelar,
Great to hear that, once solved, I will close this topic.
If you have any question, please let me know.
