Yoast does not correctly create the meta “twitter: title”

That’s right. By default, Twitter fallback to the Facebook specific open graph meta when there’s no or missing Twitter specific meta and as such, you see the og:title is being used for you as the fallback title when you leave the Twitter title field empty.

Thanke…

I have established in the plugin configuration that “twitter: title” is made up of the post title, a separator and the site title…

If I leave the “twitter: title” field empty in the post, “twitter: title” should be composed of the post title, a separator and the site title… but Yoast doesn’t create “twitter: title”

Is this a plugin bug?

Hi,

We would like some more information.

1. Can you confirm you are using WordPress 5.4.1? You can check by clicking on the W in the top left and selecting About. If you need to update, please check with your host provider.?Please know that if you are using an older version of WordPress Core you may experience unexpected behavior with Yoast.?This guide explains more:?https://yoast.com/why-we-dont-support-old-wordpress-versions/.

2. Can you confirm you are using the most recent Yoast SEO , v14.2? If you update, does the issue resolve?

3. Are all your non-Yoast plugins and themes also updated?

4. Can you provide a URL which highlights the issue?

Hi…

Everything is updated to the latest version.

As you can see in this test post: https://www.viaje-iniciatico.com/prueba/ Yoast has not created “twitter:title”.

Thanke.

@josezabaleta Can you please clarify what your expectation for the output when having the ‘Twitter title’ left blank?

When no value is input for the Twitter title, Twitter will default to using the Open Graph value, but it will not be output as separate metadata. We have more information on this here: https://yoast.com/advanced-technical-seo-social-image-ogimage-tags/

As you can see in the screenshot https://www.viaje-iniciatico.com/yoast.jpg I have configured SEO Title: Title Separator Site title

As you can see in the screenshot https://www.viaje-iniciatico.com/yoast2.jpg I entered Facebook Title: “LALALA” and left Twitter Title empty.

As you can see in https://www.viaje-iniciatico.com/prueba/ og: title = LALALA and twitter:title has not been created.

Therefore, the title that Twitter publishes is “LALALA”

Why hasn’t Yoast created twitter:title = Title Separator Site title?

Hi @josezabaleta,

We understand that this behavior may be unexpected when you leave the Twitter title blank. However, this is by design, not a bug. You can see Twitter’s documentation about which Open Graph tags it uses as a fallback: https://developer.twitter.com/en/docs/tweets/optimize-with-cards/overview/markup.

If your question is related to Twitter cards not showing correctly for your site, please feel free to give us more details since that would be a separate issue.

So if I want the title published by Facebook to be “LALALA” and the title published by Twitter to be the title of the post separator title of the site… I have to enter “LALALA” in the title for Facebook and I have to enter title of the post separator title of the site in title for Twitter.

It would be interesting if leaving the title for Twitter empty, Yoast created twitter:title = SEO title configured in the plugin: https://www.viaje-iniciatico.com/yoast.jpg

Thanke

Hello @josezabaleta

Yes, you will have to define separate titles for Facebook and Twitter if you want for each of them to have separate titles.

If you don’t set a title for Twitter, it will use the Facebook open graph title as a fallback.

If you don’t set a title for Facebook, it will fall back to the SEO title or title in the Search Appearance settings.

Thank you… I conclude with the following idea:

If I don’t set a title for Facebook, it will fall back to the SEO title.

In the same way, if I don’t set a title for Twitter, it would be interesting that SEO title will be used as an alternative.

Best regards.

One last clarification… In my previous message I shared an idea… but I have to admit that it is not mine… This is how Yoast worked not long ago… In my opinion the change has been for the worse…

Best regards.