FAQPage is an archive page, so make sure the page you created has children for the questions and answers. See this FAQ for more info: https://wpsso.com/docs/plugins/wpsso/faqs/how-do-i-create-a-schema-faqpage/
j.s
While I imagine that a parent/child FAQ is good for SEO, it seems counterintuitive for the FAQ Page Schema Type to not work for… a page.
At any rate, thank you for your response. I will change this to article, and mark it resolved.
The Schema FAQPage type is a collection of Questions and Answers (see https://schema.org/FAQPage and https://developers.google.com/search/docs/appearance/structured-data/faqpage). WordPress manages collections as either a parent page with child pages, or a taxonomy archive page, like categories, etc.
js.
Google defines a FAQ page as:
A Frequently Asked Question (FAQ) page contains a list of questions and answers pertaining to a particular topic.
https://developers.google.com/search/docs/appearance/structured-data/faqpage
Google defines a FAQ Page as exactly that: a page. Not pages, and not a parent with child pages. If WordPress is forcing this by referring to a FAQ Page as a collection, then it seems wrongly applied based on Google’s definition.
Yes, a FAQPage is a page, and the markup contains a list of Questions and their Answers, in the same way that a WordPress archive page is a list of posts/pages. The mainEntity that Google warned you about is that missing list of Questions and Answers. You can choose to create Questions and Answers for the FAQPage markup, or not. The FAQ I mentioned previously suggests a few different ways to manage your Questions and Answers.
js.
