Shoppers email the same product questions when the page never answers them. A size that runs small, a fabric that cannot be tumble dried, or a ship window measured in business days will keep arriving until the product page says it in plain text. Put that answer in a Shopify product FAQ, under the description, where the person is already deciding whether to buy.
Product FAQs for AI Crawler can hold questions on the products you assign, and a separate shop-wide group when the answer is true for the whole store. The text is saved into Shopify metafields, so the storefront reads that saved copy and does not call the app just to draw the list. The product block and the shop-wide block also emit FAQPage JSON-LD in the light DOM, outside the widget, built from those same questions and answers. A monthly creation limit exists under Shopify Managed Pricing. The feature catalog does not publish the number or a price, so the plan screen inside the app is the place to read the figure that applies to the shop.
Questions worth publishing on the product
Start with the replies your support team already pastes. If several people asked whether a coat is waterproof this week, that question belongs on the coat. If the return window is the same for every product, it can live in a shop-wide group instead of being copied onto every item. Skip a question that only repeats the product title. A shopper who is looking at the navy coat does not need an FAQ that asks whether this is the navy coat.
Write the fact in the first sentence. An inseam, a fiber content, or a handling time is usable. A slogan about real life is not. An FAQ also does not refund an order, reprint a shipping label, or replace the policy page checkout already links. It tells the shopper what you will do. The order and the policy page still do the work.
Product FAQs and a shop-wide group
Assignment is the split. Attach products with Shopify's resource picker and that group shows on those product pages, through the product-page block that reads the product's FAQ metafield. Leave the product assignment empty and the group is shop-wide. A page-section block displays that global group on a page you choose, such as a help page. Shipping policy and a product's fabric do not belong in the same list, even when both are honest answers.
A body-level app embed loads the FAQ script across the store. You still place the product block on the product template and the page block on the page that should show the global list. Editing a group saves its fields, its question and answer pairs, and its product links again. The storefront keeps using the metafield copy from that save. Display does not depend on a live call to the app. Analytics logging is the request the storefront still makes.
- Product group: assigned products, shown on those product pages.
- Shop-wide group: no products assigned, shown from the page block.
- Saved copy: question and answer text stored in metafields at save time.
- Crawler copy: FAQPage JSON-LD in the light DOM, outside the widget shadow DOM, with question and answer text stripped of HTML and escaped for valid JSON-LD.
Four layouts on the product page
Each block can use one of four templates. Accordion is the default: a compact list that opens an answer when the shopper chooses it. Grid/cards lays the questions out as cards, which suits a longer help page people scan. Boxed puts each question in its own box. Minimal uses quieter rows when the theme is already sparse. The template is chosen per block, so a product page and a help page do not have to share a look.
The widget renders inside a shadow DOM, which keeps most theme CSS from restyling the list. That is isolation. It does not copy your theme font, spacing, or button shape by itself. Open a real product on a phone after you pick the template. A desktop preview of the theme editor is a weak test for a question someone will read beside the add-to-cart button.
Long lists can include a search box that filters by a substring of the question and of the answer as the shopper types. A Load More control reveals further items in batches set by the group's pagination size. Search here filters the FAQ widget. It does not replace the store's product search. Use it when one product, or the shop-wide page, carries more answers than a person will open one by one.
How a monthly creation limit fits the work
Managed Pricing checks a monthly FAQ-creation limit on manual creation and on AI generation. When the shop reaches that limit, creation is blocked and the app shows an upgrade prompt. The catalog records that this check exists. It does not record a product count or a dollar amount. Staff guides should quote the number from the plan screen in the app, not a figure copied from an old note.
You can type every question yourself. A group has a name, a category, tags, a status, a template, a pagination size, and as many question and answer pairs as you add. AI generation is a second path: the app can draft from the product title, description, vendor, and type, or from a description you write, and those drafts stay editable before you save. Either path is subject to the same monthly creation check. A draft you have not saved is not yet the answer on the product page.
Categories can be created, renamed, and deleted. Deleting a category keeps the FAQs and clears their category assignment. The admin list also has status tabs, name search, category filtering, and delete.
Questions merchants ask about product FAQs
Will an FAQ stop support email?
It can answer the shopper who reads the page before they write. It will not catch the shopper who never scrolls, and it will not resolve an order that is already late. Treat a drop in repeat questions as something you observe in the inbox, not as a rate the app promises.
Where do I read the creation limit?
On the plan screen in the app. The feature catalog confirms that a monthly limit is enforced and that an upgrade prompt appears when it is reached. It does not publish the number.
Does the FAQ replace my returns page?
No. A short answer can point at the rule, such as the number of days and whether the shopper pays return postage. The full policy page is still the page checkout and footers should link.
Install Product FAQs for AI Crawler only after the plan screen shows a limit the shop can live with.
Read how groups, layouts, and the light-DOM FAQ markup work on Product FAQs for AI Crawler. Put the three answers you pasted most often onto one product this week and see whether those threads get shorter.