diff --git a/docs-site/content/27.0/api/search.md b/docs-site/content/27.0/api/search.md
index 69b51766..03bb6ec2 100644
--- a/docs-site/content/27.0/api/search.md
+++ b/docs-site/content/27.0/api/search.md
@@ -716,7 +716,7 @@ Let's create a preset with name `listing_view`.
 ```js
   await client.presets().upsert("listing_view", {
     value: {
-      searches: [{ collection: "products", q: "*", sort_by: "popularity" }],
+      collection: "products", q: "*", sort_by: "popularity",
     },
   });
 ```
@@ -727,9 +727,7 @@ Let's create a preset with name `listing_view`.
 ```dart
   await client.presets.upsert('listing_view', {
     'value': {
-      'searches': [
-        {'collection': 'products', 'q': '*','sort_by': 'popularity'}
-      ]
+      'collection': 'products', 'q': '*','sort_by': 'popularity'
     }
   });
 ```
@@ -741,11 +739,10 @@ Let's create a preset with name `listing_view`.
 curl "http://localhost:8108/presets/listing_view" -X PUT \
 -H "Content-Type: application/json" \
 -H "X-TYPESENSE-API-KEY: ${TYPESENSE_API_KEY}" \
--d '{"value": {"searches":[{"collection":"products","q":"*", "sort_by": "popularity"}]}}'
+-d '{"value": {"collection":"products","q":"*", "sort_by": "popularity"}}'
 ```
   </template>
 </Tabs>
-
 You can refer to this preset configuration during a search operation.
 
 <Tabs :tabs="['JavaScript','Dart','Shell']">
@@ -776,37 +773,30 @@ curl -H "X-TYPESENSE-API-KEY: ${TYPESENSE_API_KEY}"  -X POST \
   </template>
 </Tabs>
 
-You can use the preset configuration for a `GET .../search` end-point as well. 
-
-The only requirement is that for 
-`GET .../search`, the stored preset value should be a simple dictionary of search configurations, like this.
-
-<Tabs :tabs="['Dart','Shell']">
-  <template v-slot:Dart>
+:::tip
+The `value` key in the preset configuration can also match the search parameters for <RouterLink :to="`/${$site.themeConfig.typesenseLatestVersion}/api/federated-multi-search.html`">Federated / Multi Search</RouterLink>. For example:
 
-```dart
-  await client.presets.upsert('listing_view', {
-    'value': {
-      {
-        'collection': 'products',
-        'q': '*',
-        'sort_by': 'popularity',
-      }
-    }
-  });
+```js
+  await client.presets().upsert("listing_view", {
+    value: {
+      searches: [
+        {
+          collection: "products",
+          q: "*",
+          sort_by: "popularity",
+        },
+        {
+          collection: "blog_posts",
+          q: "*",
+          sort_by: "published_at:desc",
+        }
+      ],
+    },
+  })
 ```
+:::
 
-  </template>
-  <template v-slot:Shell>
-
-```shell
-curl "http://localhost:8108/presets/listing_view" -X PUT \
--H "Content-Type: application/json" \
--H "X-TYPESENSE-API-KEY: ${TYPESENSE_API_KEY}" -d '
-{"value": {"collection":"products","q":"*", "sort_by": "popularity"}}'
-```
-  </template>
-</Tabs>
+It's generally recommended to use single-search presets for flexibility. You can then combine them in a multi-search request using the `preset` parameter.
 
 :::tip
 Explicit query parameters passed to the search end-point will override parameters stored in preset value.
diff --git a/docs-site/content/27.1/api/search.md b/docs-site/content/27.1/api/search.md
index 98d10cbd..3b6c42f9 100644
--- a/docs-site/content/27.1/api/search.md
+++ b/docs-site/content/27.1/api/search.md
@@ -756,7 +756,7 @@ Let's create a preset with name `listing_view`.
 ```js
   await client.presets().upsert("listing_view", {
     value: {
-      searches: [{ collection: "products", q: "*", sort_by: "popularity" }],
+      collection: "products", q: "*", sort_by: "popularity",
     },
   });
 ```
@@ -767,9 +767,7 @@ Let's create a preset with name `listing_view`.
 ```dart
   await client.presets.upsert('listing_view', {
     'value': {
-      'searches': [
-        {'collection': 'products', 'q': '*','sort_by': 'popularity'}
-      ]
+      'collection': 'products', 'q': '*','sort_by': 'popularity'
     }
   });
 ```
@@ -799,7 +797,7 @@ client.Presets().Upsert(context.Background(), "listing-view", preset)
 curl "http://localhost:8108/presets/listing_view" -X PUT \
 -H "Content-Type: application/json" \
 -H "X-TYPESENSE-API-KEY: ${TYPESENSE_API_KEY}" \
