Aglet

Verify a search boost across organic and promoted result paths

A ranking change is verified by the promises it makes in each context. Exercise queries that should receive the boost and queries that should not, then inspect order, labeling, filters, and return navigation. Confirm that a visible promotion does not masquerade as neutral relevance.

Check whether the outcome improved

  1. Test intended promotion

    Run the scoped query and confirm the promoted result appears where the policy expects, with the correct category or campaign context. Check that the result still supports the query and that selected sort does not silently contradict the visible control.

  2. Test an excluded query

    Use a neighboring phrase and a context outside the rule. Confirm that ordinary relevance remains understandable and that the boost does not leak into unrelated results. Record the first unexpected position and whether the interface gives a useful explanation.

  3. Check the user promise

    Review labels, sort names, facets, snippets, and back links around the changed order. Ensure the closure statement names tested rule scope and omitted query families. Keep a partial result open if intent and business policy still conflict.

What to carry forward

Verification passes when intended promotions are scoped, excluded queries retain understandable relevance, and labels match the ordering policy. If one context cannot be tested, report a bounded pass and preserve the unverified branch rather than treating a single ranked sample as universal proof.

Technical background: Elastic documentation.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow