Paste this inside a script tag with type application/ld+json in your page head. Only use QAPage on a real question and answer page, not a curated FAQ list, which should use FAQPage instead.
Built by Rankite, the SEO team behind Swordfish AI's +400% revenue and Zluri's +45% organic growth. See the case studies
These two schema.org types look similar but describe different content. FAQPage is for a curated list of questions and answers that you, the site owner, wrote, like a support or pricing FAQ. QAPage is for a single question with one or more answers submitted by different people, the structure of a forum thread or a community Q&A page, where an accepted answer is chosen from possibly several suggested ones. Using QAPage on a page that is really just your own FAQ list misrepresents the content.
The output nests a Question inside mainEntity, with an acceptedAnswer and, if you filled them in, one or more entries in suggestedAnswer, matching the structure Google's documentation describes for QAPage. Optional fields, like the question's author, an answer's author, and upvote counts, are only included when you provide them, keeping the output free of empty or placeholder values.
Structured data should describe content that actually exists and is visible on the page, in the same form. Only mark up a real question with real answers from real users, since search engines can take action against structured data that misrepresents a page's content, and rich result eligibility for QAPage can also depend on factors beyond valid markup, like the page's overall quality and how the question and answers are presented visually.
Get a free, no-obligation SEO audit and a 30-minute strategy session. We'll show you exactly where the growth is hiding.
Fill out the form and we'll get back to you within one business day. Prefer email? Write to us directly at contact@rankite.com.