Bad for SEO + no support = don’t buy this plugin

  • bloeise

    (@bloeise)


    2 years, 5 months ago

    NO SUPPORT
    I have used the paid version of TranslatePress for several years. This year my site was renewed, which caused some issues with TranslatePress settings. I reported these, got response weeks laters and not all issues addressed.

    A month later, TranslatePress changed its paid plugin. They failed to mention that the setting of the standard language changed, and so Google thought my business website was only in the translating language. Another support request, also asking them to solve an older issue. No response.

    17th of November it turns out Yoast SEO is adding the *wrong* canonical links to my original pages: it leads to the translated pages, but without the subfolder, so the link is faulty and can’t be indexed. Where does Yoast get this canonical link? From TranslatePress. And despite having a paid version that should give some level of support, no reply. And for a whole week my traffic hits rock-bottom. This cant go on for another week, so I decided to unplug TranslatePress.

    BAD FOR SEO
    If you have the paid version of TranslatePress and you have had a dive in SEO traffic? Check what TranslatePress has been doing to your site. Check if your standard pages have a language set, check the canonical link on each page, check in Search Console what Google thinks of the page. Especially, check the report double-page, not indexed. If you can’t fix any of these SEO problems in the settings, you’ll need support from TranslatePress, and you won’t get it.

    DON’T BUY THIS PLUGIN
    For quitting the paid version of TranslatePress, please follow these steps:
    1. Go to 2checkout that handles TranslatePress payments (site is secure.2co.com with sub directory /myaccount/. Can’t find the link? Search your email for Translatepress to find an invoice, that will contain this link). Give your email address to receive a login link.
    2. Go to My Products. You’ll see the subscription of TranslatePress as active. Press the button to stop the auto-renewal. Give your reason and press the button that says stop (left white button, not the big blue button).
    3. Read the refund policy of TranslatePress and apply if applicable, see details TranslatePress site (google TranslatePress + refund + policy)

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support Denis

    (@sdenis)

    2 years, 5 months ago

    Hi Thomas,

    We thank you for your feedback.

    Due to the variety of plugins from the WP market, peculiar conflicts may appear from time to time as TranslatePress interacts with all the plugins that bring any changes to the front-end.

    Even though we try to respond as quickly as possible to tickets, sometimes the waiting time can exceed 24 hours.
    And since we work Monday to Thursday, the wait time has unintentionally increased in your case.
    However, for the wait time, we apologize.

    As far as we can see, TranslatePress does not process canonical URLs at all in your setup, so, the issue has been escalated to the development team for further investigation.

    Also, the problem you mentioned seems to be similar to this one:
    https://github.com/Yoast/wordpress-seo/issues/15141

    But I’m sure though that if you want to give the plugin a second chance, we’ll get to the bottom of the problem.

    ewatrinet

    (@ewatrinet)

    2 years ago

    Hey there,

    I faced the exact same issue a few days ago (I run Translate Paid Personal Plan using FR>ENG language).

    1/ When you translate and save the slug of a page, it changes the canonical URL of the original page, while correctly creating a canonical URL for the translated page.
    2/ When you edit and update your original post, it gets your original canonical URL back, but the canonical URL of translated version…changes as well. In a word, it’s currently impossible to get a stable and satisfactory state for multiple languages. That kills the very reason why we purchased this plugin in the first place, that is get more traffic (not less).

    I am still trying to fine a workaround (the Github thread https://github.com/Yoast/wordpress-seo/issues/15141 seems indeed to address a similar bug) but in the meantime, I decided to follow @bloeise advice and unplug TranslatePress from my website, because we cannot afford unindexing URLs and losing key SERP rankings.

    kozmonauta

    (@kozmonauta)

    1 year, 11 months ago

    @ewatrinet this is very worrying.
    Has the TranslatePress team responded with a solution yet?

    kozmonauta

    (@kozmonauta)

    1 year, 11 months ago

    @ewatrinet I posted it here in the support area, in case you want to follow and detail your report better.

    https://wordpress.org/support/topic/serious-seo-problem-in-translatepress/

    Thanks.

    Plugin Support Alex

    (@alexcozmoslabs)

    1 year, 11 months ago

    Hi,

    @ewatrinet There is no issue with canonical strings from what I’ve tested. I used the latest versions of our plugin and addon and tested them with Yoast SEO and RankMath, both in the latest versions.
    As my colleague already specified, TranslatePress doesn’t create canonical at all. Those are added by the SEO plugins probably, but they use the translations made with our product. You can create a new post, and translate its slug, then you will see in additional language, the canonical is translated also with the same string. Changing the slug of the original post, will not affect the translated slug, which will remain with the same translation, thus the canonical will remain with the same translation as well. Changing the slug translation will also change the translation of the page canonical in that specific language. There is no issue with canonical, at the time we speak.

    We encourage you to test with the latest versions of the plugins, and if you still have issues let us know what SEO plugin you use in order to test with it too.

    @kozmonauta You received the answer to the topic you have opened, also.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Bad for SEO + no support = don’t buy this plugin’ is closed to new replies.