How to add FAQ schema to a WordPress page

Step by step

1. Decide whether the page should have it

FAQPage is for a page where you, the site owner, wrote both the questions and the answers: a support page, a product FAQ, a section at the end of a guide. It is not for forums or pages where users submit answers. Those are QAPage. And it only applies to questions that are visible on the page. Marking up questions the visitor cannot see breaks Google's structured data guidelines.

2. Write the questions on the page first

Add the questions and answers to the page content as normal text, each question as a heading or bold line with its answer below. Phrase questions the way people ask them, and answer in the first sentence before adding detail. The schema will mirror this text, so get the visible version right before touching the markup.

3. Add the schema in the editor

1. Open the page and open the SEO Settings sheet (⌘E or Ctrl+E).
2. Go to the schema section and choose FAQ as the schema type.
3. Add each question and its answer as a pair, matching the visible text.
4. Save the page.

Each pair is printed as a Question with an acceptedAnswer of type Answer, inside one FAQPage object. If a whole post type is made of FAQ-style pages, the same type can be set once for that post type on the Schema screen instead.

4. Or add JSON-LD by hand

Without a plugin, build the markup with the FAQ schema generator and paste it into a Custom HTML block on the page:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "How long does shipping take?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "Orders ship within two working days and arrive in three to five."
    }
  }]
}
</script>

Users without the unfiltered HTML capability have script tags stripped on save. That means Authors and Contributors on a normal site, and everyone except super admins on multisite. In that case an administrator needs to add the block.

5. Validate the markup

View the page source and confirm one FAQPage block is present. Then paste the page's JSON-LD into the JSON-LD validator, or test the URL in the Schema Markup Validator at validator.schema.org. Google's Rich Results Test is built around the features Google still shows, and FAQ is no longer one of them, so a general schema validator is the useful check.

6. Keep page and schema in step

When you edit an answer on the page, edit it in the schema too. Drift between the two is the most common fault: the page says three to five days, the markup still says seven. Review FAQ pairs whenever you update the page.

7. Avoid duplicates

A page should carry one FAQPage object. If a page builder's FAQ or accordion widget also outputs schema, switch that option off or remove the pairs from the sheet. Two blocks listing overlapping questions is confusing for any parser.

What FAQ schema does and does not do now

Google limited FAQ rich results to well-known government and health sites in 2023 and retired them for everyone on 7 May 2026. HowTo rich results were removed in 2023 as well. So adding FAQPage markup will not change how your result looks in Google.

The case for it is narrower and honest: structured question-and-answer data is easy for any crawler or answer engine to parse and attribute. Nobody publishes a guarantee that marked-up answers are quoted more often. If the questions are real and already on the page, the markup costs a few minutes. If you would be inventing questions to have something to mark up, skip it.

Write answers that stand alone

The parts that carry value are the answers themselves, with or without markup. Keep each answer complete without the surrounding page, lead with the direct answer, and keep promotional lines out. "Contact us to find out" is not an answer. Short, specific answers are also what search engines lift into featured snippets and "People also ask" boxes, which never depended on FAQ schema.