If you want to have a chance to achieve the best possible scores associated with on page SEO via Google Page Insights, you will not want to take the approach of the HTML editor, unless it is capable of saving and exposing the H1 tags of text. You want to ensure that the H tags are exposed. You also want to make sure the images have alt text, so unless the HTML editor can do that, you do not want to use the HTML editor approach.
The approach that I take, which has resulted in 100% on SEO as well as Best Practices and Accessibility on Google Page Insights is to have two data types, one is blog post and the other is blog post section. I also have an option set of section type.
My blog data type has fields like title, page title, Meta Title, Description, word count, category, keywords and other data points that would naturally belong to the blog post itself, especially the necessary components of Structured Data like the author, publish date (not using the built in created date so I can schedule a post without needing to schedule a backend workflow), modified date (not using modified date built in).
My blog post section data type has fields like blog post (related data type), section order number, section type option, as well as fields that may or may not be filled in based on the section type, like paragraph (text), image (img), image alt text (text), image caption (text), header (text).
In my apps I have a complete Content Management System, and I released my Blog Builder - SEO Juice Boost Template a while ago that is what I use in my own apps.
@salemmo409 Trust me when i say this; Take @boston85719 advice, and make sure you set up this properly so it’s scalable (i did not do this and had to redo everything a few weeks later)
. Thanks all.