Hi,
Thanks for the follow-up with that information. Unfortunately, we are unable to reproduce the issue and what further compounds it is that Google’s on testing tools are able to find the right title. So there is something about the Google Analytics code such as its location or how it is built that is causing an issue.
As Yoast is outputting the right title and Google’s Search Engine is able to find it our ability to support this issue is limited. What we can say is to
1. AMP has an open issue related to Google Tags here https://github.com/ampproject/amphtml/issues/30176. We are not sure if that matches but try removing the Google Tag part of the Analytics Code and see if the issue resolves.
2. Are you able to move the code up to say the middle part of the page or the top part? Do the results change?
3. Are all your non-Yoast plugins and themes also updated?
4. We had another recent release. Can you confirm you are using the most recent Yoast SEO, v15.7? If you update, does the issue resolve? We ask as new versions of Yoast contain some AMP specific functionality.
5. If you deactivate SiteKit and move that analytics code into some other plugin does the issue resolve? For example, if you go to AMP-Settings there is an analytics spot there to enter in the AMP specific analytics. If you move it there does the issue resolve?
NOTE: AMP pages require a different set of analytics then what is found on regular pages. We checked the topic here https://www.ads-software.com/support/topic/amp-visits-in-ga/ and it is not clear to us if the specific AMP analytics are in use. Can you confirm? This guide explains more: https://amp-wp.org/documentation/getting-started/analytics/.
If the code is correct and implemented correctly for AMP and the code is just firing the Google Analytics code and nothing else AND everything else is updated and moving the code around still all fails to resolve it, ie you deactivate Yoast SEO and issue is resolved.
Based on the information you provided, we expect this to be an issue. We’re actively using the bug tracking on our GitHub repository so your best next step would be to create a new issue for our developers at https://github.com/Yoast/wordpress-seo/issues/new. You will need an account to create a new issue. If this is your first bug report, please check out: https://kb.yoast.com/kb/how-to-write-a-good-bug-report/.