Easy Ways to Add an FAQ to Your WooCommerce Store

How-to WooCommerce By the Jompom team 12 min read

How do you add an FAQ to a WooCommerce store?

Cut support emails and returns with a WooCommerce FAQ. Here’s what to answer, three easy ways to add it, and what FAQ schema still does in 2026.

The quickest way to add a WooCommerce FAQ is a dedicated FAQ page built with the block editor’s Details block, plus short product-level answers in a custom product tab. Neither needs a paid plugin. Below you’ll find which questions are worth answering, three ways to put them on your store, how FAQ structured data works today, and how to stop your answers going stale.

Why a WooCommerce FAQ is worth the effort

Every online shop gets the same handful of questions again and again. How long does delivery take? Can I return this? Will it fit? Does it work with what I already have? Each time a shopper has to email you to find out, two things can happen: they wait, or they leave. A clear FAQ answers them on the spot.

A good WooCommerce FAQ pays off in three ways:

  • Fewer support emails. If the answer is one click away, most people won’t write in. That frees up time you’d otherwise spend typing the same reply about delivery times.
  • Fewer returns. Many returns happen because the product wasn’t what the buyer expected: wrong size, wrong material, not compatible. Answering those questions before the sale means fewer surprises after it.
  • More confident buyers. Shoppers can’t pick up your product or ask a sales assistant. Plain answers about shipping, payment and returns make your shop feel open and trustworthy, which matters most to first-time customers who don’t know you yet.

An FAQ also helps you. Writing it forces you to spell out your policies clearly, and it gives search engines and AI assistants more plain-language text about what you sell and how you work.

WooCommerce FAQ illustrated as a product page with an open question accordion and a FAQ tab
Illustration: answer the questions before they reach your inbox, on an FAQ page and right on the product.

What questions should your WooCommerce FAQ answer?

Don’t guess. The best questions come from the people who already write to you. Go through your inbox, contact form entries, order notes, live chat logs and return reasons from the last few months, and list every question that comes up more than once. Product reviews and questions on marketplaces where you also sell are good sources too.

Most stores end up with questions in two groups.

Store-wide questions

  • Delivery: where you ship to, how long it takes, what it costs and whether there’s a free-delivery threshold.
  • Returns and refunds: how long customers have, who pays return postage and how long a refund takes to arrive.
  • Payment: which methods you accept and when the card is charged.
  • Orders: how to track an order, change it or cancel it.
  • Accounts: whether shoppers need an account to buy and how to reset a password.
  • Taxes and duties: whether prices include VAT or sales tax, and whether overseas buyers may pay import charges.

Product-level questions

  • Size and fit: how a garment runs, or the exact dimensions of a piece of furniture.
  • Materials and care: what it’s made of and how to clean it.
  • Compatibility: which models, devices or versions it works with.
  • What’s in the box: accessories, batteries, cables and what isn’t included.
  • Warranty: how long it lasts and how to claim.

Keep each answer short and direct. Lead with the actual answer (“Yes, we ship to the EU”), then add the detail. If a policy has a longer page, such as your returns policy, summarise it in two sentences and link to the full version rather than copying it.

Build a store FAQ page with the Details block

For store-wide questions, a single FAQ page is the simplest option, and WordPress can do it without any plugin. Since WordPress 6.3, the block editor includes a Details block. It shows a heading the visitor can click to reveal the answer underneath, which is exactly the accordion layout most FAQ pages use.

Here’s how to build your WooCommerce FAQ page:

  1. Go to Pages → Add New Page and give it a clear title, such as “FAQ” or “Help & FAQs”.
  2. Add a Heading block for each group of questions (Delivery, Returns, Payment and so on), so the page is easy to scan.
  3. Click the + inserter, search for Details and add the block. Type the question in the summary line.
  4. Type the answer in the paragraph inside the block. You can add more blocks inside it, such as a list or a link to your full returns policy.
  5. Repeat for each question. Duplicating a finished block (from the block toolbar’s options menu) saves a lot of clicks.
  6. Publish, then add the page to your header or footer menu and link it from your cart and checkout area.

Behind the scenes the Details block outputs the standard HTML <details> and <summary> elements. That’s good news: browsers handle the open-and-close behaviour themselves, it works with a keyboard and screen readers, and it doesn’t load any extra JavaScript. The block also has an option to open by default, which is handy for your single most important question.

