Hello!
Thank you for notifying me about this. I used the wrong call there when I was migrating the entire codebase. I just fixed it for the next update. There’s nothing you need to do; only the og:locale output is missing from what is calling it, which is something that can be inferred from the document language. You can safely ignore the message.
I plan to have this update out in the first week of June.
Still, that file should never be loaded on most typical installations (that’s why I didn’t find the issue earlier). It appears your site is using outdated code from The SEO Framework. When this code is called, we send deprecation notices to urge developers to update their code, risk their code no longer working, or even crash the site in a future update.
The code in question is probably from this plugin: https://wordpress.org/plugins/accelerated-mobile-pages/. I already submitted an issue to help resolve this issue: https://github.com/ahmedkaludi/accelerated-mobile-pages/issues/5603.
But, I cannot recommend using AMP at all. Not because of the plugin but because of Google. It’s proven to cause a loss of revenue, has been involved in many scandals, and it isn’t faster than a responsive theme. Most major news sites are also moving away from it because AMP sites have no longer received preferential treatment from Google since 2021.
Thread Starter
zicoxx
(@zicoxx)
Thanks again for the reply.
Very clearly the warning message derives from the support for obsolete instructions regarding AMP for WP so they will have to update the TSF while you fix them.
I am pleased to have been able to help improve your product and I will continue to do so if I have the opportunity to report.
While regarding AMP I perfectly agree with you, and on many sites that I manage (I am a medium/high level webmaster) I have eliminated support in agreement with the publishers.
But on one site in particular, where I started using TSF with subscription, there is a rather strange situation that doesn’t allow me to disconnect AMP: I’ll tell you quickly because I’d like to have an opinion.
On this site where AMP is still present there is excellent indexing and positioning on a very important keyword in Google News and when I tried to disconnect AMP everything went down until I reactivated AMP. This stopped me because obviously we were talking about a significant drop in traffic. So until I have a clear reason, within the limits of what we can understand from our side, I am forced to keep AMP standing.
Then add the annoying SERP fluctuations that send one to a madhouse, in short, unfortunately I cannot safely disconnect AMP and this makes me sad
If you want to tell me what you think I would be happy
Hi again!
A drop in URLs (in this case, AMP) can cause a drop in ranking and clicks. It’d be best to 301-redirect a bunch of AMP URLs to their non-AMP counterparts and see if that affects ranking. 301-redirects tell search engines to look elsewhere (with about a 15% drop in ranking, temporary).
If the results for the redirected pages look promising, you could try redirecting the entire site from AMP to non-AMP.
To learn more, please see https://moz.com/learn/seo/redirection.
