Text version of this lessonExpand
This lesson fixes a common product-data problem: the title becomes a dumping ground for color, capacity, material, category, collection rules, promotion claims, and shipping promises. The better move is to separate title, attributes, Google product category, product_type, collection rules, and promotion fields.
What you should produce
By the end, you should have a title, attribute, and taxonomy decision table, which works as the field priority table for this lesson. It should show the title formula, required structured attributes, Google product category, product_type path, collection-rule field, responsible person or team, and QA locations.
This table is not a back-office note. It is a shared product-data asset for ads, SEO, on-site search, collection pages, Merchant Center, and Meta Catalog.
Separate the field jobs first
| Field | Job | Keep out | QA location |
|---|---|---|---|
| Title | Brand, product type, key spec, one core use case | Discounts, free shipping, every keyword | PDP, feed preview, search result |
| Attributes | Color, size, material, capacity, fit model | Only placing them in description or images | Shopify variants, category metafields, filters |
| Google product category | The closest official Google category | Internal shorthand or custom business path | Merchant Center category preview |
| product_type | Your internal path for budget, reporting, and review | Replacing the official Google category | Feed, product groups, internal reports |
| Collection rules | On-site navigation and buyer choice tasks | Depending on temporary title words | Collection page, site search, sorting rule |
Plain terms
Title is the first field buyers and platforms use to identify the product. For a 20oz stainless-steel commute cup, the title should clarify brand, type, capacity, material, and one core use case. It should not carry discounts, shipping promises, and every keyword.
Attributes are fields systems can read separately, such as color, capacity, material, and fit model. If those facts only appear in description copy, filters, feeds, product sets, and dynamic ads may miss them.
Google product category is the official category Google uses to understand the item. product_type is your own internal taxonomy path. They can be different, but one should not replace the other.
Category metafields are Shopify attribute fields mapped to the selected product category. After the Shopify product category is set, Shopify can suggest category-specific attributes such as color, size, fabric, or capacity. These fields can connect to variant options, swatches, filters, and channel-readable data.
Structured data is machine-readable product information on the page, often including name, price, availability, brand, reviews, and identifiers. It reads product facts and should not conflict with title, attributes, feed, or page promises. For example, if the title says 20oz while structured data or feed still exposes 32oz, search results and review signals can drift.
Category metafields: choose category before attributes
Small teams often create custom metafields first, then later discover that storefront variants, filters, feed fields, and ad product sets each have their own version. A safer order is: choose the Shopify product category, review suggested category metafields, connect attribute entries to variant options and swatches, then validate whether feeds and marketplaces can read the values.
| Situation | Right move | QA location |
|---|---|---|
| The product has no stable category | Choose Shopify product category before adding attributes | Shopify product page, category metafields |
| Color is both an attribute and a buying option | Connect category metafield entries to variant options | Variant admin, PDP options, feed color field |
| The storefront needs swatches | Use reusable color entries, not only visual theme blocks | PDP swatches, collection filters, mobile display |
| Platforms lack readable attributes | Move category-specific facts into fields instead of lengthening the title | Merchant Center, Meta Catalog, structured data |
Attribute gap triage: do not start by changing the title
Many title problems are really field-gap problems. Diagnose the symptom first, then decide whether to collect attributes at source, rewrite the title, fix taxonomy, or change collection rules.
| Symptom | Likely root | First evidence | Fix path |
|---|---|---|---|
| Title is long, but attributes are still missing | The title is replacing attribute collection | PDP title, Shopify attributes, Merchant Center preview, filters | Collect structured color, capacity, and material first; then rewrite the title formula |
| Variant can sell, but filters cannot find it | Variant option, category metafield, and feed field are disconnected | Shopify variants, Search & Discovery filters, Meta Catalog, Merchant Center fields | Connect attribute entries to variant options, then validate filters and channel previews |
| Google category and product_type are mixed | Platform category, internal taxonomy, and collection path are not separated | Feed fields, Merchant Center category preview, Google Ads product groups, internal reports | Use official Google category for platform understanding; keep product_type for business reporting |
| Collections depend on words in the title | Collection rules do not use stable attributes or product_type | Collection rules, site-search terms, title rewrite record, sorting logic | Move collection rules to stable fields; keep title focused on identification |
Category Metafield Builder Lab: choose the next move by product pressure
This section matches the interactive lab in the page. The point is not to memorize that Shopify has category metafields. The point is to decide, while entering real product data, whether the next move should be category, attribute, variant, swatch, or collection-rule work. If the order is wrong, the title may read better while feeds, filters, and product sets still cannot read the field.
Why this decision comes first: Shopify's standard product category controls which category metafields can appear. Those attributes can then connect to variant option values, PDP swatches, collection filters, and channel-readable fields. Google product category supports platform understanding; it should not replace your internal product_type path.
| Product pressure | Do not start with | Safer move | Decision-table line |
|---|---|---|---|
| 20oz insulated cup is still uncategorized | Creating a pile of custom metafields | Confirm Shopify product category first, then add capacity, material, and color category metafields | Category -> category metafields -> PDP/filter/feed preview |
| 20oz / 32oz can sell, but feed capacity is missing | Stuffing capacity into the title | Connect the capacity category metafield to variant option values | Capacity field -> variant option -> collection filter -> feed preview |
| Color swatches look good, but channel color drifts | Only fixing visual theme swatches | Use one standard color entry to drive variants, swatches, filters, and feed color | Color entry -> swatch -> filter -> channel color |
| Gift collection depends on title words | Putting gift back into the title for coverage | Move collection rules to a stable tag, product_type, or attribute | Collection-rule field -> SKU sample -> coverage QA |
| Google category is used as internal product_type | Changing Google product category to clean up reporting | Use Google product category for platform understanding and product_type for your business path | Platform category, internal path, and collection rules are validated separately |
How to do it in the admin: Confirm the product Category in Shopify first, using the closest standard category based on the product's main function. Then review the category metafields that appear. If color, size, or capacity is also a buying option, connect the relevant entry to variant options. Finally, sample the PDP, collection filters, Merchant Center preview, and Meta Catalog item.
Example: rewriting an insulated-cup product
In this insulated-cup example, the old title might be: "20oz insulated cup free shipping limited discount commute camping gift leakproof stainless steel." It looks rich, but color, capacity, material, use case, promotion, and collection logic are all mixed together.
After rewriting, the title can return to: "Brand + insulated cup + 20oz stainless steel + leak-resistant commute." Color, capacity, and material move into attributes. Discounts move into promotion fields. Shipping moves into fulfillment or shipping settings. Commute, gift, and summer collection rules should use stable tags, product_type, or attributes instead of title words.
Do not validate only by asking whether the title reads better. Sample at least five priority SKUs and compare PDP, Shopify fields, Merchant Center preview, Meta Catalog item, collection page, and site-search results.
Field Structure Pressure Lab: decide where the fact should live
Title optimization only works after fields have their own jobs. In real meetings, ads asks for more keywords, SEO asks for more scenario words, design fixes swatches first, merchandising pushes a new product live, and site ops wants collection coverage back. Decide whether the fact belongs in title, attribute, Google product category, product_type, variant option, swatch, or collection rule before the loudest request rewrites the title.
| Pressure scenario | Tempting wrong move | Safer read | First evidence | Blocked move |
|---|---|---|---|---|
| Ads wants more keywords in the title | Keep adding capacity, material, use-case, and discount words into title | Decide whether each word is identification, structured attribute, promo promise, or collection scenario; only identification belongs in title | Current title, Shopify attributes, category metafields, Merchant Center item preview, filters, and search terms | Do not add title words before the attribute gap is diagnosed |
| A new product must launch, but Shopify Category is still empty | Publish first, then use custom metafields for color, capacity, and material | Choose the closest Shopify product category by main function, review suggested category metafields, then connect attributes and variants | Shopify Category, suggested attributes, variant options, main product function, and Merchant Center category preview | Do not bulk-create custom fields or use Google product category as internal product_type when category is empty |
| Swatches look good, but feed and filter colors drift | Only fix theme color chips or feed rules | Use one standard color entry as the source, connect variant option, swatch, collection filter, and feed color, then sample QA | Color category metafield entry, variant option value, theme swatch, Search & Discovery filter, and feed color | Do not fix only UI or only feed before the color source is unified |
| Gift collection loses products, and the team wants gift back in title | Put scenario words back into every title to restore collection coverage | Move collection rules to stable tag, product_type, or attribute; keep title for identification | Collection rules, title change log, tag/product_type/attribute coverage, and SKU samples that dropped out | Do not pollute the title formula for coverage before collection rules move |
This is not another summary. It trains the field-location decision under pressure. When the field location is wrong, a harder-working title makes feeds, filters, product sets, and reports harder to explain.
Stop/Go: do not launch when title, attributes, and taxonomy blur together
| Signal | Action | QA location |
|---|---|---|
| Title is readable, attributes filter, taxonomy supports review | Go, move into sync and QA | PDP, feed preview, site-search results |
| Title carries discounts, shipping, or keyword stuffing | Hold, rewrite the title formula | Title formula sheet, priority SKU sample |
| Attributes only appear in description text | Hold, collect attributes at source | Shopify variants, category metafields, supplier file |
| Google category uses internal language | Hold, fix platform category | Merchant Center category preview |
| product_type cannot support budget or reporting | Hold, fix internal taxonomy path | Product groups, reporting dimensions, merchandising review |
Copyable lesson notes: title, attribute, and taxonomy decision table
Do not copy the vague note "title optimized." Copy notes another teammate can use to keep judging: the lesson conclusion, first evidence, blocked move, and next lesson bridge.
- Lesson conclusion: title, attributes, Google product category, product_type, and collection rules each have a job; title cannot carry every field.
- First evidence: current title, Shopify product category, category metafields, variant options, swatches, feed preview, and collection rules.
- Blocked move: do not add title words before attribute-gap triage; do not bulk-create custom fields when category is empty.
- Title formula: brand, product type, key spec, one core use case.
- Required attributes: color, size, material, capacity, fit model, and source location.
- Taxonomy split: job of Google product category, product_type, and collection rules.
- Responsible person and QA: who changes the field, where to validate it, and which sync cycle to wait for.
- Counter-signal: where a wrong decision will first show up, such as a page, feed, product set, or report.
- Next lesson bridge: after field structure is stable, move to Merchant Center feed quality and debugging.
The next lesson moves into Merchant Center feed quality and debugging. Carry forward a reviewable field decision table, not a vague optimization conclusion.
Public sources
These sources are not vocabulary homework. They confirm field boundaries. Google product data specification expects fields such as title, image, availability, GTIN, variant attributes, and google_product_category to be accurate, correctly formatted, and aligned with the landing page. google_product_category can override Google's automatic categorization when needed. product_type is your own categorization system and can support bidding, reporting, and product groups in Google Ads Shopping campaigns. Shopify category metafields explains that a standard category unlocks predefined category attributes and can connect them to variant options. Shopify Standard Product Taxonomy makes Shopify product category part of source-field governance, not a dropdown to skip.
| Boundary | Lesson use |
|---|---|
| Google product data spec expects accurate fields that match the landing page. | The title cannot carry color, capacity, material, variant, and taxonomy fields by itself. |
| google_product_category is Google's official category, not an internal menu. | Use it for platform understanding, not as product_type or collection path. |
| product_type is your own categorization system for bidding, reporting, and product groups. | It can fit business review, but it should not pretend to be Google official taxonomy. |
| Shopify standard category unlocks category metafields. | Choose product category before adding attributes, variant options, swatches, and filters. |
| Different categories need different important attributes. | Use category to decide what to collect instead of forcing every product into one generic field sheet. |