--d '{"value": {"searches":[{"collection":"products","q":"*", "sort_by": "popularity"}]}}'
+-d '{"value": {"collection":"products","q":"*", "sort_by": "popularity"}}'
 ```
   </template>
 </Tabs>
@@ -846,51 +844,31 @@ curl -H "X-TYPESENSE-API-KEY: ${TYPESENSE_API_KEY}"  -X POST \
   </template>
 </Tabs>
 
-You can use the preset configuration for a `GET .../search` end-point as well.
-
-The only requirement is that for
-`GET .../search`, the stored preset value should be a simple dictionary of search configurations, like this.
-
-<Tabs :tabs="['Dart','Go','Shell']">
-  <template v-slot:Dart>
-
-```dart
-  await client.presets.upsert('listing_view', {
-    'value': {
-      {
-        'collection': 'products',
-        'q': '*',
-        'sort_by': 'popularity',
-      }
-    }
-  });
-```
-
-  </template>
-  <template v-slot:Go>
-
-```go
-preset := &api.PresetUpsertSchema{}
-preset.Value.FromSearchParameters(api.SearchParameters{
-  Q:      pointer.String("*"),
-  SortBy: pointer.String("popularity"),
-})
+:::tip
+The `value` key in the preset configuration can also match the search parameters for <RouterLink :to="`/${$site.themeConfig.typesenseLatestVersion}/api/federated-multi-search.html`">Federated / Multi Search</RouterLink>. For example:
 
-client.Presets().Upsert(context.Background(), "listing-view", preset)
+```js
+  await client.presets().upsert("listing_view", {
+    value: {
+      searches: [
+        {
+          collection: "products",
+          q: "*",
+          sort_by: "popularity",
+        },
+        {
+          collection: "blog_posts",
+          q: "*",
+          sort_by: "published_at:desc",
+        }
+      ],
+    },
+  })
 ```
+:::
 
-  </template>
-  <template v-slot:Shell>
-
-```shell
-curl "http://localhost:8108/presets/listing_view" -X PUT \
--H "Content-Type: application/json" \
--H "X-TYPESENSE-API-KEY: ${TYPESENSE_API_KEY}" -d '
-{"value": {"collection":"products","q":"*", "sort_by": "popularity"}}'
-```
-  </template>
-</Tabs>
+It's generally recommended to use single-search presets for flexibility. You can then combine them in a multi-search request using the `preset` parameter.
 
 :::tip
 Explicit query parameters passed to the search end-point will override parameters stored in preset value.
-:::
+:::
\ No newline at end of file
diff --git a/docs-site/content/28.0/api/search.md b/docs-site/content/28.0/api/search.md
index 72dc1835..5a997fed 100644
--- a/docs-site/content/28.0/api/search.md
+++ b/docs-site/content/28.0/api/search.md
@@ -965,7 +965,7 @@ Let's create a preset with name `listing_view`.
 ```js
   await client.presets().upsert("listing_view", {
     value: {
-      searches: [{ collection: "products", q: "*", sort_by: "popularity" }],
+      collection: "products", q: "*", sort_by: "popularity",
     },
   });
 ```
@@ -976,9 +976,7 @@ Let's create a preset with name `listing_view`.
 ```dart
   await client.presets.upsert('listing_view', {
     'value': {
-      'searches': [
-        {'collection': 'products', 'q': '*','sort_by': 'popularity'}
-      ]
+      'collection': 'products', 'q': '*','sort_by': 'popularity'
     }
   });
 ```
@@ -1006,100 +1004,180 @@ client.Presets().Upsert(context.Background(), "listing-view", preset)
 
 ```shell
 curl "http://localhost:8108/presets/listing_view" -X PUT \
--H "Content-Type: application/json" \
--H "X-TYPESENSE-API-KEY: ${TYPESENSE_API_KEY}" \
--d '{"value": {"searches":[{"collection":"products","q":"*", "sort_by": "popularity"}]}}'
+    -H "Content-Type: application/json" \
+    -H "X-TYPESENSE-API-KEY: ${TYPESENSE_API_KEY}" \
+    -d '{
+          "value": {
+            "collection": "products",
+            "q": "*",
+            "sort_by": "popularity"
+          }
+        }'
 ```
   </template>
 </Tabs>
 
-You can refer to this preset configuration during a search operation.
+You can refer to this preset configuration during a search operation using the `preset` search parameter.
 
-<Tabs :tabs="['JavaScript','Dart','Go','Shell']">
+The following shows the [`multi_search`](./federated-multi-search.md) endpoint, but you can also use the `preset` search parameter with the single search endpoint as well.
+
+<Tabs :tabs="['JavaScript','PHP','Python','Ruby','Dart','Java','Go','Shell']">
   <template v-slot:JavaScript>
 
 ```js
-await client.multiSearch().perform({},{
-  preset: 'listing_view'
-});
+let searchRequests = {
+  'searches': [
+    {
+      'preset': 'listing_view'
+    }
+  ]
+}
+
+client.multiSearch.perform(searchRequests, {})
 ```
 
   </template>
-  <template v-slot:Dart>
 
