Multilingual support using Breakdance & SEO Framework

  • Resolved teahead

    (@teahead)


    6 months, 1 week ago

    Hi There,

    I have read quite a few posts and your own support articles and decided a new question was required to summarise this. I can see you have stated in other posts you can only offer 100% support for MultilingualPress and WPML, with somewhat Limited support for Translatepress with sitemap flushing support missing.

    Our Setup
    We are using Breakdance page builder for our woocommerce store that has many thousands of product pages, we are based in the UK but need strong discovery in the EU so do need multi lingqual support. But we require optimal SEO for EU countries as well as domestically in the UK with good quality translations.

    Translatepress
    Firstly please can you explain with using Translatepress what the effect of sitemap flushing support being missing would be and what complications it would incurr. Is there any other Downsides to Translatepress. This plugin has apparently some support for Breakdance

    WPML
    With this being the most popular Plugin you have advised you support this fully in your support articles and other posts. This is not compatible with breakdance but is compatible with Bricks and many other plugins it would appear. From your experience from an SEO standpoint would WPML and TranslatePress present similar results or would the integration limitations with Translatepress make this less effective.

    Multilingualpress
    You have stated “It is, in our opinion, the only correct method. However, we understand that this solution is not feasible for everyone and that running a multisite can be steeply costly for many” So are you stating that this can offer the most refinement and best results from an SEO site for multiple regions due to the flexibility of having mirrored sites. What would those added costs be vs WPML?

    I hope you can offer some clarity on this as I am trying to make sure we select the best options and want to use the SEO Framework vs other SEO plugins that seemingly seem to offer support for a few more SEO plugins, if that support is good or transparent or not I appreciate is a different matter.

    Kind Regards

    • This topic was modified 6 months, 1 week ago by teahead.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter teahead

    (@teahead)

    Could you also Expand on support for Weglot that claims 100% compatability with all plugins, From an SEO perspective how would Weglot work and is this something that would be supported by SEO framework and function well?

    Plugin Author Sybre Waaijer

    (@cybr)

    Hello!

    Your question is comprehensive and touches on many points. I’d be sitting here for a week writing to expound on all these issues.

    So, could you please elaborate on what you want to achieve so I can work from there?

    To answer a few issues that I can, ‘succinctly’:

    1. I do not know about compatibility with Weglot. We barely get requests about this. The last one was this, where a Weglot developer also chimed in: https://www.ads-software.com/support/topic/weglot-compatibility/.

    2. WPML works great with TSF. We’re going to expand support for this in the next update.

    3. Polylang is annoying to work with because it suffers from a couple of critical bugs (which their author ignores because fixing those bugs doesn’t bring them cash). We hijack Polylang via TSF to implement these bug fixes, and we haven’t heard a single complaint about it. The bug fixes work, but this non-cooperation makes me distrustful about the future of their product. We only support Polylang because I don’t want to let our users down.

    3. TranslatePress should also work with TSF. However, you won’t get translated sitemaps in some server configurations, which some see as a dealbreaker. From a programmer’s perspective, I found it to be less intuitive to work with than WPML and Polylang.

    4. MultilingualPress is the correct method because it separates every language to a new site. It manages this via a WordPress Multisite network, which should then be configured to support subsites. This way, you need only one server and cache one instance of WordPress to support all languages. Then, you treat every site differently: Translating a site isn’t always only updating the language, but sometimes it’s adhering to a culture. Maybe you want to use different colors for different languages, which is impossible with most other solutions. WPML supports this in some regard, but then you need to use String Translations and keep track of all your site’s options.

    5. I manage a multilingual site on a Multisite network without any translation plugins. I simply added a toggle to switch between languages on the homepage. I didn’t even add the hreflang tag. And yet, Google provides the correct version to different audiences: Dutch for Dutch-speaking searchers and English for everyone else. This works well when you set the site language correctly in WordPress’s settings. This is a cheap solution because the site is for a friend, and he didn’t want to spend a dime more than necessary; he just wanted the site to exist. Most people overcomplicate things, and this also works.

    Thread Starter teahead

    (@teahead)

    Hi Sybre

    Thanks for your indepth response, I found that MultilingualPress does indeed seem like the right way to do it properly and the only plugin on a single site solution that has broad compatability appears to be WPML when it comes to other plugins.

    I appreciate knowing that we have two options and we have changed our development to bricks builder instead of Breakdance as breakdance has limited support for WPML or MultilingualPress, Bricks does supposidly work with MultilingualPress and WPML so this gives us at least two options.

    Many thanks again for your time and input, it is very helpful.

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.