Reference product recordKverneland AC820825 Fan Impeller
Supplier AKoło wentylatora AC820825
Supplier BRueda del ventilador AC820825
Legacy catalogКрыльчатка вентилятора AC820825
Product familyOutput studioNaming composerone record → controlled naming
Product titles & metadata
Standardize Product Titles and Search Metadata at Scale
Product naming becomes messy when every supplier and employee follows a different convention.
The metadata package is generated from the same validated technical record and SEO search context: product title, meta title, meta description and the keyword set used to guide the page content.
ENRIVAQ generates product titles and search metadata from structured product data and category-specific rules. The objective is consistent naming while keeping each product identifiable and useful to buyers.
Titles should communicate what the product is. Metadata should explain why the page is relevant. Neither should depend on improvised wording.
Rulecategory-defined
field order
field order
BrandProduct typeIdentifierKey property
Catalog titleKverneland AC820825 Fan Impeller for Optima Planters
Built from category rules and verified fields.
SEO titleKverneland AC820825 Fan Impeller | Optima Planter Part
Same record, prioritized for search context.
02
Naming problems
Inconsistent product names create problems beyond appearance
A supplier title is built for the supplier’s system. Another source may order the same information differently or omit the product type. When those formats enter one catalog unchanged, recognition and entity signals become weaker.
Supplier AKoło wentylatora AC820825
Supplier BRueda del ventilador AC820825
Legacy catalogКрыльчатка вентилятора AC820825
Typical defectField order, terminology or product type differs
converge→
Consistent entity naming
One recognizable structure within a product family.
Category-specific key field
The business decides which verified property matters.
Buyer-readable output
Not supplier shorthand copied unchanged.
03
Title formula
Use category rules instead of random AI wording
A title can follow a visible structure, but the exact order and included fields must be defined by the catalog and the way buyers recognize that product family.
Kverneland
Fan impeller
AC820825
Optima / Optima HD
For one category, a dimension may be essential. For another, an OEM number or connection type may matter more. The formula must reflect the product, not a universal template.
04
SEO titles
Product title and SEO title do not have to be identical
The on-page title serves the buyer and catalog. The SEO title communicates the page clearly in a search result. Both derive from the same verified product record.
Kverneland AC820825 Fan Impeller for Optima Planters
Prioritizes catalog consistency, product recognition and the approved naming order.
Kverneland AC820825 Fan Impeller | Optima Planter Part
Uses the same facts while prioritizing page meaning for the search-result context.
05
Metadata
Use the meta description to summarize the real product
A useful meta description should tell a searcher what is on the page, not repeat a generic marketing promise.
06
Examples
Show how different source titles converge on one controlled product record
The reference rows below use public naming variants for AC820825 and show the same controlled catalog/SEO output.
Example 01Koło wentylatora AC820825Kverneland AC820825 Fan Impeller for Optima PlantersKverneland AC820825 Fan Impeller | Optima Planter PartFan impeller AC820825 for Kverneland Optima and Optima HD precision planters.
Example 02Rueda del ventilador AC820825Kverneland AC820825 Fan Impeller for Optima PlantersKverneland AC820825 Fan Impeller | Optima Planter PartOEM reference AC820825 with verified product identity and Optima-family compatibility.
Example 03Крыльчатка вентилятора AC820825Kverneland AC820825 Fan Impeller for Optima PlantersKverneland AC820825 Fan Impeller | Optima Planter PartStructured product content generated from accepted AC820825 facts; unresolved values remain excluded.
07 · Editorial checkpoint
Rule gate
Consistency matters more than creative variation
Automated title and metadata generation should operate within clear editorial rules. Exact limits belong to the real catalog policy and are not invented here.
Configured length rulesProject/category content policyCheck
Duplicate title detectionCatalog comparisonCheck
Required identifiersCategory naming ruleCheck
Unsupported technical claimsValidated recordExclude
Keyword-only stuffingEditorial reviewExclude
Visible page consistencyPublished page fieldsCheck
Naming Composer
Standardize a real set of product titles
Provide several titles from the same product family or supplier feed. See how a structured naming rule can make the catalog more consistent.