-```dart
-await client.multiSearch.perform({}, queryParams: {
-  'preset': 'listing_view'
-});
-```
+  <template v-slot:PHP>
 
-  </template>
-  <template v-slot:Go>
+```php
+$searchRequests = [
+  'searches' => [
+    [
+      'preset' => 'listing_view'
+    ]
+  ]
+];
 
-```go
-client.MultiSearch.Perform(context.Background(),
-  &api.MultiSearchParams{
-    Preset: pointer.String("listing_view"),
-  },
-  api.MultiSearchSearchesParameter{},
-)
+$client->multiSearch->perform($searchRequests, []);
 ```
 
   </template>
-  <template v-slot:Shell>
+  <template v-slot:Python>
 
-```shell
-curl -H "X-TYPESENSE-API-KEY: ${TYPESENSE_API_KEY}"  -X POST \
-'http://localhost:8108/multi_search?preset=listing_view'
+```py
+search_requests = {
+  'searches': [
+    {
+      'preset': 'listing_view'
+    }
+  ]
+}
+
+client.multi_search.perform(search_requests, {})
 ```
+
   </template>
-</Tabs>
+  <template v-slot:Ruby>
 
-You can use the preset configuration for a `GET .../search` end-point as well.
+```rb
+search_requests = {
+  'searches': [
+    {
+      'preset': 'listing_view'
+    }
+  ]
+}
 
-The only requirement is that for
-`GET .../search`, the stored preset value should be a simple dictionary of search configurations, like this.
+client.multi_search.perform(search_requests, {})
+```
 
-<Tabs :tabs="['Dart','Go','Shell']">
+  </template>
   <template v-slot:Dart>
 
 ```dart
-  await client.presets.upsert('listing_view', {
-    'value': {
-      {
-        'collection': 'products',
-        'q': '*',
-        'sort_by': 'popularity',
-      }
+final searchRequests = {
+  'searches': [
+    {
+      'preset': 'listing_view'
     }
-  });
+  ]
+};
+
+await client.multiSearch.perform(searchRequests, queryParams: {});
+```
+
+  </template>
+  <template v-slot:Java>
+
+```java
+HashMap<String,String > search1 = new HashMap<>();
+
+search1.put("preset","listing_view");
+
+List<HashMap<String, String>> searches = new ArrayList<>();
+searches.add(search1);
+
+HashMap<String, List<HashMap<String ,String>>> searchRequests = new HashMap<>();
+searchRequests.put("searches",searches);
+
+HashMap<String,String> commonSearchParams = new HashMap<>();
+
+client.multiSearch.perform(searchRequests, commonSearchParams);
 ```
 
   </template>
   <template v-slot:Go>
 
 ```go
-preset := &api.PresetUpsertSchema{}
-preset.Value.FromSearchParameters(api.SearchParameters{
-  Q:      pointer.String("*"),
-  SortBy: pointer.String("popularity"),
-})
+searchRequests := api.MultiSearchSearchesParameter{
+  Searches: []api.MultiSearchCollectionParameters{
+    {
+      Preset: "listing_view"
+    },
+  },
+}
 
-client.Presets().Upsert(context.Background(), "listing-view", preset)
+commonSearchParams := &api.MultiSearchParams{}
+
+client.MultiSearch.Perform(context.Background(), commonSearchParams, searchRequests)
 ```
 
   </template>
   <template v-slot:Shell>
 
-```shell
-curl "http://localhost:8108/presets/listing_view" -X PUT \
--H "Content-Type: application/json" \
--H "X-TYPESENSE-API-KEY: ${TYPESENSE_API_KEY}" -d '
-{"value": {"collection":"products","q":"*", "sort_by": "popularity"}}'
+```bash
+curl "http://localhost:8108/multi_search" \
+        -X POST \
+        -H "Content-Type: application/json" \
+        -H "X-TYPESENSE-API-KEY: ${TYPESENSE_API_KEY}" \
+        -d '{
+          "searches": [
+            {
+              "preset": "listing_view"
+            }
+          ]
+        }'
 ```
+
   </template>
 </Tabs>
 
 :::tip
-Explicit query parameters passed to the search end-point will override parameters stored in preset value.
+The `value` key in the preset configuration can also match the search parameters for <RouterLink :to="`/${$site.themeConfig.typesenseLatestVersion}/api/federated-multi-search.html`">Federated / Multi Search</RouterLink>. For example:
+
+```js
+  await client.presets().upsert("listing_view", {
+    value: {
+      searches: [
+        {
+          collection: "products",
+          q: "*",
+          sort_by: "popularity",
+        },
+        {
+          collection: "blog_posts",
+          q: "*",
+          sort_by: "published_at:desc",
+        }
+      ],
+    },
+  })
+```
 :::
+
+It's generally recommended to use single-search presets for flexibility. You can then combine them in a multi-search request using the `preset` parameter.
+
+:::tip
+Explicit query parameters passed to the search end-point will override parameters stored in preset value.
+:::
\ No newline at end of file