DEV: restructure indexing content

content/commands/ft.create.md

@@ -222,7 +222,7 @@ after the SCHEMA keyword, declares which fields to index:
 
  - `TEXT` - Allows full-text search queries against the value in this attribute.
 
- - `TAG` - Allows exact-match queries, such as categories or primary keys, against the value in this attribute. For more information, see [Tag Fields]({{< relref "/develop/ai/search-and-query/advanced-concepts/tags" >}}).
+ - `TAG` - Allows exact-match queries, such as categories or primary keys, against the value in this attribute. For more information, see [Tag Fields]({{< relref "/develop/ai/search-and-query/indexing/tags" >}}).
 
  - `NUMERIC` - Allows numeric range queries against the value in this attribute. See [query syntax docs]({{< relref "/develop/ai/search-and-query/query/" >}}) for details on how to use numeric ranges.
 

content/commands/ft.tagvals.md

@@ -62,7 +62,7 @@ Use FT.TAGVALS if your tag indexes things like cities, categories, and so on.
 
 ## Limitations
 
-FT.TAGVALS provides no paging or sorting, and the tags are not alphabetically sorted. FT.TAGVALS only operates on [tag fields]({{< relref "/develop/ai/search-and-query/advanced-concepts/tags" >}}).
+FT.TAGVALS provides no paging or sorting, and the tags are not alphabetically sorted. FT.TAGVALS only operates on [tag fields]({{< relref "/develop/ai/search-and-query/indexing/tags" >}}).
 The returned strings are lowercase with whitespaces removed, but otherwise unchanged.
 
 ## Return
@@ -87,5 +87,5 @@ FT.TAGVALS returns an array reply of all distinct tags in the tag index.
 
 ## Related topics
 
-- [Tag fields]({{< relref "/develop/ai/search-and-query/advanced-concepts/tags" >}})
+- [Tag fields]({{< relref "/develop/ai/search-and-query/indexing/tags" >}})
 - [RediSearch]({{< relref "/develop/ai/search-and-query/" >}})

content/develop/ai/search-and-query/advanced-concepts/query_syntax.md

@@ -64,7 +64,7 @@ You can use simple syntax for complex queries using these rules:
 * Georadius matches on geo fields with the syntax `@field:[{lon} {lat} {radius} {m|km|mi|ft}]`.
 * As of 2.6, range queries on vector fields with the syntax `@field:[VECTOR_RANGE {radius} $query_vec]`, where `query_vec` is given as a query parameter.
 * As of v2.4, k-nearest neighbors (KNN) queries on vector fields with or without pre-filtering with the syntax `{filter_query}=>[KNN {num} @field $query_vec]`.
-* Tag field filters with the syntax `@field:{tag | tag | ...}`. See the full documentation on [tags]({{< relref "/develop/ai/search-and-query/advanced-concepts/tags" >}}).
+* Tag field filters with the syntax `@field:{tag | tag | ...}`. See the full documentation on [tags]({{< relref "/develop/ai/search-and-query/indexing/tags" >}}).
 * Optional terms or clauses: `foo ~bar` means bar is optional but documents containing `bar` will rank higher.
 * Fuzzy matching on terms: `%hello%` means all terms with Levenshtein distance of 1 from it. Use multiple pairs of '%' brackets, up to three deep, to increase the Levenshtein distance.
 * An expression in a query can be wrapped in parentheses to disambiguate, for example, `(hello|hella) (world|werld)`.
@@ -128,8 +128,8 @@ If a field in the schema is defined as NUMERIC, it is possible to use the FILTER
 ## Tag filters
 
 As of v0.91, you can use a special field type called a
-[_tag field_]({{< relref "/develop/ai/search-and-query/advanced-concepts/tags" >}}), with simpler
-[tokenization]({{< relref "/develop/ai/search-and-query/advanced-concepts/escaping#tokenization-rules-for-tag-fields" >}})
+[_tag field_]({{< relref "/develop/ai/search-and-query/indexing/tags" >}}), with simpler
+[tokenization]({{< relref "/develop/ai/search-and-query/indexing/tokenization#tag-field-tokenization" >}})
 and encoding in the index. You can't access the values in these fields using a general fieldless search. Instead, you use special syntax:
 
 ```