One tip: don’t hide everything. If your page has only five or six questions, plain headings and paragraphs may be easier to read than accordions. Accordions earn their place once the page gets long.

Add product FAQs with a custom product tab

Store-wide answers belong on the FAQ page, but questions about one product belong on that product’s page, right where the buyer is deciding. WooCommerce product pages already show tabs such as Description, Additional information and Reviews. You can add your own FAQ tab with the woocommerce_product_tabs filter.

The snippet below adds an “FAQ” tab, but only to products that actually have FAQ content, so you don’t end up with empty tabs across the shop. The content comes from a custom field called product_faq.

add_filter( 'woocommerce_product_tabs', function ( $tabs ) {
	$faq = get_post_meta( get_the_ID(), 'product_faq', true );

	if ( '' === trim( (string) $faq ) ) {
		return $tabs;
	}

	$tabs['product_faq'] = array(
		'title'    => __( 'FAQ', 'your-text-domain' ),
		'priority' => 25,
		'callback' => function () use ( $faq ) {
			echo '<h2>' . esc_html__( 'Frequently asked questions', 'your-text-domain' ) . '</h2>';
			echo wp_kses_post( wpautop( $faq ) );
		},
	);

	return $tabs;
} );

A few notes on how it works:

  • Where to put it: in your child theme’s functions.php or a small custom plugin, not in the parent theme, where the next theme update would wipe it out. A code snippets plugin works too.
  • Priority: WooCommerce’s default tabs use 10 (Description), 20 (Additional information) and 30 (Reviews), so 25 places the FAQ tab between the last two.
  • Safety: wp_kses_post() strips anything that isn’t allowed in post content, so a stray script in the field can’t run on your product page. wpautop() turns line breaks into paragraphs.

To fill the field, open a product, and look for the Custom Fields panel below the editor. If you can’t see it, open Screen Options at the top of the screen and tick Custom Fields. Add a new field named product_faq and type your questions and answers as short paragraphs. The name has no leading underscore on purpose: fields starting with _ are hidden from that panel.

If you’d like a nicer editing box than the raw Custom Fields panel, a custom-fields plugin can give the same product_faq field a proper text area on the product screen. The tab code stays the same.

Always test a change like this on a staging copy first. A typo in functions.php can take the whole site offline, which is the last thing you want on a shop.

Use an FAQ plugin

If you’d rather not touch code, or you want features the two methods above don’t have, an FAQ plugin is the third route. The WordPress.org plugin directory has plenty of them, and they tend to fall into a few types:

  • Accordion and FAQ block plugins add styled accordions with more design options than the core Details block, such as icons, colours and “expand all” buttons.
  • Product tab plugins let you add FAQ tabs (and other tabs) to WooCommerce products from the admin screen, sometimes with global tabs shown on every product in a category.
  • Knowledge base plugins build a full help centre with categories, search and article pages. They make sense for stores with a lot of technical products.
  • SEO plugins such as Yoast SEO and Rank Math include an FAQ block of their own that adds structured data for you.

When choosing one, check the basics: when it was last updated, whether it’s tested with your WordPress version, how it handles accessibility, and how much extra CSS and JavaScript it loads on every page. Each plugin is one more thing to keep updated, so pick one only if it does something you actually need.

Which WooCommerce FAQ method should you use?

Most stores combine two of these: a store-wide FAQ page plus product FAQs on the products that need them.

Ways to add a WooCommerce FAQ compared
MethodBest forNeeds code?Effort
FAQ page with Details blockDelivery, returns, payment and other store-wide questionsNoLow
Custom product tabSize, fit, compatibility and other product-specific questionsA short snippetMedium
FAQ pluginStyled accordions, global tabs or a full help centreNoLow to set up, ongoing updates
Product descriptionOne or two quick answers on a single productNoLow

That last row is worth remembering. If a product only needs one answer, such as “Batteries not included”, put it in the short description near the Add to basket button. Not every answer needs its own tab.

Should you add FAQ schema to your WooCommerce FAQ?

FAQ schema is structured data, usually JSON-LD, that labels your questions and answers using the FAQPage type from schema.org. Search engines read it to understand that a page contains a list of questions with answers.

