> ## Documentation Index
> Fetch the complete documentation index at: https://product-discovery.developer.voyado.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Name and series

> Learn how the Name and Series attributes affect search ranking, autocomplete, and More from Series recommendations, with examples and best practices.

This guide explains how to use the **Name** and **Series** attributes effectively within search functionality in Voyado Elevate. Understanding their impact on ranking and search results will help optimize product visibility and ensure relevant search experiences.

## How name and series work

### Series

* Used only in **search results** and in the **More from Series** recommendation area.
* Helps group related products together, improving discoverability on product detail pages.
* Ranked **low** in primary search results, meaning matches in this field have little influence on ranking.

### Name

* Used in **search** and **autocomplete**.
* Critical for product identification and matching search intent.
* Ranked **high** in search results, making it a primary factor in determining product relevance.
* Can override and demote hits on other fields, such as **Title**, making careful usage essential to avoid unintended ranking shifts.

<Note>
  Both **Series** and **Name** are treated as known concepts in Elevate's search logic. When a visitor's query matches values in these fields, the corresponding products are placed in the primary list. As a result, matches in less authoritative fields, such as **Title**, are considered weaker signals and may be demoted to the secondary list.
</Note>

## Practical examples

### Example 1: using Series for stylistic grouping

A retailer selling *"Voyado Fit"* running shoes assigns several related models — such as trail, road, and lifestyle versions — to the same **Series**. These products share a unifying style or concept but are sold as distinct items rather than color or size variants. When a customer views one of the shoes, they see **More from Series** recommendations, helping them explore other items within the same style family. However, searching for "Voyado Fit" will **not** prioritize **Series** matches in the ranking if any stronger matches exist in higher-weighted fields like **Name**.

### Example 2: Name taking precedence over Title

A product named *"Voyado Fit Pro Max"* has the title *"Men's Running Shoe - Lightweight, Breathable"*. A visitor searching for "Pro Max" will likely see this product at the top because **Name** carries more ranking weight than **Title**. If another product only has "Pro Max" in its title but not in its **Name**, it may be pushed lower in results.

### Example 3: risk of Name overpowering other fields

If a generic term like *"Classic Sneakers"* is set as a **Name** across multiple products, searches for "classic sneakers" may **demote** more relevant results that have this term in the **Title**.

**Solution:** Use **Name** for **unique product identifiers**, not general descriptors.

## Best practices

* Use **Name** for distinct product identifiers (for example, *"Voyado Air Zoom X"*).
* Use **Series** for collections (for example, *"Voyado Air Zoom Series"*) to group related products.
* Avoid overly generic terms in **Name** to prevent unexpected ranking dominance.