Rename the attributePosition rule into wordPosition

Kerollmops · Kerollmops · commit 89fa4287565b · 2026-02-23T10:34:21.000+01:00
diff --git a/.code-samples.meilisearch.yaml b/.code-samples.meilisearch.yaml
@@ -162,7 +162,7 @@ update_settings_1: |-
         "proximity",
         "attributeRank",
         "sort",
-        "attributePosition",
+        "wordPosition",
         "exactness",
         "release_date:desc",
         "rank:desc"
@@ -271,7 +271,7 @@ update_ranking_rules_1: |-
       "proximity",
       "attributeRank",
       "sort",
-      "attributePosition",
+      "wordPosition",
       "exactness",
       "release_date:asc",
       "rank:desc"
@@ -1063,7 +1063,7 @@ sorting_guide_update_ranking_rules_1: |-
       "typo",
       "proximity",
       "attributeRank",
-      "attributePosition",
+      "wordPosition",
       "exactness"
     ]'
 sorting_guide_sort_nested_1: |-
diff --git a/guides/relevancy/interpreting_ranking_scores.mdx b/guides/relevancy/interpreting_ranking_scores.mdx
@@ -96,7 +96,7 @@ Let's see how moving Sort **one position** in your ranking rules changes which r
 We’ve set up our ranking rules to have sort after our Group 1 wide net rules.
 
 ```json
-["words", "typo", "proximity", "sort", "attributeRank", "attributePosition", "exactness"]
+["words", "typo", "proximity", "sort", "attributeRank", "wordPosition", "exactness"]
 ```
 
 With this set up Meilisearch evaluates the text relevance rules first, *then* uses Sort.
@@ -196,7 +196,7 @@ Also notice: Sort shows a `value` instead of a `score`. That's because Sort does
 Now let's move `sort` to the top of our ranking rules:
 
 ```json
-["sort", "words", "typo", "proximity", "attributeRank", "attributePosition", "exactness"]
+["sort", "words", "typo", "proximity", "attributeRank", "wordPosition", "exactness"]
 ```
 
 ### 🥇 Result #1 — Chicken Stew with Curry Spices and Vegetables
diff --git a/guides/relevancy/ordering_ranking_rules.mdx b/guides/relevancy/ordering_ranking_rules.mdx
@@ -78,7 +78,7 @@ Ranking rules:
   "proximity",
   "attributeRank",
   "sort", // "price:asc" "author:desc" gets swapped in here
-  "attributePosition",
+  "wordPosition",
   "exactness",
   "release_date:asc",
   "movie_ranking:desc"
