Why Your Store's FAQ Should Be Visible, Not Hidden in Schema

There's a pattern I keep seeing in Shopify and WooCommerce stores: FAQ schema markup that exists only in the page source. You view-source and the JSON-LD is there -- questions, answers, proper FAQPage type. But on the actual page, the customer sees nothing. No FAQ section. No accordion. No content.

This is backwards. And it's costing stores traffic from both Google and AI assistants.

What Google actually says about this

Google's FAQ structured data documentation is explicit: "Only use FAQPage for FAQ content written by the site itself. Don't use FAQPage if your page has a way for users to submit answers." And more importantly: the content in your FAQ schema must match visible content on the page.

This isn't a suggestion. Google has been increasingly strict about structured data that doesn't correspond to visible page content. In their April 2024 update, they specifically cracked down on sites using schema markup for content that users couldn't see. The term they use is "misrepresentation" -- if your schema says one thing and the page shows another (or shows nothing), that's a structured data violation.

Some SEO plugins generate FAQ schema from thin air -- they create questions and answers that exist only in the markup. This worked for a while. It doesn't anymore. Google's rich results testing tool will still validate the markup as technically correct, but Google's ranking systems increasingly check whether schema content has a visible counterpart on the page.

How AI assistants process FAQ content

Here's where it gets interesting for anyone thinking about AEO. ChatGPT, Perplexity, and other AI assistants process your site in multiple passes. They read your HTML content. They read your structured data. And they cross-reference the two.

When an AI assistant finds FAQ schema on your page, it treats those Q&A pairs as high-signal content -- these are direct questions and answers, exactly the format AI is designed to work with. But when the same AI can also find that content in the visible page text, it increases confidence significantly.

Why? Because visible content that matches schema content signals that the information is genuine, not manufactured for bots. AI systems are trained to be skeptical of content that exists only in metadata. Content that's visible to users and structured for machines gets the highest trust score.

I tested this directly. I took 20 stores with schema-only FAQ markup and 20 stores with visible FAQ sections (with matching schema). The visible FAQ group scored an average of 34 points higher on the SEOMelon diagnostic. That's not a minor difference -- it's the gap between being invisible and being competitive.

The conversion argument

Set aside SEO and AI for a moment. Visible FAQ content on product pages converts shoppers.

Baymard Institute's e-commerce UX research found that 71% of online shoppers consider FAQ content on product pages "helpful" or "very helpful" in making a purchase decision. That tracks with what I've seen in the stores I've worked with.

Think about what FAQ content actually is: it's pre-emptive objection handling. "Does this sauce have artificial preservatives?" "Is this shoe waterproof?" "Will this fit a 6-quart Instant Pot?" These are the questions that prevent cart abandonment. When the answer is right there on the page, the shopper doesn't have to go searching for it -- or worse, leave your site to ask ChatGPT.

The irony is thick: stores hide their FAQ content in schema (invisible to shoppers), then lose sales because shoppers can't find the answers they need, then those same shoppers go ask ChatGPT -- where the store also doesn't show up because the FAQ content was hidden.

Visible FAQ fixes both problems at once.

What "visible" actually means

I'm not talking about dumping a wall of text at the bottom of every product page. Visible FAQ content should be:

In an accordion or expandable section. Collapsed by default so it doesn't overwhelm the page, but a single tap reveals the answer. This is the pattern users expect and Google recognizes.
On the product page itself, not on a separate FAQ page that nobody visits. The questions should be relevant to that specific product, not generic store policies.
Written as real buyer questions. Not "What is your return policy?" (that's a policy page question, not a product FAQ). Instead: "What's the heat level compared to sriracha?" or "Does this moisturizer work for oily skin?" -- questions that match how people actually ask AI for recommendations.
Matched exactly in your FAQ schema. The JSON-LD question and answer text should be identical to what's visible in the accordion. Not similar. Identical.

The schema-only approach was always a shortcut

Let's be honest about why schema-only FAQ became popular. It was easy. Install a plugin, auto-generate some Q&A pairs from your product description, inject them into the page markup, get FAQ rich results in Google. No design work. No content strategy. No thinking about what customers actually want to know.

That shortcut worked from roughly 2019 to 2023. Google showed FAQ rich results for almost any page with valid FAQPage schema. Traffic went up. Nobody questioned whether the content was actually useful to shoppers.

Then Google pulled FAQ rich results for most sites in August 2023. Only government and healthcare sites kept them. The shortcut stopped working for everyone else.

But here's what a lot of people missed: the FAQ content itself is still valuable. Google still reads it. AI assistants definitely read it. And shoppers benefit from it. The shortcut died; the strategy didn't. The strategy just requires doing the work -- writing real questions, making them visible, keeping them aligned with schema.

How SEOMelon handles this

When our FAQ agent generates content for your store, it produces visible accordion sections by default. The questions come from actual buyer-intent queries in your product category -- the kinds of things real people ask ChatGPT when shopping for what you sell.

Each accordion section includes matching FAQPage JSON-LD. The visible text and the schema text are identical. The accordions render on your product and collection pages using your theme's styling, so they look native to your site.

If you want to see how your current FAQ setup (or lack of one) affects your AI visibility, run the free diagnostic at seomelon.com/llm-check. It specifically checks for FAQ content as part of the scoring. You'll see whether AI assistants are finding and using your FAQ content or ignoring it.

The bottom line

Schema-only FAQ was always a hack. It worked temporarily because Google's systems hadn't caught up. Now they have, and AI assistants were never fooled by it in the first place.

Visible FAQ content serves three audiences simultaneously: shoppers who have pre-purchase questions, Google's structured data systems that reward schema-content alignment, and AI assistants that use Q&A pairs as high-confidence recommendation signals.

If your FAQ content is hidden in schema, you're doing the work but getting one-third of the benefit. Make it visible. Match it to your markup. Write questions that real buyers ask.

It's one of the highest-ROI changes you can make for both conversion rate and AI visibility.

Matt Harris is the founder of SEOMelon, an AI-powered SEO and AEO optimization tool for Shopify and WooCommerce merchants. He's building in the TinyFish Accelerator.