A Shopify FAQ page and a product FAQ answer different questions. Shipping policy, return windows, and "where is my order" belong in a store FAQ. Fabric, fit, fill weight, and compatibility belong on the product. Putting both in one long list makes the product page noisy and makes the help page useless for the shopper who only wanted the hem length.
Product FAQs for AI Crawler supports both scopes in the same app. Leave the product assignment empty and the group is shop-wide. Attach products and the group is a product FAQ, shown on those product pages. The catalog names four templates: Accordion, Grid/cards, Boxed, and Minimal. Accordion is the usual product-page accordion FAQ. The other three are available on the block when a page needs a different shape.
Two scopes, one rule
The rule is assignment. A group linked to specific products displays only on those product pages. The product-page section block reads that product's FAQ metafield. A group with no assigned products is the global FAQ. The page-section block places it on a page you add in the theme editor, which is how a store FAQ page gets its list. A body-level app embed loads the FAQ script for the store so those blocks can render.
You can keep more than one group. A linen shirt can have its own fabric and care answers. A shop-wide group can hold delivery times and the returns window. The shirt page should not repeat the entire returns policy if the global page already states it, unless the shirt is an exception. Exceptions belong on the product, in a sentence that names the exception.
| Scope | How you set it | Where it shows |
|---|---|---|
| Product FAQ | Assign products in the resource picker | Those product pages, from the product metafield |
| Store FAQ | Leave products empty | The page where you place the global block |
Which questions go where
Use the product list for anything that would be false on a different item. "This tee is 100 percent cotton" is false on a wool sweater, so it stays on the tee. "Orders placed before noon ship the next business day" is a store rule, so it stays in the global group, and only if operations still honors it. Mixed lists are how shoppers lose trust: they apply the sweater's care line to the tee because both answers sat on one page.
Categories help you keep the admin tidy. You can create, rename, and delete categories, and the list shows a usage count. Deleting a category does not delete its FAQs. It clears the category on those groups. Tags and status sit on the group as well. The admin list can filter by category and by name, and it splits groups across status tabs. That is an admin search. It is separate from the search box a shopper sees on the storefront widget.
- Fit, materials, care exceptions, and compatibility stay on the product.
- Shared shipping, returns, and wholesale contact rules can live in the global group.
- If only one collection is an exception, say so on those products rather than burying the exception in the store page.
Templates, search, and Load More
The template is chosen per block, not forced to be the same everywhere. A product page often wants Accordion, because the shopper is beside the price and needs one answer open at a time. A store FAQ page with many policies can use Grid/cards so questions are visible without a long stack of closed rows. Boxed separates each question. Minimal keeps the type quiet. Pick the one that matches the page, then preview it.
The widget includes a live search box. It filters by a substring of the question text and the answer text as the shopper types. On a store FAQ page this matters, because shipping and returns will not be the first row forever. Load More reveals hidden items in batches. The batch size is the pagination setting on the group. Both controls filter or reveal the FAQ list. They do not search the product catalog.
Both the product block and the global block emit FAQPage JSON-LD in the light DOM, outside the widget's shadow DOM. The markup is built from the FAQ data, with HTML stripped from the text and the result escaped so the JSON-LD stays valid. That gives a crawler the questions without running the widget script. It is not a promise that a search engine will show a special result, and it is not a reason to paste the same answers into a blog post as code.
One embed, two blocks
Merchants sometimes add only the app embed and then wonder why a page is empty. The embed loads the script site-wide. The product block has to sit on the product template to read that product's metafield. The page block has to sit on the FAQ page to show the shop-wide group. Place each block once, on the template that should display it, and check a product that has an assignment and a product that does not.
Saving a group writes its fields, items, and product links again. If you move a question from a product group into the global group, edit both groups and save. The storefront will not invent that move. Content is pre-baked into metafields at save time. Creation, whether you type the rows or generate them, is subject to a monthly limit. The catalog does not publish the number. Read it on the plan screen before you promise a large help center in one afternoon.
Questions about product and store FAQs
Can one group be both product and global?
No. Products assigned means product pages. No products assigned means shop-wide. Use two groups when you need both.
Which template should a product page use?
Accordion is the default and the usual fit beside a description. Grid/cards, Boxed, and Minimal are there when the page needs them. The choice is per block.
Does widget search find products?
It filters question and answer text inside the FAQ widget. Shopify product search is a separate box.
The listing, if you install the app, is Product FAQs for AI Crawler.
Compare the two scopes on Product FAQs for AI Crawler. Move fabric answers onto the product, leave store policy in the global group, and delete the duplicate rows from the page that should not have carried them.