Compatibility with qTranslate X

Hi baga!

Thank you very much for considering The SEO Framework.

I’ve never heard of qTranslate X, so I’ve just tested qTranslate X with The SEO Framework.

Here’s what I found:
All automated descriptions, titles, canonical URL’s, shortlinks and other meta is working perfectly with The SEO Framework and qTranslate X!
That’s great ??

Even more so, the shortcodes which define the language also work in the manual description and title. As per example below:

Example title:
[:en]English Page Title[:de]German Page Title[:] | [:en]My English Website[:de]My German Website[:]

The output:
English Page Title | My English Website
German Page Title | My German Website
respectively on English and German pages.

This works great!

One thing doesn’t work:
The sitemap is placing e.g. /de/ in front of everything for example if your base language is German. This makes the sitemap incompatible.

Luckily, as discussed with other users, a sitemap isn’t at all influential for SEO, especially within WordPress.
If you’re interested, you can read the discussion here: https://www.ads-software.com/support/topic/rebuild-sitemapxml?replies=12#post-7693912

This doesn’t mean I won’t make it compatible. I will absolutely take a look at the sitemap, an update is underway! ??
I can’t give an ETA yet.

If you have any more questions, feel free to ask!

Thanks and have a great day!

Edit: Fixed discussion link.

Hi Sybre and thanks for your quick reply!

I’m happy to hear that it works with qTranslate X and no problem about the sitemap. By the way even better if you’re looking for a fix.

One more question, are there any issues with Genesis framework?

Thanks a lot and have a nice day ??

Hi baga,

Oh dear, the issues with Genesis.. ??

Just kidding, The SEO Framework is built upon the Genesis Framework!

In fact, it uses the same options tables and even automatically copies Genesis SEO data from them.

I’m using the Genesis Framework on (almost) all my personal sites in perfect harmony :).
You’ll notice that the option pages and per-page settings look exactly like Genesis’.

I hope this helps, thanks and have a great day ??

BEAUTIFUL!
I’m gonna dowload and try your plugin right now ??
Thanks again

Anytime baga ??

Let me know if you need further assistance, I’m happy to help you out ??

I’m marking this topic as resolved, I’ll look for the sitemap compatibility in the near future. I’ll update on this post when the compatibility is present.

Fantastic, excellent support so far.

Hi baga!

Anytime ??

I wanted to inform you that The SEO Framework 2.4.2 will support the sitemap in conjunction with qTranslate X ??

The SEO Framework 2.4.2 will also fix various issues with Canonical URLs and qTranslate X.

Stay tuned, I expect this update to be released tomorrow if everything goes well ??

What a wonderful new!
Looking forward to the 2.4.2 release ??

Hi again.
I’ve finally started to use The SEO Framework and noticed issues with qTranslate X:

– the sitemap is generated only in one language;
– the SEO bar is red for all the pages, saying “Title: far too long”. Same issue on description.

How can I change <meta property="og:locale" content="en_US" /> to <meta property="og:locale" content="en_GB" />?

I have a few more questions that are not language related, can I post’em here or should I open a new topic?

Hi baga,

Feel free to post them here ??

The og:locale listens to the current WordPress language settings, I’ve seen it working great with WPML and qTranslate alike as they automatically change the whole interface.

You can change the default settings in General Settings of WordPress, and set the “Site Language” option all the way below.

Regarding the SEO Bar being red, that should definitely be checked out. It’s worth noting that the bar changes color at the following character count thresholds:

Description:
0~99: Red
100~144: Yellow
145~155: Green
156~174: Yellow
175+: Red

Title (including the separator and main blog Title):
0~24: Red
25~41: Yellow
42~55: Green
56~72: Yellow
75+: Red

I’m unable to replicate your issue with qTranslate, please take a look at the numbers and see if you find an issue there.

The sitemap is split into different languages because qTranslate lets WordPress know that it’s another website of some sort, therefore The SEO Framework can’t access them directly. As stated in my first comment: “The sitemap is placing e.g. /de/ in front of everything for example if your base language is German. This makes the sitemap incompatible.”

Please keep in mind that the sitemap is currently cached for only one language. I’ll take a look at how I can split the cache into multiple ones (one for each language) when qTranslate is used!

I hope this helps ??

Happy Holidays!

Sybre thanks for getting back.

About og:locale I was able to change it from WordPress language settings.

SEO Bar: for sure there’s something weird going on.

I realized that the automated description are generated only for the main language, is there a way to disable them completely?

og:image value is empty on most pages because I don’t have a featured image, can I disable it?

What about the <link rel="alternate" type="application/json+oembed"? If I click on it, the following error appears

{“code”:”oembed_invalid_url”,”message”:”Not Found”,”data”:{“status”:404}}

, is it normal or should I worry about it?

Thank you very much and happy holidays to you too!!!

Hi @baga,

‘Random’ Json script
The json+oembed code is something added through WordPress 4.4, I think it’s used for the new REST API, which I still need to dive in as it contains powerful stuff :). It’s quite new so it might contain some bugs. On my test sites the output is the same, but I’m certain that The SEO Framework doesn’t interact with it. It’s also invalid HTML but I’m sure I’m not the only one who has caught up on that, so a fix is imminent.

Only the <title> tag and everything between the HTML indicators is output by The SEO Framework on the front-end. In special cases this can differ but requires developer input.

Automated Description
Currently, there’s no way to disable the automated description consistently.
I might make it filterable but I must check for possible redundancy and errors that might come with it, as the plugin currently always expects an output on several occasions (placeholders, cache, etc.).

Depending on your qTranslate settings, where subdirectory or sub-domain is recommended, the cache might conflict.

The automated description is only made once in the admin dashboard for the current admin language. On the front end it may differ but I have yet to test this (I find qTranslate very time consuming to do test cases with).

Manual Description
To make sure the description is consistent and different for multiple languages, you can use the following syntax to output different descriptions by manually filling in the description. It will however notify you of “Too long” descriptions, so you can ignore that.
[:en]My English Description[:de]My German Description[:]

OG:image
Disabling OG image will result in an invalid OG structure (as fetched by Facebook) and it’s therefore recommended to leave on, even if empty :). So there’s to worry about.

About the SEO Bar
It will only calculate output from either manual input or from the current admin area language. You can see all output values by defining the debug constants (as found in the API docs), and without a closer inspection on your site I can’t say for sure what’s causing the current output. You could of course debug the values yourself but it will require some PHP knowledge. If you wish to proceed with manual debugging, please tell me and I’ll inform you where to look and what to use :).

I hope this helps! ??

Thanks again Sybre!

I made some confusion with the json+oembed code, I didn’t realize it was added by WordPress itself.

Tha automated description issue will take a lot of my time, since I will have to manually rewrite 200+ pages x 10 languages.

I think I’ll go back to Yoast 2.3.5 temporarily.

Hi @baga,

Thanks for getting back ??

Have you already manually filled in those descriptions in the past with Yoast SEO? With the SEO Data Transporter you can easily transfer them ??
Read how to here: https://theseoframework.com/docs/seo-data-migration/

The next update of The SEO Framework will overhaul the way automated description are processed, I’ll be sure to add a filter for your needs in there ??

The filter will work exactly like this:
add_filter( 'the_seo_framework_enable_auto_description', '__return_false' );
This will effectively remove the description when none is provided manually ??
It will also automatically clean up your database over time as the transients are not used anymore.

I hope this helps! A beta version is almost ready!

Thanks and have a great day ??

Excellent that sounds great, I will give it a try for sure.
Thank you!