Skip to main content
bjoern_schulze
Helper ⭐️⭐️⭐️
October 27, 2022
Open

Own content types for Tutorials and FAQs

  • October 27, 2022
  • 5 replies
  • 102 views

I want to follow up on this idea regarding Google Rich Results for FAQs and How-Tos from a few years back and add new feature ideas because:

  • I believe it is still relevant → and even moreso based on the direction Google is taking its search results page
  • inSided / Gainsight are focussing their product vision to position the platform as a 360 degree customer hub with more and more content types

Customer education content (i.e. self-service content) typically comes in the type of a tutorial (how-to) or an FAQ. Both of these types differ from a classic article, both in structure and in content.

An article usually is a continuous text separated by paragraphs and sub-headlines.

A tutorial / How-To usually is a step-by-step instruction about how to use a product or a function.

An FAQ usually consists of several questions and their answers regarding a product or a function.

I therefore propose to create separate content types for:

  • Tutorials / How-Tos → Add steps (title, body, image) within one piece of content to complete an instruction
  • FAQs → add questions and answers within one piece of content

I furthermore propose to enrich both of these new content types with the Google Rich Results enhancements:

Having these new content types and enhancements will give inSided customers the opportunity to:

  • create well-structured customer education content → for better self-service
  • be highly visible on Google → because Google is pushing very hard towards moving away from the classic search results page towards integrated rich results (content widgets)

5 replies

Cristina
Helper ⭐️⭐️⭐️
November 18, 2022
The following idea has been merged into this idea:

All the votes have been transferred into this idea.
Cristina
Helper ⭐️⭐️⭐️
November 18, 2022
New→Open
Cristina
Helper ⭐️⭐️⭐️
November 18, 2022

Hi @bjoern_schulze, thank you for bringing this up! You’re raising very good points and it makes me think that we should create a more flexible topic form that could be customised and meet multiple needs and, at the same time, have a high performance on Google search. Really curious to hear more thoughts on this! 🙏🏻 

Suvi Lehtovaara
Helper ⭐️⭐️
January 25, 2023

We strongly agree with this idea 👍🏻

InSided already supports structured data in the form of QA Pages. We’d like to expand this to FAQ’s.

The main difference between QA Pages and FAQ pages is what they represent, and how they are represented on the SERP (Search Engine Results Page)

 oUyyB8B5Yq_ogEmO_FLOSdB6fIKy2_E1ah-RiJzrDN3m5hNo0YnG3soVel9YM-l5P7IP_8VTiOS7PQgYxMUTdYS5r3pUUDJ515alAq76NC6P14Ob14tPo8PqQlYNfz5lmeUqJ9G-MnU2fG_lYvkfC6zWNsjFg2L6MIDr-FaWDwCYBjhstVuBqBv7XK6ZFw

 

QA Pages are presented as a singular question with multiple answers, usually elevated to a position 0 spot. This makes them very desirable, but also difficult to achieve. 

FAQ Pages are broader, and rather than seeking to answer a singular question, seek to also answer adjacent ones. FAQ Pages have multiple questions with singular answers. 

They're tracked different in Google Search Console, and users engage with them differently. In addition to a general boost in SEO, it also helps target newer segments - as both the data for QA pages and FAQ pages is used for voice search. 

Use Case 

We often have situations where we want to preemptively answer the questions users might have, and keep them to a singular page in order not to confuse visitors. The FAQ page structure is ideal for this. It improves general SEO, enhances our present in the SERP presence and ensures our content is compatible with voice activated search assistants (such as Google Assistant, Siri, Alexa etc.) 

(Potential) Solution

Allow for a "FAQ block" segment in the content editor that automatically structures the content within it as structured data, and subsequently overrides the page type to that of a FAQ Page.

https://yhteiso.elisa.fi/
Cristina
Helper ⭐️⭐️⭐️
February 9, 2023
The following idea has been merged into this idea:

All the votes have been transferred into this idea.