Skip to main content

Define the first useful search experience

For review — no decision recorded

Prepared 5 October 2026.

Decision requested​

Which conditions and example queries must the first search understand, and what should it ask when the meaning is ambiguous or the required facts are missing?

The broad search behavior is agreed. Concrete vocabulary, result eligibility and relevance examples are still needed to judge whether it works for readers.

Current agreement​

One query entry point covers Casinos, Offers, articles, providers, games and public reviews in separate result groups. Factual Casino and Offer matches must satisfy applicable filters from structured published facts. Articles and reviews can appear as topical reading without proving those facts.

Relevance comes before an applicable rating. A Casino star rating does not promote positive review text above negative text. Explicitly selected filters remain in force until the reader confirms a replacement.

The first direction supports English, German, French and Swedish with curated terms, aliases and bounded condition interpretation. Casino and Offer search uses one visible selected market; another market mentioned in a query prompts a change rather than silently switching it.

Proposal for discussion​

Agree a small initial set of useful conditions and a shared set of queries with expected factual and topical results. Show recognized conditions as editable filters. Use name suggestions while typing and interpret full conditions when the reader submits the query.

For ambiguous wording, agree the short clarification or choices shown to the reader. Unsupported wording must not silently become an unsupported fact filter. This keeps later conditions extensible without promising arbitrary interpretation of every sentence.

Illustrative result​

A query for "Apple Pay deposits up to EUR 20" could mean a minimum deposit no greater than EUR 20, or something else. The condition's meaning must be agreed. Once interpreted, the method, deposit direction, currency and minimum must match one supported condition. An article mentioning Apple Pay may appear in its own group; it does not prove that the related Casino meets the requirement.

If the reader already selected a different maximum, the query should propose replacing it and wait for confirmation.

Choices and tradeoffs​

  • Select the first conditions, exact meanings, synonyms and unsupported-query treatment. More vocabulary needs more checked examples.
  • Define public eligibility and references for games, providers, articles and reviews, along with which filters apply to each type.
  • Choose rating signals and tie handling without creating a common score across unrelated result types. Commercial placement policy remains a separate choice.
  • Define behavior when neither the requested language nor English has a published result. Showing a labelled English publication does not promise full translation.
  • Agree a corpus and measurement scenario for the response targets: at most 100 ms at the 95th percentile for the search API, and at most 300 ms for visible results in the agreed dev scenario. These are goals, not measurements. Update and withdrawal visibility also need agreed acceptance; no numeric freshness promise is selected.

Response requested​

Provide representative queries with the intended conditions and result groups, at least one ambiguous query and the expected clarification. Identify the first market and language cases, then agree how relevance and update visibility will be checked. Read Search and markets and languages for the existing reader behavior.

Recorded outcome​

No decision recorded. This brief does not authorize implementation or change delivery timing. Share the specific page and version through the existing discussion channel. Respond with accept, requested changes or defer, identifying the question concerned. How to review explains how an actual agreement is recorded and reflected in the product documents.