Should Every Category Still Have FAQs in 2026?

⏱ 11 min read

FAQ category page SEO changed on 7 May 2026, when Google dropped FAQ rich results in Search, the expandable question dropdowns that once padded out a listing. For most stores that feature had already been dead since August 2023, when Google narrowed it to well-known government and health sites, so the snippet most teams chased has not worked for commercial pages in years.

The timing matters. Question-shaped content is more visible than ever. As of March 2026, AI Overviews appeared on roughly 48% of tracked Google queries, up from about 34.5% three months earlier, and they cluster on informational, question-form searches, where coverage runs highest. These figures move month to month, so treat them as a direction. The direction reframes ecommerce FAQ content as an AI-search asset rather than a rich-result trick.

So the real question is not whether FAQs keep their dropdown. It is whether a Shopify collection FAQ still earns anything now that the dropdown is gone for everyone. The short answer is sometimes, and not for the reason most teams assume. This guide covers what changed, what the data on category-page content shows, and a simple rule for deciding which FAQ blocks to keep. If you run this in-house, it also ties into the rest of your Shopify SEO tips.

What Actually Changed With FAQ Rich Results

The change was a three-year retreat, not a single event. Google reduced FAQ visibility in 2023, limited it to government and health sites, then removed it for every site in May 2026, with the reporting and testing tools following in stages. Here is the timeline that matters for planning.

One point gets lost in the noise. FAQPage is still a valid Schema.org type. Google’s FAQ structured data documentation, updated on 7 May 2026, says the rich result is gone but that Google still uses FAQ structured data to understand pages, and that adding or removing the markup does not change rankings. The display feature ended. The markup is not banned, and there is nothing to panic-delete. For FAQ category page SEO, the visible content stays valuable even though the snippet is gone.

Do Category FAQs Still Help SEO, and Should You Keep the Schema?

Two questions get asked together, so answer them together. FAQ category page SEO still works, but indirectly, and never through the rich result. Rankings on a collection come from relevance to the query, topical coverage, internal links, and how cleanly the page answers buyer intent. A good FAQ feeds all of those: it resolves objections that block the sale, adds named entities and long-tail question coverage, and gives a natural place to link to a deeper guide or a related collection. A well-scoped category page FAQ keeps the page focused on one buyer question at a time, the same discipline you would apply to technical SEO for Shopify.

The schema is a separate matter, and here the rule is narrow. Adding or removing FAQ markup does not change rankings, because Google does not use rich results as a ranking input. That is a statement about the markup, not the content: the visible questions and answers still affect relevance, because they are part of what the page says. So keep FAQPage schema wherever it accurately describes visible Q&A on the page, and remove it only where it points to content that no longer exists or was added purely for the old snippet. Treat it as a governance pass alongside your Shopify product schema, not an emergency.

One housekeeping step before the deadlines: export any FAQ appearance data you still want from Search Console before the June 2026 report removal and the August 2026 API cutoff. After that the reporting is gone, but the content decision stays the same.

What the Data Says About Category-Page Content

The instinct to bulk up category pages with content, FAQs included, is not what the top of the SERP looks like. In Digitaloft’s 2025 study of 300 category pages ranking first on Google UK for commercial terms, the average page carried just 310 words of unique content. Two-thirds sat under 400 words, and nearly half under 200. Where an FAQ appeared, it was part of that small budget, which is why lean, specific ecommerce FAQ content beats padding.

About 10% of those top pages had no content at all beyond the H1, and most of them belonged to household-name brands trading on authority and brand search. If you are not one of those brands, zero content is not a strategy. But neither is a wall of text. The winning pattern was consistent: a tight, value-led intro above the product grid, with a short, targeted FAQ below it where the category genuinely needs one.

Why FAQs Still Matter for AI Search

The dropdown left just as question-shaped content became more valuable. Shopping is now firmly in scope: AI Overviews reached 14% of shopping queries by March 2026, up from 2.1% four months earlier, across a study of 20.9 million shopping SERPs (Search Engine Land, Visibility Labs). These figures move month to month, so treat them as a direction, not a fixed number. The direction is clear: the surfaces that quote you are expanding into commerce, and a Shopify collection FAQ is one of the cleanest sources you can hand them. This is where FAQ category page SEO now earns its keep, through visibility in AI answers rather than a SERP dropdown.

