FAQs

FAQs in Evident are answers you write, not a customer Q&A board. They exist to catch the objection a shopper has at the moment they have it.

Scoping

Every FAQ has a target type and, unless it is store-wide, a target:

Target type	Attaches to
PRODUCT	One product
CATEGORY	A category — inherited by everything in it
PAGE	A content page
BLOG	A blog post

An FAQ with no target is global and cascades into every FAQ widget on the store. This is the mechanism worth understanding: write shipping, returns and sizing answers once as globals, and every product page gets them without you touching a single product.

Suppress the cascade on a specific placement with data-no-global when a product needs to stand alone.

Writing them

FAQs → All FAQs. Question, answer, target, order.

Answers support formatting and links. Keep them short — an FAQ that runs to four paragraphs is a content page that has ended up in the wrong place.

The questions worth writing are the ones your support inbox already answers repeatedly. If you are guessing, you are writing marketing copy with a question mark on it, and shoppers can tell.

Displaying them

<div
  data-evident-widget="faq"
  data-target-type="product"
  data-product-id="PRODUCT_ID"
></div>

Three layouts via data-layout:

• Accordion — collapsed, click to open. Best when there are many.
• Dual column — two columns, all open. Good for four to eight.
• List — everything open in one column. Good for a handful you actively want read.

data-limit caps how many render.

Structured data

The widget emits FAQPage structured data, which is what makes FAQ rich results possible in search. There is nothing to configure — it comes with the widget.

Two things affect whether it does you any good:

• Google shows FAQ rich results selectively, and has narrowed the eligible sites considerably. Treat it as upside, not as the reason to do this.
• Duplicating the same global FAQs across every product page is fine for shoppers and unremarkable to search engines, but do not expect each page to win a rich result for identical content.

Importing

FAQs → Import / Export takes a CSV. Useful if you already maintain answers in a spreadsheet, a helpdesk, or another platform’s FAQ app.

What this is not

There is no customer-submitted question flow — no “ask a question” button that routes to your inbox and publishes the answer. If a shopper’s question is not answered, they still email you.

Whether you want that is a real product decision. Public Q&A produces content you did not write and cannot fully control, which is either its main virtue or its main risk depending on your category.