> For the complete documentation index, see [llms.txt](https://seyarat.gitbook.io/seyarat-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://seyarat.gitbook.io/seyarat-docs/taxonomies.md). # Taxonomies Includes Listing taxonomies. 10 hierarchical taxonomies are registered: **Makes, Models, Categories, Features, Condition, Door, Color, Drive Type, Transmission, and Fuel Type.** Every listing taxonomy supports an image; Color also supports a HEX swatch. ### Taxonomy Fields A taxonomy is a classification and a term is one selectable value. Open **WordPress Admin** → **Listings** → **Makes** / **Models** / **Categories** / **Features** / **Condition** / **Door** / **Color** / **Drive Type** / **Transmission** / or **Fuel Type**.

Field	What to enter
Name	The visitor-facing term, for example Toyota.
Slug	The URL-safe form, for example `toyota`. Leave it empty to let WordPress generate it.
Parent	Select a broader term only when the classification truly needs a hierarchy.
Description	Optional explanatory text.
Image	Choose Select, pick or upload an appropriately licensed image, then confirm. Use Replace to choose another image or Remove to clear it.
Color swatch	Color only. Enter a six-digit HEX color such as `#ff7516`; the source default is `#ff7516`.

1. Open the taxonomy menu and check existing terms to avoid duplicates. 2. Enter Name; leave Slug blank unless a planned slug is required. 3. Choose Parent only for a deliberate hierarchy, then add Description, Image, and Color swatch when applicable. 4. Click Add New. For an existing term, open it, change only the intended fields, and click Update. 5. Create or edit a test listing, select the term, publish/preview it, then verify its card, single page, archive, and enabled search filter. {% hint style="info" %} The term appears in the taxonomy list and can be selected on a listing; its label, image, hierarchy, filter result, and optional swatch are correct. {% endhint %}

### Taxonomies #### Makes * The vehicle manufacturer or brand, such as Toyota, Ford, or BMW. #### Models * The vehicle model name, such as Corolla, Mustang, or X5; models are managed separately from makes. #### Categories * The vehicle body or market type, such as SUV, Sedan, Truck, or Coupe. #### Features * The equipment available on a vehicle, organized into parent groups such as Interior or Safety. #### Condition * The sale condition of the vehicle, such as New, Used, or Certified Pre-Owned. #### Door * The number of vehicle doors, with common values from 2 Doors to 5 Doors. #### Color * The vehicle exterior color, including a HEX swatch used for visual display. #### Drive Type * The drivetrain configuration, such as Front-Wheel Drive, Rear-Wheel Drive, or All-Wheel Drive. #### Transmission * The gearbox type, such as Automatic, Manual, Semi-Automatic, or Dual-Clutch. #### Fuel Type * The energy or fuel used by the vehicle, such as Petrol, Diesel, Electric, or Hybrid. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://seyarat.gitbook.io/seyarat-docs/taxonomies.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.