@@ -116,7 +116,7 @@ Place custom ranking rules at the end of your sequence. They work best for addin
 Each ranking rule has its own settings you can fine-tune beyond just ordering. For example, you can adjust which fields take priority in attribute ranking, or configure how aggressively typo tolerance matches similar words. If you want to dig into the specifics:
 
 - [Built-in ranking rules](https://www.meilisearch.com/docs/learn/relevancy/ranking_rules#list-of-built-in-ranking-rules) — how each rule works and what it evaluates
-- [Attribute ranking order](https://www.meilisearch.com/docs/learn/relevancy/attribute_ranking_order) — controlling which fields matter most with `attributeRank` and `attributePosition`
+- [Attribute ranking order](https://www.meilisearch.com/docs/learn/relevancy/attribute_ranking_order) — controlling which fields matter most with `attributeRank` and `wordPosition`
 - [Typo tolerance settings](https://www.meilisearch.com/docs/learn/relevancy/typo_tolerance_settings) — adjusting how flexible matching behaves
 
 **Want to see these rules in action?** In our next guide, [How Do I Interpret Ranking Score Details?](/guides/relevancy/interpreting_ranking_scores), we walk through a real example showing exactly how Meilisearch evaluates each rule — and how moving Sort one position can flip your results.
diff --git a/learn/filtering_and_sorting/sort_search_results.mdx b/learn/filtering_and_sorting/sort_search_results.mdx
@@ -85,7 +85,7 @@ This is the default configuration of Meilisearch's ranking rules:
   "proximity",
   "attributeRank",
   "sort",
-  "attributePosition",
+  "wordPosition",
   "exactness"
 ]
 ```
diff --git a/learn/relevancy/attribute_ranking_order.mdx b/learn/relevancy/attribute_ranking_order.mdx
@@ -38,7 +38,7 @@ By default, nested fields share the same weight as their parent attribute. Use d
 With the above ranking order, `review.critic` becomes more important than its sibling `review.user` when calculating a document's ranking score.
 
 <Note>
-The `attributeRank` and `attributePosition` rules' positions in [`rankingRules`](/learn/relevancy/ranking_rules) determine how the results are sorted. Meaning, **if `attributeRank` is at the bottom of the ranking rules list, it will have almost no impact on your search results.**
+The `attributeRank` and `wordPosition` rules' positions in [`rankingRules`](/learn/relevancy/ranking_rules) determine how the results are sorted. Meaning, **if `attributeRank` is at the bottom of the ranking rules list, it will have almost no impact on your search results.**
 
-The legacy `attribute` rule combines both `attributeRank` and `attributePosition`. If you use `attribute`, its position determines the impact of both attribute ranking order and position within attributes.
+The legacy `attribute` rule combines both `attributeRank` and `wordPosition`. If you use `attribute`, its position determines the impact of both attribute ranking order and position within attributes.
 </Note>
diff --git a/learn/relevancy/custom_ranking_rules.mdx b/learn/relevancy/custom_ranking_rules.mdx
@@ -53,7 +53,7 @@ The following array includes all built-in ranking rules and places the custom ru
   "proximity",
   "attributeRank",
   "sort",
-  "attributePosition",
+  "wordPosition",
   "exactness",
   "release_date:asc",
   "movie_ranking:desc"
diff --git a/learn/relevancy/ranking_rules.mdx b/learn/relevancy/ranking_rules.mdx
@@ -19,7 +19,7 @@ Meilisearch contains seven built-in ranking rules in the following order:
   "proximity",
   "attributeRank",
   "sort",
-  "attributePosition",
+  "wordPosition",
   "exactness"
 ]
 ```
@@ -62,13 +62,13 @@ This rule evaluates only the position of matched words within attributes and doe
 
 ## Attribute
 
-`attribute` is an older built-in ranking rule equivalent to using both `attributeRank` and `attributePosition` together. When you use `attribute`, Meilisearch first sorts results by the attribute ranking order, then uses the position within attributes as a tiebreaker.
+`attribute` is an older built-in ranking rule equivalent to using both `attributeRank` and `wordPosition` together. When you use `attribute`, Meilisearch first sorts results by the attribute ranking order, then uses the position within attributes as a tiebreaker.
 
 <Warning>
-You cannot use `attribute` together with `attributeRank` or `attributePosition`. If you try to configure ranking rules with both, Meilisearch will return an error. We recommend using a combination of the `attributeRank` and `attributePosition` rules.
+You cannot use `attribute` together with `attributeRank` or `wordPosition`. If you try to configure ranking rules with both, Meilisearch will return an error. We recommend using a combination of the `attributeRank` and `wordPosition` rules.
 </Warning>
 
-For most use-cases, we recommend using `attributeRank` and `attributePosition` separately. This gives you more control over result ordering by allowing you to place other ranking rules (like `sort` or custom ranking rules) between them.
+For most use-cases, we recommend using `attributeRank` and `wordPosition` separately. This gives you more control over result ordering by allowing you to place other ranking rules (like `sort` or custom ranking rules) between them.
 
 ## 6. Sort
 
diff --git a/learn/relevancy/ranking_score.mdx b/learn/relevancy/ranking_score.mdx
@@ -6,7 +6,7 @@ description: This article explains how the order of attributes in the `searchabl
 
 When using the [`showRankingScore` search parameter](/reference/api/search#ranking-score), Meilisearch adds a global ranking score field, `_rankingScore`, to each document. The `_rankingScore` is between `0.0` and `1.0`. The higher the ranking score, the more relevant the document.
 
-Ranking rules sort documents either by relevancy (`words`, `typo`, `proximity`, `exactness`, `attributeRank`, `attributePosition`) or by the value of a field (`sort`). Since `sort`  doesn't rank documents by relevancy, it does not influence the `_rankingScore`.
+Ranking rules sort documents either by relevancy (`words`, `typo`, `proximity`, `exactness`, `attributeRank`, `wordPosition`) or by the value of a field (`sort`). Since `sort`  doesn't rank documents by relevancy, it does not influence the `_rankingScore`.
 
 <Note>
 A document's ranking score does not change based on the scores of other documents in the same index.
@@ -19,7 +19,7 @@ The table below details all the index settings that can influence the `_rankingS
 | Index setting          | Influences if                                        | Rationale                                                                                                                                                                    |
 | :--------------------- | :--------------------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `searchableAttributes` | The `attributeRank` ranking rule is used             | The `attributeRank` ranking rule rates the document depending on the attribute in which the query terms show up. The order is determined by `searchableAttributes`          |
-| `searchableAttributes` | The `attributePosition` ranking rule is used         | The `attributePosition` ranking rule rates the document based on the position of query terms within attributes                                                               |
+| `searchableAttributes` | The `wordPosition` ranking rule is used         | The `wordPosition` ranking rule rates the document based on the position of query terms within attributes                                                               |
 | `rankingRules`         | Always                                               | The score is computed by computing the subscore of each ranking rule with a weight that depends on their order                                                               |
 | `stopWords`            | Always                                               | Stop words influence the `words` ranking rule, which is almost always used                                                                                                   |
 | `synonyms`             | Always                                               | Synonyms influence the `words` ranking rule, which is almost always used                                                                                                     |
diff --git a/learn/resources/telemetry.mdx b/learn/resources/telemetry.mdx
@@ -167,11 +167,11 @@ This list is liable to change with every new version of Meilisearch. It's not be
 | `ranking_rules.typo_position`                      | Position of the `typo` ranking rule if any, otherwise `null`                                | 2
 | `ranking_rules.proximity_position`                 | Position of the `proximity` ranking rule if any, otherwise `null`                           | 3
 | `ranking_rules.attribute_position`                 | Position of the `attribute` ranking rule if any, otherwise `null`                           | 4
-| `ranking_rules.attribute_rank_position`            | Position of the `attributeRank` ranking rule if any, otherwise `null`                       | 4
-| `ranking_rules.attribute_position_position`        | Position of the `attributePosition` ranking rule if any, otherwise `null`                   | 6
-| `ranking_rules.sort_position`                      | Position of the `sort` ranking rule                                                         | 5
-| `ranking_rules.exactness_position`                 | Position of the `exactness` ranking rule if any, otherwise `null`                           | 6
-| `ranking_rules.values`                             | A string representing the ranking rules without the custom asc-desc rules                   | "words, typo, attribute, sort, exactness"
+| `ranking_rules.attribute_rank_position`            | Position of the `attributeRank` ranking rule if any, otherwise `null`                       | 5
+| `ranking_rules.attribute_position_position`        | Position of the `wordPosition` ranking rule if any, otherwise `null`                        | 6
+| `ranking_rules.sort_position`                      | Position of the `sort` ranking rule                                                         | 7
+| `ranking_rules.exactness_position`                 | Position of the `exactness` ranking rule if any, otherwise `null`                           | 8
+| `ranking_rules.values`                             | A string representing the ranking rules without the custom asc-desc rules                   | "words, typo, attributeRank, sort, wordPosition, exactness"
 | `sortable_attributes.total`                        | Number of sortable attributes                                                               | 3
 | `sortable_attributes.has_geo`                      | `true` if `_geo` is set as a sortable attribute                                             | true
 | `filterable_attributes.total`                      | Number of filterable attributes                                                             | 3
diff --git a/reference/api/settings.mdx b/reference/api/settings.mdx
@@ -102,7 +102,7 @@ By default, the settings object looks like this. All fields are modifiable.
     "proximity",
     "attributeRank",
     "sort",
-    "attributePosition",
+    "wordPosition",
     "exactness"
   ],
   "stopWords": [],
@@ -239,7 +239,7 @@ If the provided index does not exist, it will be created.
 | **[`proximityPrecision`](#proximity-precision)**     | String           | `"byWord"`                                                                                       |  Precision level when calculating the proximity ranking rule                     |
 | **[`facetSearch`](#facet-search)**     | Boolean           | `true`                                                                                       |  Enable or disable [facet search](/reference/api/facet_search) functionality                     |
 | **[`prefixSearch`](#prefix-search)**     | String           | `"indexingTime"`                                                                                       | When Meilisearch should return results only matching the beginning of query                     |
-| **[`rankingRules`](#ranking-rules)**                 | Array of strings | `["words",`<br />`"typo",`<br />`"proximity",`<br />`"attributeRank",`<br />`"sort",`<br />`"attributePosition",`<br />`"exactness"]` | List of ranking rules in order of importance                                |
+| **[`rankingRules`](#ranking-rules)**                 | Array of strings | `["words",`<br />`"typo",`<br />`"proximity",`<br />`"attributeRank",`<br />`"sort",`<br />`"wordPosition",`<br />`"exactness"]` | List of ranking rules in order of importance                                |
 | **[`searchableAttributes`](#searchable-attributes)** | Array of strings | All attributes: `["*"]`                                                                          | Fields in which to search for matching query words sorted by order of importance |
 | **[`searchCutoffMs`](#search-cutoff)**              | Integer          | `null`, or 1500ms                                                                                | Maximum duration of a search query                                               |
 | **[`separatorTokens`](#separator-tokens)**           | Array of strings | Empty                                                                                            | List of characters delimiting where one term begins and ends                     |
@@ -1474,8 +1474,8 @@ Ranking rules are built-in rules that rank search results according to certain c
 | **`"typo"`**             | Sorts results by increasing number of typos                                     |
 | **`"proximity"`**        | Sorts results by increasing distance between matched query terms                |
 | **`"attributeRank"`**    | Sorts results by the attribute rank of the query terms within attributes        |
-| **`"attributePosition"`**| Sorts results by the position of query terms within attributes                  |
-| **`"attribute"`**        | Legacy rule combining `attributeRank` and `attributePosition`                   |
+| **`"wordPosition"`**| Sorts results by the position of query terms within attributes                  |
+| **`"attribute"`**        | Legacy rule combining `attributeRank` and `wordPosition`                   |
 | **`"sort"`**             | Sorts results based on parameters decided at query time                         |
 | **`"exactness"`**        | Sorts results based on the similarity of the matched words with the query words |
 
@@ -1488,7 +1488,7 @@ Ranking rules are built-in rules that rank search results according to certain c
   "proximity",
   "attributeRank",
   "sort",
-  "attributePosition",
+  "wordPosition",
   "exactness"
 ]
 ```
@@ -1518,7 +1518,7 @@ Get the ranking rules of an index.
   "proximity",
   "attributeRank",
   "sort",
-  "attributePosition",
+  "wordPosition",
   "exactness",
   "release_date:desc"
 ]
@@ -1554,7 +1554,7 @@ If some documents do not contain the attribute defined in a custom ranking rule,
 
 Make sure that any attribute used in a custom ranking rule is present in all of your documents. For example, if you set the custom ranking rule `desc(year)`, make sure that all your documents contain the attribute `year`.
 
-You cannot use the `attribute` ranking rule together with `attributeRank` or `attributePosition`. If you try to configure ranking rules with both, Meilisearch will return an error. We recommend using a combination of the `attributeRank` and `attributePosition` rules.
+You cannot use the `attribute` ranking rule together with `attributeRank` or `wordPosition`. If you try to configure ranking rules with both, Meilisearch will return an error. We recommend using a combination of the `attributeRank` and `wordPosition` rules.
 </Warning>
 
 [To learn more about ranking rules, refer to our dedicated guide.](/learn/relevancy/ranking_rules)

Original file line number	Diff line number	Diff line change
`@@ -85,7 +85,7 @@ This is the default configuration of Meilisearch's ranking rules:`
`85`	`85`	`"proximity",`
`86`	`86`	`"attributeRank",`
`87`	`87`	`"sort",`
`88`		`- "attributePosition",`
	`88`	`+ "wordPosition",`
`89`	`89`	`"exactness"`
`90`	`90`	`]`
`91`	`91`	```