diff --git a/content/develop/clients/php/connect.md b/content/develop/clients/php/connect.md
index 0c3d361aef..19ac950b62 100644
--- a/content/develop/clients/php/connect.md
+++ b/content/develop/clients/php/connect.md
@@ -12,7 +12,7 @@ categories:
 description: Connect your PHP application to a Redis database
 linkTitle: Connect
 title: Connect to the server
-weight: 2
+weight: 10
 ---
 
 ## Basic connection
diff --git a/content/develop/clients/php/queryjson.md b/content/develop/clients/php/queryjson.md
index 2236274d12..ab4bc05812 100644
--- a/content/develop/clients/php/queryjson.md
+++ b/content/develop/clients/php/queryjson.md
@@ -12,7 +12,7 @@ categories:
 description: Learn how to use the Redis query engine with JSON
 linkTitle: Index and query JSON
 title: Example - Index and query JSON documents
-weight: 2
+weight: 20
 ---
 
 This example shows how to index and query Redis JSON data using `predis`.
diff --git a/content/develop/clients/php/vecsearch.md b/content/develop/clients/php/vecsearch.md
new file mode 100644
index 0000000000..531bc5e557
--- /dev/null
+++ b/content/develop/clients/php/vecsearch.md
@@ -0,0 +1,272 @@
+---
+categories:
+- docs
+- develop
+- stack
+- oss
+- rs
+- rc
+- oss
+- kubernetes
+- clients
+description: Learn how to index and query vector embeddings with Redis
+linkTitle: Index and query vectors
+title: Index and query vectors
+weight: 30
+---
+
+[Redis Query Engine]({{< relref "/develop/interact/search-and-query" >}})
+lets you index vector fields in [hash]({{< relref "/develop/data-types/hashes" >}})
+or [JSON]({{< relref "/develop/data-types/json" >}}) objects (see the
+[Vectors]({{< relref "/develop/interact/search-and-query/advanced-concepts/vectors" >}}) 
+reference page for more information).
+Among other things, vector fields can store *text embeddings*, which are AI-generated vector
+representations of the semantic information in pieces of text. The
+[vector distance]({{< relref "/develop/interact/search-and-query/advanced-concepts/vectors#distance-metrics" >}})
+between two embeddings indicates how similar they are semantically. By comparing the
+similarity of an embedding generated from some query text with embeddings stored in hash
+or JSON fields, Redis can retrieve documents that closely match the query in terms
+of their meaning.
+
+The example below uses the [HuggingFace](https://huggingface.co/) model
+[`all-MiniLM-L6-v2`](https://huggingface.co/sentence-transformers/all-MiniLM-L6-v2)
+to generate the vector embeddings to store and index with Redis Query Engine.
+
+## Initialize
+
+You can use the [TransformersPHP](https://transformers.codewithkyrian.com/)
+library to create the vector embeddings. Install the library with the following
+command:
+
+```bash
+composer require codewithkyrian/transformers
+```
+
+## Import dependencies
+
+Import the following classes and function in your source file:
+
+```php
+<?php
+
+require 'vendor/autoload.php';
+
+// TransformersPHP
+use function Codewithkyrian\Transformers\Pipelines\pipeline;
+
+// Redis client and query engine classes.
+use Predis\Client;
+use Predis\Command\Argument\Search\CreateArguments;
+use Predis\Command\Argument\Search\SearchArguments;
+use Predis\Command\Argument\Search\SchemaFields\TextField;
+use Predis\Command\Argument\Search\SchemaFields\TagField;
+use Predis\Command\Argument\Search\SchemaFields\VectorField;
+```
+
+## Create a tokenizer instance
+
+The code below shows how to use the
+[`all-MiniLM-L6-v2`](https://huggingface.co/sentence-transformers/all-MiniLM-L6-v2)
+tokenizer to generate the embeddings. The vectors that represent the
+embeddings have 384 dimensions, regardless of the length of the input
+text. Here, the `pipeline()` call creates the `$extractor` function that
+generates embeddings from text:
+
+```php
+$extractor = pipeline('embeddings', 'Xenova/all-MiniLM-L6-v2');
+```
+
+## Create the index
+
+Connect to Redis and delete any index previously created with the
+name `vector_idx`. (The
+[`ftdropindex()`]({{< relref "/commands/ft.dropindex" >}})
+call throws an exception if the index doesn't already exist, which is
+why you need the `try...catch` block.)
+
+```php
+ $client = new Predis\Client([
+    'host' => 'localhost',
+    'port' => 6379,
+]);
+
+try {
+    $client->ftdropindex("vector_idx");
+} catch (Exception $e){}
+```
+
+Next, create the index.
+The schema in the example below includes three fields: the text content to index, a
+[tag]({{< relref "/develop/interact/search-and-query/advanced-concepts/tags" >}})
+field to represent the "genre" of the text, and the embedding vector generated from
+the original text content. The `embedding` field specifies
+[HNSW]({{< relref "/develop/interact/search-and-query/advanced-concepts/vectors#hnsw-index" >}}) 
+indexing, the
+[L2]({{< relref "/develop/interact/search-and-query/advanced-concepts/vectors#distance-metrics" >}})
+vector distance metric, `Float32` values to represent the vector's components,
+and 384 dimensions, as required by the `all-MiniLM-L6-v2` embedding model.
+
+The `CreateArguments` parameter to [`ftcreate()`]({{< relref "/commands/ft.create" >}})
+specifies hash objects for storage and a prefix `doc:` that identifies the hash objects
+to index.
+
+```php
+$schema = [
+    new TextField("content"),
+    new TagField("genre"),
+    new VectorField(
+        "embedding",
+        "HNSW",
+        [
+            "TYPE", "FLOAT32",
+            "DIM", 384,
+            "DISTANCE_METRIC", "L2"
+        ]
+    )   
+];
+
+$client->ftcreate("vector_idx", $schema,
+    (new CreateArguments())
+        ->on('HASH')
+        ->prefix(["doc:"])
+);
+```
+
+## Add data
+
+You can now supply the data objects, which will be indexed automatically
+when you add them with [`hmset()`]({{< relref "/commands/hset" >}}), as long as
+you use the `doc:` prefix specified in the index definition.
+
+Use the `$extractor()` function as shown below to create the embedding that
+represents the `content` field. Note that `$extractor()` can generate multiple
+embeddings from multiple strings parameters at once, so it returns an array of
+embedding vectors. Here, there is only one embedding in the returned array.
+The `normalize:` and `pooling:` named parameters relate to details
+of the embedding model (see the
+[`all-MiniLM-L6-v2`](https://huggingface.co/sentence-transformers/all-MiniLM-L6-v2)
+page for more information).
+
+To add an embedding as a field of a hash object, you must encode the
+vector array as a binary string. The built-in
+[`pack()`](https://www.php.net/manual/en/function.pack.php) function is a convenient
+way to do this in PHP, using the `g*` format specifier to denote a packed
+array of `float` values. Note that if you are using
+[JSON]({{< relref "/develop/data-types/json" >}})
+objects to store your documents instead of hashes, then you should store
+the `float` array directly without first converting it to a binary
+string.
+
+```php
+$content = "That is a very happy person";
+$emb = $extractor($content, normalize: true, pooling: 'mean');
+
+$client->hmset("doc:0",[
+    "content" => $content,
+    "genre" => "persons",
+    "embedding" => pack('g*', ...$emb[0])
+]);
+
+$content = "That is a happy dog";
+$emb = $extractor($content, normalize: true, pooling: 'mean');
+
+$client->hmset("doc:1",[
+    "content" => $content,
+    "genre" => "pets",
+    "embedding" => pack('g*', ...$emb[0])
+]);
+
+$content = "Today is a sunny day";
+$emb = $extractor($content, normalize: true, pooling: 'mean');
+
+$client->hmset("doc:2",[
+    "content" => $content,
+    "genre" => "weather",
+    "embedding" => pack('g*', ...$emb[0])
+]);
+```
+
+## Run a query
+
+After you have created the index and added the data, you are ready to run a query.
+To do this, you must create another embedding vector from your chosen query
+text. Redis calculates the vector distance between the query vector and each
+embedding vector in the index as it runs the query. You can request the results to be
+sorted to rank them in order of ascending distance.
+
+The code below creates the query embedding using the `$extractor()` function, as with
+the indexing, and passes it as a parameter when the query executes (see
+[Vector search]({{< relref "/develop/interact/search-and-query/query/vector-search" >}})
+for more information about using query parameters with embeddings).
+The query is a
+[K nearest neighbors (KNN)]({{< relref "/develop/interact/search-and-query/advanced-concepts/vectors#knn-vector-search" >}})
+search that sorts the results in order of vector distance from the query vector.
+
+The results are returned as an array with the number of results in the
+first element. The remaining elements are alternating pairs with the
+key of the returned document (for example, `doc:0`) first, followed by an array containing
+the fields you requested (again as alternating key-value pairs).
+
+```php
+$queryText = "That is a happy person";
+$queryEmb = $extractor($queryText, normalize: true, pooling: 'mean');
+
+$result = $client->ftsearch(
+    "vector_idx",
+    '*=>[KNN 3 @embedding $vec AS vector_distance]',
+    new SearchArguments()
+        ->addReturn(1, "vector_distance")
+        ->dialect("2")
+        ->params([
+            "vec", pack('g*', ...$queryEmb[0])
+        ])
+        ->sortBy("vector_distance")
+);
+
+$numResults = $result[0];
+echo "Number of results: $numResults" . PHP_EOL;
+// >>> Number of results: 3
+
+for ($i = 1; $i < ($numResults * 2 + 1); $i += 2) {
+    $key = $result[$i];
+    echo "Key: $key" . PHP_EOL;
+    $fields = $result[$i + 1];
+    echo "Field: {$fields[0]}, Value: {$fields[1]}" . PHP_EOL; 
+}        
+// >>> Key: doc:0
+// >>> Field: vector_distance, Value: 3.76152896881
+// >>> Key: doc:1
+// >>> Field: vector_distance, Value: 18.6544265747
+// >>> Key: doc:2
+// >>> Field: vector_distance, Value: 44.6189727783
+```
+
+Assuming you have added the code from the steps above to your source file,
+it is now ready to run, but note that it may take a while to complete when
+you run it for the first time (which happens because the tokenizer must download the
+`all-MiniLM-L6-v2` model data before it can
+generate the embeddings). When you run the code, it outputs the following result text:
+
+```
+Number of results: 3
+Key: doc:0
+Field: vector_distance, Value: 3.76152896881
+Key: doc:1
+Field: vector_distance, Value: 18.6544265747
+Key: doc:2
+Field: vector_distance, Value: 44.6189727783
+```
+
+Note that the results are ordered according to the value of the `distance`
+field, with the lowest distance indicating the greatest similarity to the query.
+As you would expect, the text *"That is a very happy person"* (from the `doc:0`
+document)
+is the result judged to be most similar in meaning to the query text
+*"That is a happy person"*.
+
+## Learn more
+
+See
+[Vector search]({{< relref "/develop/interact/search-and-query/query/vector-search" >}})
+for more information about the indexing options, distance metrics, and query format
+for vectors.