> Custom elements aren’t “semantic” because search engines don’t know what they mean. Lots of good points in this article but I don't think this is an issue. I

> Custom elements aren’t “semantic” because search engines don’t know what they mean. Lots of good points in this article but I don't think this is an issue. IMHO custom elements shouldn't be used to define content, we have standard elements for that, it should be used for rich interactive components. For example a datepicker. If there is content in the element then I do not see how search engines would interpret it any different than a normal div, or even better the custom elements should define content appropriately such as <my-component><article>text</>