Think of answers on a question/answer web page like Yahoo Answers. The documentation indicates they don’t have to be relevant or accurate answers. Best to use suggestedAnswer when there are many possible answers. suggestedAnswer – This property is expecting you to create an Answer data item. Url – The URL for where the question lives on the page.Using the actual question is a good idea, just to keep things simple. name – Choose an identifier to name the data item.text – The actual text of the question itself.Question Schema Markup Properties Explained If there are 5 upvotes and downvotes are not supported, then the value for upvoteCount is 5. For example, if there are 5 upvotes and 2 downvotes, the aggregate value used for upvoteCount is 3. If the page supports upvotes and downvotes, then set the upvoteCount value to a single aggregate value that represents both upvotes and downvotes. The total number of votes that this question has received. For example, “I’m cooking, and I need to know how many teaspoons are in a cup. The intended content is the long form of the question. This should be defined by either a Person or Organization schema class, with the name property filled in by text. The intended content for this property is the short form of the question. There should only ever be 1 acceptedAnswer, however than can be any number of suggestedAnswer. We must use the class Question to define the mainEntity property.Īt least one of either acceptedAnswer or suggestedAnswer must be nested underneath the Question. Let’s have a look at each class, they’re required properties as called out in the Documentation, and what values these properties should be defined by: QAPage Schema Class for Q&A Markup An example looks like this: How many ounces are there in a pound? They are:Įach of these will be connected and nested underneath one another. There are 3 schema classes that we will need to use to complete our Q&A Page markup. With that out of the way let’s get into how to achieve this stand out rich result! Q&A Page Schema Markup Requirements This is not intended for a single page with a long list of FAQs. Therefore this is excellent for support pages and forum posts, or any page with a single question and multiple answers. The documentation for Q&A Page is very clear that this is meant for pages that answer and discuss a single question. Let’s take a second and discuss the type of content this rich result is built for. But first, what does it look like? How will your snippets change by implementing this QAPage schema markup? Here is the example provided by Google: Right away people started asking us how to achieve this new iteration of the question & answer rich result. “There’s a new Google Rich result in town, “Q&A Page”, powered by #/QAPage, Question and Answer…” On December 3rd, 2018, Aaron Bradley pointed out that he saw the new Q&A Page rich result. Q&A Schema Markup: A Timelineĭecember 2017 – Google released a question and answer rich result cardĭecember 2018 – Google search results now include a “Top Answer” rich result Learn more about Q&A page structured data in Google’s documentation here. Google recommends that your QAPage schema includes a URL for each individual answer to improve user experience. You can mark up these questions and answers with QAPage schema to have this content eligible for enhanced Google features in search results. Question and answer page (Q&A Page) schema markup is a relatively new type that is used for pages that contain a question and a way for users to submit answers to that question.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |