Issues with Builder >> SEO
Dear support team,
We have been using the BeTheme WP theme for some time now and we are pretty happy with what we have achieved with it. However, we are facing some issues now that we are trying to refine our SEO strategies.
We are aware that in order to be able to use the Yoast SEO built-in recommendations in the Page Editor we need to import the Muffin Builder elements with the Builder >> SEO option, since otherwise these elements would not be visible to the WP Editor and thus to Yoast (although they render just fine on the frontend). In order to avoid replicated content, Hide the content should be set to ON. We did so, but we noticed that some elements are missing their HTML surrounding code when imported with this feature.
For example, the 'Image' muffin builder element is rendering the image links as they are (see attached image), whereas the 'Photo Box' element does indeed output proper HTML with IMG tag, although it does not seem to recognise the alt element (we tried settings a title and that is also outputted as orphaned text in the editor).
Also, regular links do not output HTML either, but other muffin builder elements like the titles do indeed output the title tag just fine.
Finally, some styles get rendered as elements while ideally they should not appear as content in the editor.
We would like to know of these are known issues (we wonder if maybe some of those tags where added in subsequent theme release and they haven't been added into the parsing strategy needed to port them to the editor) or we might just be experiencing an issue with our setting. We tried both in live environment and in a VVV vagrant box with the same results, and we tried to disable our custom child theme and all active plugins, just in case, with no effect.
Any input would be really appreciated. We can provide backend access if needed.
Thank you very much in advance.
Comments
we know that this is not ideal, some style and tags may get messed up. You will have to go thru the code and check it again. We will work on it and try to make it better, for now we do not have any solution for this.
Thanks