For a few years, FAQ markup could make Google show your questions as expandable rich results right under your listing. That has ended in two steps. In August 2023, Google limited FAQ rich results to well-known, authoritative government and health websites. Then in May 2026 it stopped showing the FAQ rich result altogether and removed its documentation for it, as noted in the Google Search Central changelog. So adding FAQPage markup to your shop will not bring back those drop-downs in Google results.

Is it still worth adding? It does little harm, and some sites keep it because it describes the page’s content in a clean, machine-readable way that other search engines and tools may still read. But don’t add it expecting more clicks from Google. The visible FAQ is what does the real work, for shoppers and for search engines alike. If you do keep the markup, stick to the long-standing rules:

  • Every question and answer in the markup must be visible on the page. Don’t mark up text that visitors can’t see.
  • Use it for questions you answer. Pages where customers post questions and others reply are a different type (QAPage).
  • Don’t use FAQ markup for advertising copy.
  • Don’t add the same FAQ markup to many pages. If one set of shipping questions appears on every product, mark it up once, on your FAQ page, if at all.

The easiest route is the FAQ block in your SEO plugin, which writes the markup for you. Adding JSON-LD by hand is possible, but it’s one more thing that can fall out of sync with the visible text when you edit an answer. Note that WooCommerce already adds its own Product structured data to product pages, so leave that in place and treat FAQ markup as an optional extra.

Keep your WooCommerce FAQ up to date

An out-of-date FAQ is worse than none. If your FAQ says delivery takes three days but your courier now takes five, customers will quote your own page back at you, and some will ask for refunds. A few habits keep answers accurate:

  • Update the FAQ in the same task as the policy. When you change shipping rates, return windows or payment methods, put “update the FAQ” on the same to-do list.
  • Review it on a schedule. Read the whole FAQ every quarter and before busy periods like Black Friday or the holidays, when cut-off dates and delivery times change.
  • Keep listening. When a new question shows up in your inbox three times, add it. When nobody has asked a question in a year, consider removing it.
  • Put one fact in one place. Write each policy detail once and link to it, rather than repeating “30 days” on twenty pages. One edit then fixes it everywhere.
  • Check the page still works. After WordPress, WooCommerce or theme updates, open your FAQ page and a product with an FAQ tab to make sure the accordions and tabs still behave.

That last point is where FAQ upkeep overlaps with general store maintenance. Theme and plugin updates are the most common reason a custom tab or accordion suddenly looks broken, so it pays to update on a staging site or straight after a fresh backup. Our WooCommerce maintenance service covers that routine if you’d rather not do it yourself.

The bottom line

A WooCommerce FAQ is one of the cheapest ways to improve a store. Collect the questions customers already ask, answer store-wide ones on an FAQ page built with the Details block, and add product-level answers in a custom tab where they’re needed. Use a plugin only if it gives you something you can’t get otherwise, treat FAQ schema as optional now that Google no longer shows FAQ rich results, and review your answers whenever your policies change.

Frequently asked questions

No. WordPress’s built-in Details block creates an accordion-style FAQ page without any plugin, and a short woocommerce_product_tabs snippet adds FAQ tabs to products. A plugin is only worth it if you need extra design options or a full help centre.

Link it from your main menu or footer, and from the places where questions come up: the cart, checkout, delivery information and returns pages. Shoppers should find it without searching.

No. Google limited FAQ rich results to government and health sites in 2023 and stopped showing them in May 2026. The markup is harmless and other tools may read it, but it won’t add drop-downs to your Google listing. A clear, visible FAQ on the page is what helps.

As many as your customers genuinely ask, and no more. Many stores start with 10 to 20 store-wide questions grouped by topic, plus a few on the products that need them. Short and accurate beats long and padded.

Yes. Jompom doesn’t write your FAQ for you, but our plans handle the upkeep around it: WordPress core, plugin and theme updates, cloud backups, uptime monitoring and security scans, with a report for every task and fixes done by a WordPress expert. See the plans.

Written by the Jompom team

We safely update WordPress core, plugins and themes, and keep sites online, secure and fast. 12+ years of WordPress work, with a team of 60+ developers and web experts.

Found this useful?

WordPress care on autopilot

Let our team handle the updates, backups and security scans, with a report for every task. You get back to running your business.