How to Add FAQ Schema to Your Pages Step by Step

Updated on January 13, 2026

If you've ever noticed those expandable question-and-answer blocks appearing directly in Google search results — the ones that sit right below a page title without you even clicking through — that's FAQPage schema doing its job. It's one of the most practical structured data types you can add, and unlike some other schema types, you don't need a developer on call to implement it. This walkthrough takes you from raw Q&A content all the way to a validated, live implementation.

Step 1: Decide Which Pages Actually Deserve FAQ Schema

Before you write a single line of JSON-LD, take a breath and think about whether the page genuinely has a FAQ section. Google's guidelines are clear on this: the FAQ markup should reflect content that's actually visible to users on the page. Don't mark up questions that exist only in the code.

Good candidates include:

  • Service pages where customers repeatedly ask the same things ("Do you offer refunds?" "How long does shipping take?")
  • Long-form blog posts that dedicate a section to answering reader questions
  • Product pages with a formal Q&A section
  • Support or help articles that are structured around questions

Landing pages stuffed with fake FAQs purely to grab rich results tend to get ignored or demoted over time. Real questions — the kind your support inbox is full of — work far better.

Step 2: Write Your Q&A Pairs with Purpose

This step matters more than most tutorials acknowledge. The quality of your questions and answers directly affects whether Google chooses to display the rich result at all.

A few principles worth following:

Write questions the way real people ask them. "What is the return policy?" works. "Return policy information details" does not — that's a heading, not a question.

Keep answers complete but scannable. Google typically shows around 320 characters in the rich result preview, but the full answer is what matters for searchers who expand it. Aim for answers that are genuinely helpful in 2–4 sentences.

Avoid promotional language in answers. "Our amazing product does X better than anyone else!" is the kind of answer that won't perform well. Informative, neutral tone wins.

Here's an example of a well-written pair for a shipping FAQ:

Q: How long does standard shipping take?

A: Standard shipping typically takes 5–7 business days within the continental US. Orders placed before 2 PM ET on weekdays are usually shipped the same day. You'll receive a tracking number by email once your order leaves our warehouse.

Notice it's specific, actionable, and doesn't need any hype to be useful.

Step 3: Generate the FAQPage JSON-LD

JSON-LD (JavaScript Object Notation for Linked Data) is the format Google recommends for structured data. You don't need to memorize the syntax — there are good tools that handle the boilerplate.

Option A: Write it manually — which is faster once you've done it twice. The structure looks like this:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "How long does standard shipping take?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Standard shipping typically takes 5–7 business days within the continental US. Orders placed before 2 PM ET on weekdays are usually shipped the same day. You'll receive a tracking number by email once your order leaves our warehouse."
      }
    },
    {
      "@type": "Question",
      "name": "Can I change my order after placing it?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Orders can be modified within one hour of placement by contacting our support team. After that window, the order enters fulfillment and changes are no longer possible."
      }
    }
  ]
}
</script>

Each question goes inside the mainEntity array as a separate object. Add as many as you have — there's no hard limit, though Google typically only shows up to 3 in rich results.

Option B: Use a generator tool. Merkle's Schema Markup Generator (technicalseo.com/tools/schema-markup-generator/) has a dedicated FAQPage option. You type in your questions and answers through a UI and it spits out valid JSON-LD. Useful when you're getting started or if you're building FAQ markup for non-technical clients.

Either way, double-check that your name values exactly match the question text on the page, and that your text values inside acceptedAnswer match the answer text. Mismatches between the markup and visible content are a common reason rich results fail to appear.

Step 4: Insert the Schema into Your Page

Where you put the JSON-LD block matters less than people think — Google can read it from either the <head> or the <body>. That said, convention and tidiness both favor the <head>.

If you're using WordPress: The cleanest method is to use a plugin like Rank Math, Yoast SEO Premium, or Schema Pro. All three let you add FAQ schema through a visual interface tied to individual posts or pages, without touching code at all. Rank Math is probably the most flexible — it has a dedicated FAQ block in the Gutenberg editor that simultaneously adds the visible Q&A content and generates the markup.

If you're working on a custom or static site: Paste the <script type="application/ld+json"> block into the <head> section of the relevant page. If your site uses templates, put it in the template for pages that have FAQ sections, with a conditional check so it only renders when FAQ data exists.

If you're on Shopify, Webflow, or similar: These platforms typically let you inject custom code into page templates or through their "custom code" sections. Shopify's theme editor has a <head> section in theme.liquid — that's the right place.

One thing to avoid: don't add the schema twice. If you're using a plugin that auto-generates FAQ schema, don't also paste it manually — duplicate structured data can confuse crawlers.

Step 5: Validate Before You Push Live

This step gets skipped constantly and it's the one that catches the most errors. Google's Rich Results Test (search.google.com/test/rich-results) is the tool you want.

You have two options:

  • Test by URL — paste your live page URL and it fetches the page as Googlebot sees it
  • Test by code — paste your raw HTML or just the JSON-LD snippet for a quick syntax check before deploying

The tool will show you detected items, any warnings, and any errors. Common errors to watch for:

"Missing field 'name'" — means a Question object is missing its question text. Usually a copy-paste issue where the field name got garbled.

"The value of 'text' must be a string" — happens when an answer accidentally contains HTML tags inside the JSON. Strip the HTML from your text values (plain text only inside JSON-LD).

"FAQPage must have at least one mainEntity" — your mainEntity array is empty or the property name is misspelled.

Schema.org's own validator (validator.schema.org) is also useful for a more technical pass — it checks conformance to the schema specification rather than just Google's implementation of it.

Step 6: Monitor Performance in Search Console

Once the page is live and validated, rich results don't appear instantly. Googlebot needs to recrawl and process the page, which can take anywhere from a few days to a couple of weeks depending on your site's crawl frequency.

In Google Search Console, navigate to Search Results and filter by search appearance. Once your FAQ schema starts generating impressions, you'll see a "FAQ rich result" option appear in the filter. This lets you track click-through rate and impressions specifically for those rich results — useful for gauging whether your questions align with what people are actually searching.

If impressions never show up after a few weeks, re-run the Rich Results Test on the live URL to confirm the markup is still being detected. Sometimes a plugin update or template change quietly removes the structured data without anyone noticing.

A Few Things That Will Get Your Rich Results Pulled

Google has explicitly said it will disable rich results for pages that misuse FAQ schema. The situations that trigger this:

  • Using FAQ markup for advertising or promotional content disguised as Q&A
  • Marking up questions that aren't visible on the page
  • Putting FAQ schema on every page of a site regardless of whether the content actually contains questions
  • Duplicating the same Q&A content across many pages (identical markup on 50 product pages signals manipulation)

The threshold here isn't that strict — Google mostly wants you to use schema to describe what's actually on the page, not to game the results. If your FAQ content is real and your markup accurately reflects it, you'll be fine.

The Payoff

FAQPage schema is one of the few structured data types where the implementation effort is genuinely low and the potential payoff is visible. A rich result that shows two or three expandable answers in the SERP can significantly increase the real estate your listing takes up — which tends to push down competing results and improve click-through rates even when your ranking position stays the same.

The whole process described above — picking the right pages, writing good questions, generating clean JSON-LD, inserting it correctly, and validating it — takes maybe an hour for a single page once you've done it once. After that it's a repeatable pattern you can apply across your site systematically.