Collection FAQ
Add questions and answers to your collection pages, generate them with AI, and place the block on any page.
Collection FAQs answer the questions shoppers ask while they are still browsing a range, before they have picked a product: how the sizes run across the range, what the products have in common, how to choose between them.
They are usually worth more than product FAQs for search and AI visibility. A collection page is the page that ranks for the broad, high-intent search — "waterproof walking boots" rather than one boot — and a question-and-answer pair is the format AI systems most readily quote.
📸 Screenshot needed — the Product FAQ page with the Collections tab selected, showing the collection list on the left and the FAQ editor in the middle.
Where to find it
Collection FAQs live on the same page as product FAQs. Open Product FAQ and switch to the Collections tab.
Everything works the same way as the Products tab — pick a collection on the left, then add, generate, connect, reorder and edit entries in the middle. The only difference in the list is that each row shows how many products the collection contains instead of a variant count.
One FAQ library, two places to use it
Product and collection FAQs share a single library. The same saved entry can be attached to any number of products and any number of collections.
That means an answer like "Do you ship internationally?" is written once and attached wherever it is relevant. When you edit an entry that is used in more than one place, Product Pelican asks whether you want to update it everywhere or make a separate copy for the one you are editing.
Use Connect existing to attach an entry you have already written — the picker shows how many products and collections each one is currently used on.
Generating with AI
Click Suggest FAQs and Product Pelican reads the collection: its title, description, how many products it holds, a sample of those products, and the real facts about the range — the brands in it, the product types, the option spread and the price range.
Because it is working from the actual contents of the collection, the answers can be specific about the range rather than generic.
Links to related collections
Collection FAQ answers can link to your other collections, exactly as collection descriptions do. Product Pelican works out which collections are genuinely related — from your navigation menus first, and from shared products where there is no useful navigation — and offers those to the AI as link targets.
Only URLs Product Pelican supplied are ever kept. If the AI invents a link, it is stripped out before you see the suggestion, so an FAQ can never publish a broken URL.
When generation is unavailable
The Suggest FAQs button is disabled until a collection has a description of at least 200 characters.
AI suggestions inherit the quality of what they are written from, and a collection with an empty description gives the AI nothing specific to work with. Write the description first — the Collection audit page can generate one for you — then come back.
Plan limits
On the Free plan, AI FAQ generation covers up to 10 collections, counted as collections with at least one FAQ assigned. This is separate from the 10-product allowance, so using one does not consume the other. Any paid plan removes both caps, and writing FAQs by hand is never limited.
Showing them on your storefront
Add the Collection FAQs block in your theme editor. Unlike the product block, it is not restricted to one type of page — you can add it to a collection page, your homepage, or any landing page.
The block has one extra setting:
Collection
Empty
Which collection's FAQs to show. Leave it empty on a collection page and it uses the collection being viewed. Pick one to show a specific collection's FAQs anywhere else.
Every other setting — heading, output style, accordion, colours, custom CSS, structured data — works exactly as it does on the product FAQ block.
On a homepage or landing page you must pick a collection. There is no collection in context on those pages, so the block stays empty until you choose one in its settings. In the theme editor it tells you this; on the live page it simply renders nothing.
Structured data
The block emits schema.org FAQPage markup for the collection's questions, the same as the product block, and for the same reason: it hands search engines and AI crawlers each question and answer in a format they parse directly.
If another app already emits FAQPage markup on your collection pages, turn one of them off to avoid duplicate structured data.
Related pages
Product FAQ — the same editor, for products.
Collection audit — write the collection descriptions that FAQ generation needs.
AI prompts — edit the collection FAQ prompt under Collections → FAQ Generation.
Plans & billing — FAQ generation limits per plan.
Last updated