Great SEO Builds Community, and Great Community Improves SEO

tyw  We haven't permanently fixed it yet. We maintain 2 brands (Ziggo and Vodafone in NL) with 2 seperate communities. We made a rough fix for 1 and we didn't see any significant gain in click throughs from Google. So to permanently fix it, is now lower on the backlog. We still want to do it, for future proofing purposes.

Maybe I can say something about the cause: Below we are looking at the Forum Topic Page quilt in Studio (we don't have or need Aurora yet). The OOTB topic-message component must be in a section called 'main-content', otherwise the Structured Data is broken. This took a long time to find and is not documented. So creating your own layouts in Khoros is not as flexible as promised. 

Broken Google Structured Data:

<quilt layout="name" nestable="false" disableTopCssClass="false">
  <add to="common-header">
    <component id="quilt:Header"/>
  </add>
  <add to="main-top-content">
    <component id="topic-message"/>
  </add>
  <add to="main-content">
    <component id="thread-pager"/>
    <component id="solution-count-conditional"/>
    <component id="solution-list"/>
    <component id="reply-count-conditional"/>
    <component id="message-list-detail-with-inline-editors"/>
  </add>
  <add to="common-footer">
    <component id="quilt:Footer"/>
  </add>
</quilt>

Working Google Structured Data:

<quilt layout="name" nestable="false" disableTopCssClass="false">
  <add to="common-header">
    <component id="quilt:Header"/>
  </add>
  <add to="main-content">
    <component id="topic-message"/>
    <component id="thread-pager"/>
    <component id="solution-count-conditional"/>
    <component id="solution-list"/>
    <component id="reply-count-conditional"/>
    <component id="message-list-detail-with-inline-editors"/>
  </add>
  <add to="common-footer">
    <component id="quilt:Footer"/>
  </add>
</quilt>

So Structured Data only works when using conventional naming in quilts and layouts, and when you use OOTB components. This is 100% a coding thing @ Khoros - via a Khoros Support Ticket we never got this message across. We gave up on this route. Later we found above issues ourselves.

Probably the Khoros code that adds Structured Data to the pages has 'main-content' hardcoded in it and it doesn't look dynamically where the components are in the quilt.