'%20clip-path='url(%23canvas-clip)'/%3e%3cg%20clip-path='url(%23canvas-clip)'%3e%3cg%20transform='rotate(0,%20256,%20256)'%3e%3cg%20transform='translate(87%2087)%20scale(14.083333333333334%2014.083333333333334)%20translate(0%200)'%3e%3cpath%20fill='none'%20stroke='%23FFFFFF'%20stroke-linecap='round'%20stroke-linejoin='round'%20stroke-width='2'%20d='m18.064%2010.877l-4.89-7.26c-.42-.625-1.287-.803-1.936-.397a1.4%201.4%200%200%200-.41.397l-4.893%207.26C4.24%2013.715%204.9%2017.318%207.502%2019.423a7.13%207.13%200%200%200%204.168%201.572M15%2018a3%203%200%201%200%206%200a3%203%200%201%200-6%200m5.2%202.2L22%2022'/%3e%3c/g%3e%3c/g%3e%3c/g%3e%3c/svg%3e)
Ship a search change with evidence attached.
ParticleSearch keeps drafts, previews, live rules, runtime health, configuration sync, and protected queries visible so a merchant can tell what is ready to publish and what still needs review.
The publish contract
A draft becomes live only after the evidence agrees.
The workflow makes the difference between local convenience, verified preview, published configuration, and storefront runtime visible.
Draft
Change
Preview
Verify
Publish
Scope
Runtime
Sync
Golden
Protect
The merchant answer
Publishing should not be unlocked by opening a preview window. A safe release has a verified draft, a clear scope, a runtime that is reporting, and a way to confirm the important query still behaves after the change is live.
Guides and field notes
Go deeper when the decision needs detail.
Use these practical guides for the context, merchant decisions, and acceptance tests behind the capability you are evaluating.
Search QA guide
Learn how to judge a search answer, locate the failure, and release changes safely.
Golden queries guide
Protect important searches with expected products, positions, and recovery evidence.
Safe publishing guide
Separate draft, preview, live, runtime, observation, and rollback states.
Query tools guide
Inspect, preview, publish, and revisit a focused change.
Search monitoring guide
Keep runtime, freshness, and alerts in the operating loop.
The path
Keep the release state honest.
A merchant should be able to answer what changed, whether the preview was verified, what the storefront has loaded, and which important query would expose a regression.
Build a focused draft
Start from one query, filter, layout, or search behaviour and keep the intended outcome visible before changing live settings.
Verify before publish
Use the production-equivalent preview and compare the draft with the live result. Publishing stays unavailable while the draft is changing or verification has failed.
Confirm the runtime
After publish, check configuration sync, runtime health, active revision, and protected queries before treating the change as complete.
Decision guide
Questions this capability should answer
Use these questions to decide whether this capability is the right next move for your store.
Can I publish this draft yet?
Only when the intended change is stable, the production-equivalent preview is verified, and the publish guardrails are satisfied.
How do I know the storefront loaded the change?
Use the reported runtime state and configuration revision, not the fact that the dashboard saved successfully.
What happens when a live rule needs maintenance?
Rules remain auditable and link back to the relevant editor, where a merchant can edit, pause, activate, or remove the rule deliberately.
What is included
Controls for a reversible release
Publish safety is a merchant workflow, not a promise that every catalogue or storefront issue disappears automatically.
Live, draft, and compare states
Keep the production result, verified draft, and side-by-side comparison distinct so a local approximation cannot masquerade as live behaviour.
Protected golden queries
Record the products and positions that matter, replay the same protected manifest, and use input and output identity to make result changes inspectable before or after a publish.
Configuration reconciliation
Show whether the dashboard’s saved configuration and the storefront runtime agree, are pending, or still need confirmation.
Runtime health and preview expiry
Make the storefront health, preview link state, and expiry visible so a merchant knows which evidence is current.
Rules inventory and edit paths
Review active rules, filter the live inventory, and return to the owning editor when a rule needs to be changed or paused.
Experiments with explicit scope
Keep experiment variants, traffic, evidence, and deletion confirmation visible rather than treating an experiment as a permanent setting.
A useful boundary
Good product decisions include what the feature cannot solve.
ParticleSearch gives your team more evidence and control. It does not remove the need for accurate product data, a clear merchandising goal, or a review of the result on your own store.
- Publish safety cannot make bad product data, unavailable products, or incorrect market rules correct. It can stop a search rule from hiding the underlying problem.
- Golden queries are only as useful as the products, positions, context, and acceptance conditions the merchant records.
- Runtime confirmation proves configuration reconciliation, not a universal promise that every shopper query is now correct.
Keep exploring
See how this fits with the rest of the product.
See it on your store
Give your team a clearer way to improve search.
Install through Shopify, enable the app embed in your published theme, and run one proof check on your own storefront. Eligible Shopify installs · Shopify confirms trial eligibility before approval. Billing remains handled through Shopify.