Can SEO-Framework works with GTranslate and TranslatePress-Multilingual?

Hello!

No plugin can do that for GTranslate, because it translates the page after it’s rendered via an external service.

As for TranslatePress, TSF is compatible, but you cannot set language-specific descriptions or titles. However, TSF will generate language-specific descriptions and titles with TranslatePress.

Polylang and WPML copy pages for translation; this allows every translation to have a unique post ID and, because of that, unique metadata. This will enable you to set custom titles and descriptions for every translated page.

To learn more, see https://tsf.fyi/kb/translation-plugin-compatibility.

thanks!

As for TranslatePress, TSF is compatible, but you cannot set language-specific descriptions or titles.

?TranslatePress?Multilingual?: PRO — SEO

Pro Add-ons (available in the premium versions only)

SEO Pack – lets you translate meta information (like page title, description, url slug, image alt tag, Twitter and Facebook Social Graph tags & more) for boosting your multilingual SEO and increase traffic. Works with all popular SEO plugins.

.

However, TSF will generate language-specific descriptions and titles with TranslatePress.

TSF automatically translate descriptions and titles from my site main language

or create title from post Heading? description from what?

Hello!

SEO Pack doesn’t work with TSF, even though it would’ve been the easiest for them to add support.

TSF generates metadata from various places. Most prominently, the post title, excerpt, and content for titles and descriptions. But it also uses the post’s featured image, password protection, assigned categories, etc., for other metadata.

Google, Yandex, Bing, etc., will ignore that metadata if they find something more helpful for the search engine user about the page.

SEO Pack doesn’t work with TSF…

Thanks for answering!

TSF does not generate metadata for the SEO Pack – obviously, but you can probably write them manually (well, as we usually optimize the page, waste time, write a lot of text).

I haven’t bought the SEO Pack yet, it’s not relevant for me yet.

I have now installed SEO Framework и  TranslatePress Multilingual on my website.

In the English translation of the page, NO ONE line of HEAD block <!– The SEO Framework by Sybre Waaijer –> is translated into English or generated in any way. Everything is exactly the same as in the Russian version!

What’s the point of the SEO Framework then?

only plugin comment and author name are automatically translated:

<!– The SEO Framework Создано Сибрэ Вайэр –>

…

<!– / The SEO Framework Создано Сибрэ Вайэр | 4.24ms meta | 44.66ms boot –>

in English:

<!– The SEO Framework by Sybre Waaijer –>

…

<!– / The SEO Framework by Sybre Waaijer | 4.58ms meta | 42.28ms boot –>

.

And before the HEAD block <!– The SEO Framework by Sybre Waaijer –>

<title>…</title>

also in Russian!

• This reply was modified 1 year, 6 months ago by v0van.
• This reply was modified 1 year, 6 months ago by v0van.
• This reply was modified 1 year, 6 months ago by v0van.

Hi again!

I see you’re trying other plugins to see which works best for you.
If you ever get back to TSF, feel free to follow up ??

I was mistaken when I wrote this:

However, TSF will generate language-specific descriptions and titles with TranslatePress.

I thought TranslatePress translated the content data, but I believe they’ve changed that over the years to translate the entire HTML page. We rarely get support requests about their plugin, so I wasn’t aware of these changes. Sorry about that.

They did right to leave the metatags alone when translating the page; transforming those would cause issues in many cases.

Integrating with SEO Pack would likely resolve the issue, but they control that plugin.
So, I’ve proposed integrating support within The SEO Framework for a future update: https://github.com/sybrew/the-seo-framework/issues/630.

Thank you for the feedback!

So, I’ve proposed integrating support within The SEO Framework for a future update:?https://github.com/sybrew/the-seo-framework/issues/630.

– – –

TranslatePress translates 1 paragraph per page. Moreover, it is impossible to translate a menu or widget for the entire site. And it makes no sense to translate on every page.

Therefore, TranslatePress is suitable only for translating landing pages, and I do not plan to work with TranslatePress.

Exist

WPGlobus and Polylang for BLOG,

gtranslate for FORUM (automatic translation),

WPML for Woo.

– –

RU:

TranslatePress переводит по 1 абзацу на странице. Причём перевести меню или виджет для всего сайта невозможно. А переводить на каждой странице смысла нет.

Поэтому TranslatePress похдходит только для перевода лендингов, и я с TranslatePress работать не планирую.

Есть

WPGlobus и Polylang для БЛОГ,

gtranslate для ФОРУМ (автоматический перевод),

WPML для Woo.