Sybre Waaijer on "[Plugin: The SEO Framework] Compatibility with qTranslate X"

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! :)