Feed rules that fix titles without touching the catalog

The product name in your catalog was written for a shopper who is already on the page. The title in your feed is read by a system matching it against a query. Those are different jobs, and you do not need to change the first to fix the second. Merchant Center’s attribute rules and supplemental feeds rewrite attributes after the store exports them and before Google reads them. The storefront stays exactly as it is, and every change can be switched off in minutes.

What a rule can do, and where it stops

Rules transform data you already submit. They cannot create information that exists nowhere. Within that limit they handle most title work:

• Set an attribute to static text, to another attribute, or to several attributes joined together.
• Prepend or append text to an existing value.
• Take a value found in another attribute, such as a colour word inside the description, and write it into the attribute where it belongs.
• Apply any of the above only when a condition is true, for example when product_type contains a given string.

What they will not do is fix wrong source data. If the size field says “M” for a product that is actually large, a rule will faithfully put “M” in the title. Rules are a formatting layer, and they are only as good as the fields feeding them.

Three layers, cheapest first

Layer	What it is	Reach for it when
Attribute rules	Transformations configured inside Merchant Center on a data source	The values you need are already in the feed and you want no files to maintain
Supplemental feed	A sheet or file keyed on product ID that overrides or adds attributes	You have data outside the platform, such as a colour column from the supplier, or want a human-readable override list
Feed app or platform plugin	Software that builds the feed from the catalog with its own rule engine	You need the same output for Google, Meta and marketplaces, or per-variant logic the native rules cannot express

Most stores can get titles right with the first two. The supplemental feeds we build are usually a single sheet with an ID column and three or four attribute columns, refreshed on a schedule. A supplemental feed never replaces the primary feed, so an empty row leaves the original value in place.

The title recipe

1. List what you already submit. Open the data source and note which of brand, product_type, color, size, material, gender, age_group and pattern carry values for most products. The title can only be built from these.
2. Pick an order for each product type. Apparel wants brand, gender, type, attribute, colour and size. Hardware wants brand, type, model number and the spec a buyer filters on. Consumables want brand, product, variant and pack size. Write the order down before touching the tool.
3. Build the rule. Set title to the attributes in that order, separated by spaces or commas, with a condition on product_type so each category gets its own recipe. Where a value might be empty, order the pieces so a gap at the end does no harm.
4. Guard the length. The limit is 150 characters, and far fewer show in most placements. Put the query-matching words first and the variant details last, so truncation costs you the least.
5. Preview, then apply. The rule editor shows sample products before and after. Read twenty of them, not two.

If you want the recipe worked out for your categories first, the product feed title builder produces a pattern you can paste into the rule.

Filling attributes you never submitted

The most common gap is colour. The platform stores it as a variant option named “Colour” or “Shade”, the export puts it in the variant title or nowhere, and the color attribute arrives empty. Two fixes:

• If the colour is inside another submitted field, a rule can pull it out into color. Then the title rule uses color like any other attribute.
• If the colour is nowhere in the feed, a supplemental sheet with ID and colour columns adds it. A supplier price list or a quick export of variant options is usually the source.

The same pattern fills material, size and gender. Once the attribute exists, it improves matching on its own, and it becomes available to every title rule. Check item_group_id at the same time, because a title that now varies by colour only helps if Google knows the variants belong together. The item group ID entry covers what happens when it is missing.

Different recipes for different parts of the catalog

One title rule across a mixed catalog produces good apparel titles and odd everything else. Condition each rule on the field that separates the categories. product_type is the natural choice because it is your own taxonomy, and it is worth cleaning up for that reason alone. The product type attribute is also a matching signal, so consistent values pay twice. Where product_type is unreliable, condition on google_product_category or on a custom label you control.

Typical splits we end up with on a general store:

• Sized and coloured goods: brand, gender, type, key attribute, colour, size.
• Specified goods such as tools, electronics and parts: brand, type, model, spec, compatibility.
• Consumables: brand, product, flavour or scent, count or volume, pack size.
• Furniture and home: brand, type, material, dimensions, colour.

Testing before the rule goes live

The preview is the first check, not the last. After applying:

1. Open Diagnostics the next day and look for new item-level issues. Titles over the limit, capitalized words the policy dislikes, and values that no longer match the landing page show up here.
2. Open ten products in the Products tab and compare the new title to the product page. Every word in the feed title should be visible on the page or in its options.
3. Check that variants of one item group have titles that differ only by variant attributes.
4. Keep the previous rule version. Merchant Center lets you disable a rule; disabling is your rollback.

The Merchant Center diagnostics process we run after any feed change is exactly this, on a checklist.

Keeping the feed title honest against the page

Google’s title guidance asks the feed title to accurately describe the product on the landing page. Adding attributes the page already shows, such as colour, size or material, stays well within that. Adding promotional words, claims, capitals for emphasis, or renaming the product into something the page does not call it does not. Merchant Center also offers automatic improvements that can rewrite titles on Google’s side. Decide whether you want your rules or Google’s edits on top of them; running both makes results hard to read.

Rolling out and reading the effect

Apply the rule to one category first. Titles carry history, and a wholesale rewrite of the catalog on a Tuesday resets more than you want in one go. Give a category two to three weeks, then read impressions, clicks and the search terms or search categories the products now show for. A clean roll-out shows new query matches appearing for the attributes you added. Then move to the next category with whatever the first one taught you. What a title should contain in the first place is covered in what makes a good product title for Google Shopping.

When the catalog should change after all

Rules are the right first move, and sometimes the wrong last one. Change the source when:

• The page title is also weak for organic search, so the same fix helps two channels.
• The data is missing everywhere and a supplemental sheet would become a second catalog to maintain.
• Meta, marketplaces and the site all need the same attribute and you would otherwise rebuild it three times.
• Feed refresh timing is already a problem. Every extra layer is another step in the chain, and how often the feed updates matters more than which layer does the formatting.

Start with rules because they are reversible and fast. Move the fix upstream once you know it works.

---

Sources

• Google Merchant Center Help: Set up your attribute rules
• Google Merchant Center Help: About supplemental feeds
• Google Merchant Center Help: Title [title]