An FAQ is not just tidy, it fits how retrieval works. AI answers are assembled by splitting a page into passages, turning each into a vector embedding, and matching those against the meaning of the query. A self-contained question and answer pair is a clean passage: its meaning does not depend on the paragraph above it, so it embeds precisely and can be quoted without dragging in unrelated text. The question line also mirrors how people phrase searches, which tightens the match. A sentence that leans on “as mentioned above” breaks the moment it is lifted out of context, so it rarely gets pulled. Bing, Perplexity, and ChatGPT search still parse the markup, but what they extract and cite is the visible answer text. That is also why it pays to write for a broader content cluster strategy, where each answer can stand on its own.

So Should Every Category Have FAQs?

No. Blanket FAQs on every collection is how you end up with thin, duplicated, generic questions that dilute intent and add nothing. The same five questions copy-pasted across 40 collections is not FAQ category page SEO. It is filler with a schema wrapper. The right approach is selective, based on whether a real shopper on that specific collection would ask a question that changes a decision.

The rule of thumb: an FAQ earns its place when a genuine shopper on that collection would ask the question and the answer changes what they do next. If you cannot picture that shopper, the page does not need the block. The same audit that catches products not indexed will also surface duplicate or thin FAQ content across the catalogue.

What a Strong Shopify Collection FAQ Looks Like Now

Once a collection earns an FAQ, keep it disciplined. Three to six questions is plenty, phrased as real queries and tailored to that collection’s objections and USPs rather than to a keyword tool. Place the block below the product grid, with a short value-led intro above it, matching what the top-ranking pages in the study did.

Answers should run 40 to 60 words and stand on their own, with no “as mentioned above” that breaks when a machine lifts the chunk. Where an answer needs depth, link out once to the relevant guide instead of expanding the FAQ into an essay. Drawing questions from your support inbox and site-search logs, then linking to your own Shopify blog SEO content, beats anything guessed from a keyword list.

Put in concrete terms, the payoff is about citation eligibility, not a vanished dropdown. Take a “best trail running shoes” collection. A year ago that kind of query rarely produced an AI answer; by March 2026, AI Overviews covered 14% of shopping queries and were still climbing (per the Search Engine Land data above). Here is the before and after.

Before. The only FAQ asked “What are trail running shoes?” and answered with a definition. When Google or an assistant assembled an answer for “best trail shoes for beginners”, there was nothing on the page worth quoting, so the citation went to a review aggregator instead.

After. The FAQ answered the questions buyers actually ask, each as a self-contained 45-word chunk: “Which trail shoes suit beginners?”, “How much heel drop for long distances?”, “When should I replace trail shoes?”. Those passages are exactly what a retrieval system can lift, so the collection becomes eligible to be the cited source rather than the aggregator. How large the lift is depends on your catalogue and demand, but the mechanism is the same everywhere.

Whatever the category, a strong FAQ shares the same traits:

• Questions pulled from real support tickets and site-search logs.
• Answers that each resolve one objection, in 40 to 60 words.
• One outbound link per answer at most, only where depth helps.
• Schema kept only where it matches the visible answers.

Common Mistakes to Avoid

Most category-FAQ problems come down to a handful of repeatable errors. If you audit for these first, you will fix the majority of the damage before you touch anything else.

• Copy-pasting one FAQ set across every collection, creating near-duplicate content.
• Keeping “what is [product]” questions on pages where the shopper already knows.
• Turning the FAQ into a 1,000-word buying guide under the product grid.
• Adding FAQ schema with no matching visible answers on the page.
• Stuffing every answer with links instead of one useful next step.

Conclusion

Google retired a display feature, not the reason FAQs exist. FAQ category page SEO still earns its place when the block answers real objections and produces clean, question-shaped content that AI systems can lift and cite. It does not belong on every collection, and the data on top-ranking pages backs that up: lean, relevant, and specific wins. Audit your catalogue, cut the duplicated filler, and keep the ecommerce FAQ content that changes a decision. Then let the schema follow the content, not the other way round.