Build a Search Gateway

Search Gateway is a compact GET form that collects canonical values from an existing Faceted Search context and sends the visitor to another URL.

It does not render or refresh results on its source page. Use it for a home-page search box, header search panel, or campaign landing page that leads to a full archive.

In Gutenberg, use the dynamic Search Gateway block. Both editors use the same GET form. Faceted Search and the selected context must be enabled; an unavailable context or destination produces no public form.

Prepare the destination

Build and verify the destination first:

1. Configure its Faceted Search context.
2. Add the destination facets and Listings (Feed).
3. Confirm the full results page accepts selections and creates pf_ parameters.

The gateway inherits facet IDs, canonical values, and include/exclude behavior from that context.

Add the gateway

1. Edit the source page in the Page Builder.
2. Add Search Gateway from Faceted Search.
3. Select Context.
4. Set Destination mode:
   • URL and enter Target URL; or
   • WordPress archive, then choose Post type archive, Taxonomy term archive, or Shop.
5. Under Facets, add and reorder the fields visitors should complete.
6. Save the page.

The target may be a relative path or an absolute HTTP(S) URL. For a taxonomy destination, choose the taxonomy and enter the term ID.

Configure each field

Each facet row can set:

• Facet;
• Renderer: inherit, select, radio, checkboxes, searchable select, autocomplete, or text;
• Label override and Placeholder override;
• Show label?;
• desktop, tablet landscape, tablet portrait, and mobile widths. Portrait inherits mobile unless explicitly set.

Only input-compatible facets are offered. A renderer override changes the compact form control, not the facet’s configured matching semantics.

The controls are native inputs, not the interactive facet widgets. Searchable-select configuration uses an ordinary multiple select, and autocomplete uses browser suggestions of canonical values. Text and suggestion controls submit one value; use checkboxes or multiple select for several values. Ranges have individually named From/To inputs; proximity uses latitude, longitude and radius. Choice lists are bounded to 500 values and custom fields to 100. A removed field does not cause a custom selection to inherit all context fields.

Configure submission

Use Show submit button? to display a styled button or allow submission with Enter. When the button is visible, set its text, style, size, icon, and responsive column widths.

Under Advanced, Preserve GET parameters accepts a comma-separated allowlist of unrelated parameters from the current page. Do not list pf_ facet parameters there; the gateway generates its canonical facet fields itself.

Destination query defaults take priority over preserved parameters. Their fragment is retained, and owned facet controls do not receive duplicate hidden defaults. Security-sensitive parameter names are not copied. Keep a visible submit button for select-only forms.

Verify the redirect

Submit each field alone and then a combination. Confirm:

• the browser navigates to the intended archive;
• the destination restores the selected facets;
• labels and responsive widths match the design;
• a hidden label still gives the field an accessible name;
• the gateway’s selection mode matches the destination context.