Choose the content and query source
The correct context is the query that should remain authoritative before any visitor filters are applied.
Use an archive context
Choose the discovered context when the search lives on a normal WordPress destination:
| Destination | Context type |
|---|---|
| Category, tag, or public taxonomy term | Taxonomy archive |
| Public post type archive | Post type archive |
| Year, month, or day archive | Date archive |
| Author page | Author archive |
| Shop or product taxonomy | WooCommerce |
| WordPress search results | Search |
| Posts page or site blog index | Blog home |
The current request resolves the archive context automatically. This is the best choice when the page URL already represents the collection.
Use a custom query
Choose Custom query when the collection is defined in Settings → POM Theme → Content model → Database queries and rendered with Listings (Feed).
In the listing:
- Set Query type to Custom query.
- Choose the saved query under Custom queries.
- Set Use with faceted search? to Yes.
The resulting ctx_query_… context can also be assigned under Apply to specific pages. Use that option only when those pages must always resolve to this custom context; an explicitly requested shortcode context is otherwise sufficient.
Avoid ambiguous ownership
Do not combine facets from different contexts around one result container. Their generated IDs may be valid independently, but they do not filter the same candidate set.
Do not choose a broad query and expect a facet to enforce permanent business rules. Put permanent restrictions—such as allowed post types or an editorial subset—in the archive or saved query. Use facets only for visitor-controlled refinement.
Verify the choice
Before adding filters, render the result list with Faceted Search enabled and no selections. Its initial items and total should match the intended base collection. If they do not, fix the query source first.
Next, map the actual fields with Connect facets to content fields.