Check whether the outcome improved
Check intended corrections
Run representative typos and compare suggested or corrected results with the expected product family. Confirm the interface explains a change when it changes text, and preserve the original phrase for editing or retrying.
Check valid near misses
Use an uncommon valid term, a brand phrase, a neighboring family, and a different locale. Confirm the correction does not redirect a legitimate query. Record result sets and not only whether the page has at least one row.
Review fallback behavior
Submit literal text, dismiss a suggestion, and open a direct link with the original spelling. Check labels, mobile wrapping, and no-result recovery. Limit the closure record to tested language and scope; leave an untested tokenizer path open.
What to carry forward
Verification passes when intended variants recover useful results, valid terms remain literal, and people can reject or edit a correction. If locale or brand coverage is partial, document that boundary. Do not call the policy safe based on one successful typo.
Technical background: GOV.UK developer 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