Wordpress-seo: FAQ block structural changes

[moorscode]

The current FAQ block outputs headings as strong tags, this is not SEO or semantically a good solution.

What the output should be has been discussed and these are the conclusions:

• FAQ block should be repeatable, this will allow for headings to be placed between questions, to better manage context and structure
• Question-titles need to be headings, depending on the header they are placed under (after an H1 should come an H2)
• Answers (content) needs to be able to contain multiple blocks (paragraphs, images, videos, lists, etc)
• Need to be able to mark in the content

Because FAQ blocks should be repeatable, the JSON+LD needs to be consolidated from all FAQ blocks that have been entered on a page.

[mariusghitulescu]

Please inform the customer of conversation # 453968 when this conversation has been closed.

[atimmer]

Technical details for annotating inside the blocks

For this to work our blocks will need an identifier prop for every RichText instance inside the blocks. Our annotation code then needs to know which richTextIdentifier to put on an annotation to be make sure the annotation is applied to the correct block.

[amboutwe]

Please inform the customer of conversation # 475223 when this conversation has been closed.

[suascat]

Please inform the customer of conversation # 525947 when this conversation has been closed.

[ben72]

Any progress on repeatable FAQ blocks?

[Dargno]

Adding headers between questions would be an amazing feature, as well as setting the block template in the theme or some options field (choosing which tag the questions get). Amazing plugin so far, but hard to implement for dedicated FAQ pages because the list will get too long / not structured enough...

I think this would reduce the need to add multiple FAQ blocks to a page.

Or maybe allow multiple but only do the JSON-D part for the first block on the page (for SEO) while the rest can be built with the same interface for the page itself....

[rumejan]

Please inform the customer of conversation # 642276 when this conversation has been closed.

[michaelbriantina]

Please inform the customer of conversation # 674678 when this conversation has been closed.