Google Ads

Feed Rules

Also called Merchant Center rules, attribute rules

Transformations applied inside Merchant Center that reshape incoming product data before Google uses it, without touching your website.

Quick facts: Feed Rules

Category
Google Ads
Also called
Merchant Center rules, attribute rules
Level
Intermediate
Affects
Product approval, query matching, campaign segmentation
Where to see it
Google Merchant Center (Products, then Feeds, then Rules)
In this article4
  1. How feed rules work
  2. Why feed rules matter
  3. Common mistakes with feed rules
  4. How to act on it

How feed rules work

Merchant Center takes the product data your shop sends and stores it as a feed. A feed rule sits between the two: it reads the raw value arriving from your website and writes a different value into the field Google actually uses. Nothing on your website changes. The rule runs every time the feed is fetched, so the transformation keeps applying rather than being a one-off edit.

The building blocks are simple. A rule can set a field to a fixed value, copy it from another field, join several fields together, find and replace text inside one, or map your list of values onto Google’s. Rules can be conditional, so a change only applies to items that match a test — a particular product type, a brand, an empty field. They can also be layered, each one taking the output of the rule before it.

Why feed rules matter

Most shop platforms were built to run a shop, not to feed an advertising system. The category names, title format and size labels that read well on your own site are rarely the ones Google’s taxonomy and matching expect. Feed rules close that gap without asking a developer to rebuild the export, which for a small business is often the difference between launching this week and launching never.

They also shorten the repair cycle. When Merchant Center rejects a batch of items for a missing or malformed attribute, one rule can supply the value for the whole affected group, and those products return to the auction at the next fetch instead of waiting on a site release.

Common mistakes with feed rules

The most damaging is using a rule to state something that is not true on the page. Price, availability and identifiers are checked against your landing page, so overriding them to clear a warning creates a mismatch that gets items disapproved rather than approved. A rule reshapes data; it does not invent it.

The second is stacking rules until nobody can explain the output. Because they run in order and each can overwrite the last, accounts that have collected fixes over several years often have rules quietly cancelling each other out. The third is treating the rule as the permanent home of the fix. If the underlying data is wrong in your shop, the same wrongness still reaches your customers, your product feed for other channels and your own reporting.

How to act on it

Start from the diagnostics report rather than from the rule builder. Find the attribute genuinely causing rejections or weak matching, write one rule for it, and use the preview to check the result against real items before applying. Name each rule after the problem it solves, so the next person reading the list can tell what it is for.

Where a value belongs in a separate file — seasonal labels, curated titles, data held in a spreadsheet — a supplemental feed is usually cleaner than a long chain of conditions. Push the important corrections back into the shop over time. Rules work best as a thin, readable layer on top of decent data, and an account that leans on dozens of them is really telling you the export itself needs proper feed management.

Do and do not

Do

  • Fix one attribute per rule and name it clearly
  • Preview against real items before applying a rule
  • Push permanent corrections back into the shop platform

Do not

  • Rewrite price or availability to clear a warning
  • Stack rules until the final value is unreadable
  • Assume a saved rule applies before the next feed fetch

Questions people ask about this

Do feed rules change my website?

No. A feed rule only alters the copy of your product data held inside Merchant Center. Your shop, your product pages and any other channel reading the same export are untouched. That is useful for speed, but it also means a rule can quietly disagree with what a shopper sees on the page, which is why price and availability should never be rewritten this way.

Should I use a feed rule or fix the data in my shop?

Use a rule when the fix is purely a formatting or mapping difference between your shop and Google's requirements, or when you need items approved quickly. Fix it in the shop when the data is genuinely wrong, because the same error is reaching customers and other sales channels. Many teams do both: the rule first, the permanent correction afterwards.

Why did my rule not appear to work?

Three causes cover most cases. The rule was saved but the feed has not been fetched again, so the old values are still stored. A later rule in the list overwrote the value. Or the condition never matched, usually because the source field is empty or spelled differently than expected. Preview the rule against real items to see which applies.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.