Adding FAQ Schema to Shopify Blog Posts, the Easy Way

Adding FAQ schema to a Shopify blog post takes about ten minutes: write real questions and answers into the post, wrap them in a small block of JSON-LD, and paste that block into the post's HTML. The part worth settling first is why you would bother in 2026, because the reason most guides give you no longer exists.

Google retired FAQ rich results on May 7, 2026. The expandable answers that used to appear under a search result are gone for every site, including the government and health sites that kept them after the 2023 restriction. Google removed the supporting documentation the following month. If a guide promises you a dropdown in the search results, it was written before that change.

FAQ schema is still worth adding. The reason is different now, and smaller, and it is worth being precise about it.

What the markup still does

Structured data is a machine-readable label. FAQPage markup says: this block is a question, that block is its answer, and they belong together. Google no longer turns that into a search feature, but Google is not the only thing reading your pages. Bing parses structured data, and so do the retrieval crawlers behind AI assistants, which pull pages apart looking for passages that answer the question a person just typed.

Two honest caveats before you spend an afternoon on this.

First, Google's own documentation about AI features says there are no additional requirements to appear in AI Overviews or AI Mode, and that new machine readable files or special schema markup are not among the things that influence inclusion. So FAQ markup is not a Google AI play. Anyone selling it as one is guessing.

Second, the markup labels the answer. It does not make the answer good. An assistant that quotes your post is quoting the visible sentences, and it will do that whether or not there is JSON-LD underneath. The markup is cheap insurance for the machines that do use it, and the discipline of writing a real question-and-answer block is where most of the value actually sits.

Write the questions first

The mistake that makes FAQ blocks useless is inventing questions that sound searchable. Use the ones you already get asked. Your support inbox, your chat transcripts, and the query list in Search Console are all better sources than a keyword tool.

Three or four questions per post is the working range. Each answer should stand on its own in 40 to 60 words, because anything quoting it will lift it without the surrounding paragraph. Answer the question in the first sentence, then add the qualifier. And every question and answer in the markup has to appear in the visible post, word for word. Markup that says something the page does not is the one way this can actually hurt you.

The JSON-LD block

Here is the whole thing. Replace the two questions with yours and add a third and fourth in the same shape.

<script type="application/ld+json">
      {
      "@context": "https://schema.org",
      "@type": "FAQPage",
      "mainEntity": [
      {
      "@type": "Question",
      "name": "Do you ship to Canada?",
      "acceptedAnswer": {
      "@type": "Answer",
      "text": "Yes. Canadian orders ship from our Toronto warehouse in two to four business days, and duties are included at checkout."
      }
      },
      {
      "@type": "Question",
      "name": "Can I return a used board?",
      "acceptedAnswer": {
      "@type": "Answer",
      "text": "Yes, within 30 days, as long as the base has no core shots. Mounted bindings are fine and we pay return shipping."
      }
      }
      ]
      }
      </script>

Straight quotes only, no curly ones, and no line breaks inside a text value. Those two things cause most broken blocks.

Where it goes in Shopify

In your Shopify admin, open Content, then Blog posts, then the post. In the content editor, switch to the HTML view using the code button in the toolbar, scroll to the very bottom of the markup, paste the block after your last paragraph, and save.

Then check two things. Open the published post and view the page source to confirm the script tag survived, since a few themes and page builders strip script tags from post bodies. Then paste the URL into the Schema Markup Validator at validator.schema.org.

Use that validator, not Google's Rich Results Test. The Rich Results Test only reports features Google actually shows, so now that FAQ rich results are retired it will report nothing for a perfectly valid FAQPage block. A clean test there is not evidence your markup is broken.

What to do with FAQ markup you already have

Leave it. Google has said unused structured data does not cause problems in Search, so there is no cleanup project here and no reason to strip markup out of old posts. If anything, the posts worth revisiting are the ones where the FAQ block was written for a rich result rather than for a reader, with three thin questions padded to hit a format. Those are worth rewriting as answers.

How Riten handles it

Riten writes the FAQ block as part of the post, and when the post publishes to Shopify it attaches the FAQPage markup to the article automatically, built from that post's own questions. Nothing to paste, and the markup can only repeat what the post already says. It is one small piece of a bigger idea: posts written in answer shape, anchored to your real products, so the machines that decide what to recommend have something specific to quote.

FAQs

Does FAQ schema still do anything for Google?

Not visibly. Google retired FAQ rich results on May 7, 2026, so the markup produces no search feature, and Google's documentation says special structured data is not a requirement for AI Overviews either. Unused structured data is harmless, so existing markup can stay where it is.

Will FAQ schema get my store quoted by AI assistants?

Not on its own. Assistants quote the visible text of a page, and clear self-contained answers are what get lifted. The markup helps the crawlers that do parse structured data label those answers correctly, which makes it worth adding, but the answers do the work.

How many questions should one post have?

Three or four. Every question in the markup must also appear in the visible post, so the limit is really how many real customer questions the post genuinely answers. Padding a block to five or six weak questions gives a reader nothing and gives a machine less, not more.