No matter how much I’d like to find a solution for this issue, it cannot be fixed by making any modifications to the HTML code the plugin generates, because there is no other way to automatically embed the schema.org microdata around the content than the one that is currently used.
If your CSS tries to match the content’s div element using the element hierarchy instead of using the content’s div ID or class, then matching it would be impossible and thus no style could be applied, which would make the theme break.
If the schema.org microdata generator is enabled and the layout is affected, it can only be fixed in the stylesheet by trying to match the content’s div element in a different way. For example, if the content is matched with something like this:
.post .entry-content > p
You should use the following instead:
.post .entry-content p
Matching the element path with syntax like body>...>div>div>p
is not recommended.
Alternatively, you could try to use the JSON+LD schema.org generator. The only known bugs so far are with WooCommerce products. If you use it, since the code is not mature enough, please feel free to report any issues you encounter.
Kind Regards,
George