Tymoo Guidelines ยท Preview

FAQ markup lost its search payoff. The questions still matter.

Sources checked October 2026 | Last revised 2026-10-11 | Next review January 2027

By Chuck Aikens | I run Tymoo, a one-person consultancy for consumer product brands | 15 years of doing this work

Why it matters now

FAQs changed jobs in 2026. Google restricted the FAQ rich result in August 2023 and ended it on May 7, 2026, so the old reason to write FAQs, a bigger search listing, is gone. The reasons left are better ones: a shopper settles a doubt on the spot, Shopify offers store FAQs to AI platforms as "a trusted data source," and Google's product feed has a field built for product Q&A.

1. Markup: leave it, don't chase it

The rule

Don't add FAQPage markup to chase AI visibility. If your platform or plugin already emits it and it matches the visible text, leave it. Spend the effort on the visible text.

Why it works

  • Google ended the display. Its documentation changelog says: "This feature will no longer appear in Google Search starting May 7, 2026."
  • Google said unused markup does no harm in Search. "Structured data that's not being used does not cause problems for Search, but also has no visible effects in Google Search." So leaving it costs nothing in Search. Google says nothing there about AI answers.
  • The two strongest designs find no lift from markup. One large citation model reports schema with "no significant independent effect detected in this sample." The same agency's summary still lists schema among the items that "produce measurable citation lift," so its headline reads warmer than its model. An SEO software vendor's matched study of 1,885 pages that added JSON-LD of any type, against 4,000 controls, found a small but significant 4.6% decline on Google AI Overviews, which its authors say they "can't clearly attribute to schema," and gains indistinguishable from zero on AI Mode and ChatGPT. It looked at pages already cited by AI, over 30 days. Neither was FAQ-specific, and the matched study measured adding markup, not removing it.
  • The claims that it helps come from sellers. Two WordPress SEO plugins make the case for their FAQ blocks, and neither page backs its claim with a measurement. Two weaker designs do report markup adding something, one resting on 23 pages and one with no table. That's why I call markup's AI benefit unsupported, not disproven.

How to do it

  • Keep existing markup if it already matches the visible text.
  • Don't build new FAQPage markup, and don't score it.

2. Two jobs, brand and product

The rule

A brand FAQ holds what's true across the store: shipping, returns, payment, the company, sourcing, how the line fits together. A product FAQ holds only what's true of that one product: use, dose, ingredients, compatibility, who it's for and who it isn't. If a question has the same answer on every product page, it's a brand question.

Why it works

  • The split is my rule. No platform I read states it as a single rule. Google's and Shopify's pages point the same way, while OpenAI's feed carries shipping and returns on each product row.
  • Google draws the line for its product Q&A field. Google Merchant Center's question_and_answer attribute is for "User-, merchant-, and manufacturer-authored questions and answers about the product." Its specification also bars store-wide facts from that field: "Don't add information such as price, sale price, sale dates, shipping, delivery date, other time-related information, or your company's name."
  • Shopify keeps store policy on its own pages and links instead of copying: "A link to your shipping policy is listed on your product pages and your cart." That default applies to Shopify's free themes downloaded after November 2018, once a shipping policy is added.
  • OpenAI's product feed carries no Q&A at all: "Raw review entries and question-and-answer lists are not part of this discovery contract." So don't expect product Q&A to travel to ChatGPT through that feed.
  • A product FAQ earns its place by doing work nothing else on the page does. A restated policy has to be fixed in every copy after a change. One link, one fix.

How to do it

  • Sort every candidate question: whole store goes to the brand FAQ, one product goes to that product's FAQ.
  • Run the swap test. Put a different product in the question. If the answer is still true, it's a brand answer.
  • When a product FAQ touches shipping, returns or subscriptions, answer in a line and link the policy page. Keep prices, delivery dates and the company name out of product FAQ text.

3. Write for the reader, not for an AI lift

The rule

Write FAQs as visible page text, in the words a shopper would use, answering the doubts that stop a purchase. Don't pitch them internally as an AI visibility lever.

Why it works

  • The one study that separates FAQ content from markup finds a modest effect. An AEO agency analysed about 2 million citations across four engines and 10,000 cited pages. It calls FAQ sections "the strongest on-page signal we measured," at a coefficient of +0.07 on third-party pages, and adds: "Smaller and conditional on domain in the multivariate model." Matching how buyers phrase their prompts came in at +0.37.
  • It reports no coefficient for brand-owned pages, which is where your FAQ sits, and the sample leans B2B. Read the +0.07 as a direction on third-party B2B pages, not a forecast for yours.
  • The set disagrees with itself. The large positive FAQ figures come from the designs that separate content from markup least, and no study on the table is a controlled test on a live engine or tests consumer product pages.

How to do it

  • Start from real questions: support tickets, reviews, and, if you use Shopify's Knowledge Base app, its "Top unanswered questions" list.
  • Use the shopper's phrasing and open every answer with the answer.
  • Treat any citation lift as a bonus, and don't forecast one.
"FAQ answers should be 40 to 60 words."

The figure is a widened version of one SEO software vendor's 2016 measurement of featured snippets: "The most common length of content in Featured Snippets is between 40-50 words". The vendor reported a most-common value. Everyone after it turned that into a rule. It describes Google's snippet box, not AI answers, and the live article has since been rewritten with a softer line. My own 40 to 80 words is a readability rule, and I treat it as one.

The full Guidelines cover

What clients get

This Preview is three rules and one myth out of ten. Clients read the whole FAQ Guideline on app.tymoo.ai: every rule, the measuring method, the where-to-start order and the audit checklist, updated quarterly. Google's FAQ status changed twice in three years, so the quarterly re-read is the part that keeps it true.

Let's Connect →