Time to remove Yoast

Hi @leslierad,

Almost a year has passed since your review. We’ve made a ton of changes to Yoast SEO and would like to invite you to give the plugin a new try.

If you want to learn more about the plugin before installing it, we feel our knowledge base is the best place to start.

Thanks!

Sorry my rating remains the same, as I am still using sub 3 version, due to qtranslate-x incompatibilities with yoast and the refusal of co-operation so far.

Hi @leslierad,

Thanks for your reply! We actually have a knowledge base article about qTranslate X. You can find it here: https://kb.yoast.com/kb/wordpress-seo-qtranslate/

Do you have the integration plugin downloaded and activated?

Thanks for your reply! Just an FYI your knowledge base article about qTranslate X is actually about qtranslate, many things changed with qtranslate x making that knowledge base close to being irrelevant.

Of course I have the integration plugin active, I helped the author test several features of the plugin but it currently only supports up to wpseo ver 2.3.5 https://www.ads-software.com/support/topic/help-wanted-3/

Yoast may want to have a look at the changes and/or create a similar plugin or at the very least support it, it also seems that the plugin author has stalled development hence providing opportunity.

Why Yoast should support qtranslate-x

• – has 100,000 + active installs itself excluding other flavors
• – has 20,000 + active installs of the wp-seo addon, imagine if it actually worked with wpseo latest versions
• – AIO SEO addon only has 10,000 + active installs
• – Language translation is vital to many online businesses
• Qtranslate-x is a whole lot more refined than the original qtranslate
• – People are stuck with qtranslate variants forever, there is no alternative other than removing content entirely.
• – How hard could it really be?

More
Here is the support and issues list if you really want to dig a bit deeper https://www.ads-software.com/support/plugin/wp-seo-qtranslate-x

• This reply was modified 8 years ago by leslierad. Reason: fixed
• This reply was modified 8 years ago by leslierad.
• This reply was modified 8 years ago by Samuel Wood (Otto). Reason: Really fixed. Put UL's around LI's

Some more reasons:

All 20,000 active installs use ver 2.3.5 I see your stats are about 37% other versions, so if WPSEO worked with qtranslate-x the number would decrease.

You would get more new installations over time

Your rating rankings would improve as many qtranslate-x users were peeved and would be delighted if it was supported.

The list goes on and on, but anyway….. No hope of that !!

We have several issues with qTranslate-X that, unfortunately, are very, very deep into the basics of Yoast SEO and qTranslate. All languages are in the same fields with qTranslate. We can’t do the separation, that has to happen server side. We’d have to do server back-and-forths all the time to do our SEO and readability analysis, which is something we don’t want to do.

I also have a deeper, underlying issue with qTranslate: if it’s disabled, the site is left with very broken content in the database.

So, if you insist on using qTranslate, please use another SEO plugin. As we are very open about that, you can probably also agree with me that that’s not a “fault”, or worth a 1* review, it’s just our choice. You also wouldn’t give us a 1* rating on www.ads-software.com because we’re not compatible with Microsoft frontpage ??

@joostdevalk, Thanks for taking the time to reply,

While you do have several valid points, the main one being don’t use my plugin, that view point while you are entitled to it, will not help your ratings in the long term, unfortunately.

Playing nicely with other plugins (or at least pretending to) is surely a rating factor when one assesses a plugin for a review. (header and footer plugin – also springs to mind)

The extent of the “damage” done, in this instance is reflected in my review rating stars, along with the fact that I tried ver.3 WPSEO on launch with several non-qtranslate websites and it was full of ads and extra unwanted services, on top of that, it didn’t work and was a disaster, it seemed that it was released in alpha version that hadn’t been tested adequately.

Surely a plugin author would want their plugin to be as compatible as possible with as many other plugins as possible, trying to find solutions when they appear unattainable, working together with other developers to ensure cross compatibility, listening to user reports of issues, putting functionality before profit, after all that is what the wordpress community is meant to be about – I guess

I know there is no point going on about this, but just a real quick response to some points.

From Qtranslate-x version 3.5 onward the plugin offers a choice to “Split database file by languages” for option “Convert Database”, which allows to split .sql database file of multilingual site into separate single-language database files.

Support of one language per install would more than suffice for most users, or sell a pro plugin to enable more languages to compensate for the additional query’s.

The server back-and-forths, would probably be non-existent with your assistance as that can all be done pre-fetch on the host website.

I for one would buy several licenses for pro even for 1 language support as I’m sure many others would.

There is also a plugin to remove qtranslate, I have never tested it so can’t say if it works or not but it was recently updated https://www.ads-software.com/plugins/qtranslate-to-wpml-export/

Your version 3.0 remarks: you know that was a year ago right? Have you tested the recent version?

If qTranslate adopts a model that would be workable with our plugin, we would most definitely be willing to work with them on integration.

“Surely a plugin author would want their plugin to be as compatible as possible with as many other plugins as possible”

I’m sorry, but no. I want to be compatible with plugins that I think are good. When a plugin works against what we’d consider proper use of WordPress API’s etc, we will not integrate with them. The qTranslate developers have never reached out to <i>me</i> either yet. And surely, if you follow that earlier feeling, they should want to integrate with the biggest plugin of them all? We work with everyone who wants to integrate, but I don’t think it’s necessarily our responsibility. Just like it’s not WordPress core’s responsibility that when a plugin uses an API badly, a change in that API might break that plugin.