Hi there, I needed a light translation plugin, polylang & co are to bloated and old and never actually liked those. So I found BOGO translate (https://wordpress.org/plugins/bogo/), which looks just right, but your plugin does not recognize it and I don’t know what to change and where to make them work together 🙂 THX
You’re right, SEO Engine doesn’t know about Bogo yet. It currently only detects Polylang and WPML specifically. It needs a bit of code on my end. Good news is that Bogo is a clean one to support. It stores the post language in a simple _locale meta which is exactly what SEO Engine needs, so I’m adding it! 😊
In the meantime, here’s what’s actually affected. The only thing SEO Engine uses the multilingual plugin for is knowing which language a post is in, and that’s used for the AI features. Without Bogo support it falls back to the single language set in SEO Engine → Settings → Others → Language, so AI suggestions (Magic Fix, Magic Wand) get written in that one language instead of per post. Everything else works normally: scores, titles and meta descriptions, sitemap, schema, redirects, the analysis itself. Nothing is broken, just not language-aware yet.
So if most of your content is in one language, set that there and you’re fine. The next release will make it even better 😊
Yep, it’s a newer plugin, but lightweight and does the job without cluttering the database. I think that newer plugins developed recently, are much better and more “in tune” to today’s world (valid for SEO Engine as well :), there is no way in the world I would pick Yoast & Co these days)
Problem with translations is, I already started to translate pages, and there is a real problem that the SEO titel and description for the English page for example, are in German, which kills the whole SEO effort for that page. Moreover, the titel will now be also identified as “same Titel” / double titel which again is not good :((
I picked “auto” for language now, but there is no change. Is there any code snipped I could add somewhere (functions.php etc?) to bridge the time till SEO Engine will become compatible?
Bogo support is in 0.8.5, just released! 🎉 SEO Engine now reads each page’s language from Bogo, so English pages get English suggestions and German pages get German ones. Duplicate title detection is per-language now too, which should clear those warnings.
That said, the German titles and descriptions already saved on your English pages won’t be rewritten automatically. Fixing each one is a single click though, no code needed. Open an English page, find the SEO Engine panel, and click the magic wand next to the SEO Title, then next to the Description. It regenerates in that page’s language. Review, save, done!
That’s also why “auto” didn’t help. Auto means “use the site’s language,” so it still gives one language for the whole site rather than one per page.
That sounds wonderful! But I must be doing something wrong as I still cannot see the English version of the post/page/etc. … only the drop-down menu for language selection. BUt when I select Englosh, nothing happens :(… Do I have to set something somewhere?
You’re not doing anything wrong, this is my mistake! 🥲 Bogo automatically narrows down every post query to the current site language unless a plugin explicitly asks it not to, and SEO Engine’s post list was getting caught by that. The English posts were filtered out before SEO Engine ever saw them, so picking English in the dropdown just gave an empty list…
I reproduced it on a test site and fixed it. While I was there I also found two more spots with the same cause: the sitemap could drop URLs in the secondary language, and the internal link suggestions could propose links across languages. Both are fixed too! 🎉
It’ll all be in the next update (0.8.7, it’s being released right now). Once you have it, the language dropdown in Content SEO will properly switch between your German and English posts, and you can use the magic wand on the English ones to regenerate their titles and descriptions in English.
Thanks for pushing on this, it was a real bug and I wouldn’t have caught it without your reports! 🙂
