Feed rules: how to clean titles, prices and descriptions without editing products one by one
A beginner-friendly guide with a hypothetical before/after example and a final check before you send your catalog to each channel.
Julia Villegas

Feed rules help you clean and transform your product feed before sending it to Google, Meta, TikTok or other advertising channels. If your titles mix brand and category, prices use inconsistent decimal formats or descriptions include HTML, a rule can fix the pattern consistently without editing every product one by one.
What feed rules are
A feed rule is an instruction that applies to many products in your catalog to modify, complete, filter or reorganize their data. Instead of opening hundreds of product pages and editing each one manually, you define a condition and an action.
For example:
- If the
brandfield is empty, extract the brand from the title. - If the description contains HTML tags, remove them before export.
- If the price uses a comma as the decimal separator, convert it to the format required by the channel.
- If the product is out of stock, exclude it from a campaign set.
- If the title does not include the brand, add it at the beginning.
For beginners, it helps to think of a product feed as a living spreadsheet. Each row is a product. Each column is an attribute, such as id, title, description, price, availability, link or image_link. Feed rules are controlled formulas that prepare that spreadsheet before it is published to a channel.
Google Merchant Center documentation says that product data should accurately describe what you sell and meet the requirements for the target country, product type and destination. Its product data specification covers required attributes and recommendations such as using stable IDs, valid links, consistent prices and useful titles.
In practice, feed rules do not replace good product data in your store. They create a clean transformation layer between your commerce platform and your advertising channels, so each destination receives data in a clearer and more usable format.
Why feed rules matter for catalog campaigns
Ecommerce teams often discover feed problems after the catalog has already reached the channel: rejected products, variants grouped incorrectly, prices that do not match the landing page, weak titles or descriptions full of code. By then, the issue is urgent.
Feed rules help earlier in the process because they create a controlled layer between the store and the platforms. That layer is useful when:
- Your store data is good enough for the product page but not ideal for ads.
- Each channel expects slightly different attributes or formats.
- The same error appears across many products.
- You want to segment the catalog by campaign, stock, season or category.
- You manage several catalogs and need a repeatable workflow.
A clean feed does not guarantee that every product will be approved, and it does not automatically improve performance. It does reduce operational friction: fewer manual fixes, fewer differences between channels and more control over what gets exported.
For a store with hundreds or thousands of SKUs, the biggest impact is usually visible in titles, prices and descriptions.
| Field | Common issue | What a rule can do |
|---|---|---|
| Title | Brand missing, internal codes included or wording in the wrong order | Reorder text, add brand or remove prefixes |
| Price | Inconsistent decimals or incorrect currency formatting | Normalize the format for the channel |
| Description | HTML, extra line breaks or duplicated text | Remove tags and create a readable version |
| Stock | Out-of-stock products sent to active campaigns | Filter products or create availability-based sets |
| Category | Internal taxonomy not useful for campaigns | Map products into campaign-ready categories or sets |
Feed rules example: before and after cleaning a product feed
Imagine an online running shoe store exporting a catalog from its ecommerce platform. The team wants to send products to Google Shopping and reuse part of the catalog in dynamic product campaigns. When reviewing the feed, they find this row.
This is a hypothetical example, not a universal recommendation.
| Field | Before |
|---|---|
id |
SKU-9842-BLK-42 |
title |
Running Pro 42 black |
brand |
Vanta |
description |
Paragraph, line break and list HTML tags around “Technical shoe for daily running. Lightweight. Flexible sole.” |
price |
89,9 USD |
availability |
in stock |
link |
https://example.com/products/running-pro-black-42 |
The product is not necessarily wrong in the store. But as advertising feed data, it can be improved:
- The title does not start with the brand.
- The price uses a comma decimal separator and only one decimal digit.
- The description contains HTML.
- The ID looks stable, which is good and should usually not be changed.
- The link looks valid, but it should still be checked against the actual product page.
After applying feed rules, the exported version could look like this:
| Field | After |
|---|---|
id |
SKU-9842-BLK-42 |
title |
Vanta Running Pro black size 42 |
brand |
Vanta |
description |
Technical shoe for daily running. Lightweight. Flexible sole. |
price |
89.90 USD |
availability |
in stock |
link |
https://example.com/products/running-pro-black-42 |
The ideal title depends on the product, the channel, the market and how your customers search. The important part is the method: identify repeated patterns, apply reviewable rules and avoid changing critical fields without a clear reason.
How to create feed rules step by step
Before changing anything, work with a preview, copy or workflow where you can inspect the result. A poorly designed rule can affect many products at once.
1. Look for patterns, not one-off issues
Start by reviewing a sample of your catalog. Look for issues that appear repeatedly:
- Descriptions containing tags such as
<p>,<br>or<li>. - Titles that do not include the brand.
- Products with empty prices or inconsistent price formats.
- Internal categories that are not useful for campaign segmentation.
- Variants where color or size is stored inconsistently.
If a problem affects only one or two products, it may be better to fix it in the store. If it affects dozens or hundreds, it is a good candidate for a rule.
2. Choose the source field and destination field
A rule needs to know where to read from and where to write the result. For example:
- Read
descriptionand write a clean version todescription_clean. - Read
brandandtitleto create a newtitle_export. - Read
priceand write a formatted value toprice_formatted.
Creating separate output fields can be safer than overwriting the original field immediately. It lets you compare before and after before committing the output to a channel feed.
3. Define a clear condition
Not every rule should apply to every product. Some rules need conditions:
- If
brandis not empty andtitledoes not contain the brand, add it. - If
descriptioncontains signs of HTML, clean the text. - If
availabilityisout of stock, exclude the product from the campaign set. - If
priceis empty, do not export the product until the issue is fixed.
The more specific the condition, the lower the risk of changing products that were already correct.
4. Apply a simple transformation
Avoid overly ambitious rules at the beginning. Several small, understandable rules are usually safer than one opaque rule that tries to do everything.
Examples of simple transformations include:
- Remove HTML tags from the description.
- Replace a comma decimal separator with a period.
- Add two decimal places to the price.
- Concatenate brand, model, color and size into the export title.
- Convert internal availability values to the format expected by the channel.
5. Review a sample before saving
This step is especially important if you use AI to help write feed rules. AI can speed up the drafting of conditions or mappings, but the result should be reviewed in the editor before you apply it.
Check easy products, unusual products and edge cases:
- One product with a complete brand.
- One product without a brand.
- One product with a discounted price.
- One out-of-stock product.
- One variant with size or color.
- One product with special characters.
The question is not only “does the rule work?” It is also “does it work without breaking products that were already fine?”
How to do it with AdMotion and AI-assisted rules
In AdMotion, Feed Manager is built to connect a store catalog or any product file, clean and segment it with rules, and publish it to each channel through a URL generated on every download. AdMotion can also help write rules and sets from a natural-language description, with review before changes are applied.
A basic workflow looks like this:
- Connect the catalog. You can start from a connected store, such as Shopify, BigCommerce or Tiendanube, or from a product file or feed.
- Map the fields. Match source fields to the fields you will use: title, description, price, stock, brand, image, link, ID and any other required attributes.
- Describe the rule. For example: “Remove HTML from the description, add the brand to the beginning of the title if it is not already included, and normalize the price with two decimals.”
- Review the proposal. If you use AI assistance, do not accept a rule blindly. Review the conditions, affected fields and output examples before saving.
- Create sets or filters. You can separate products by availability, category, season or any field that is useful for your campaigns.
- Generate the channel feed. With Export Channels, the catalog can be prepared for Meta, Google Shopping and Dynamic Feed, TikTok, Pinterest, Snapchat, Criteo, Microsoft Advertising, Thribee, ChatGPT or a custom channel.
- Check the feed against the channel specification. The analyzer helps review each feed according to the selected channel before you use it.
- Copy the URL into the advertising platform. The channel will download the feed according to its own settings.
There is one important limitation to understand: the frequency at which you import data into AdMotion and the frequency at which each channel downloads the feed are not the same thing. A feed published by URL is generated on each download, but that does not mean the channel collects it instantly or at the same frequency as your store updates data.
If you also need product images that include fields such as price, brand or stock, the Templates Editor can generate one creative per product from catalog fields. For this guide, the focus is feed cleaning; creative automation makes more sense once the base data is consistent.
Common mistakes when automating feed cleanup
Automation does not remove the need for review. These are common mistakes when teams start using feed rules.
Changing the product ID
The ID should be stable. If you change it unnecessarily, a channel may interpret the item as a new product. Keep a consistent ID logic and avoid rules that rewrite identifiers unless you have a clear, controlled reason.
Creating titles that are too long or artificial
Adding brand, color, size or material can help, but a title should not become an unreadable list of attributes. It should describe the product naturally and match what the user will find on the landing page.
Removing HTML without checking the resulting text
Removing tags is useful, but it can leave words stuck together or sentences without punctuation. Review the output. A description without HTML can still be poor if it becomes confusing.
Formatting prices without checking currency and tax logic
Changing commas to periods is not enough. The feed price should be consistent with the landing page and with channel and market requirements. If you sell in several countries, check currency, tax treatment and availability by destination.
Applying global rules to very different product groups
A rule for fashion may not work for electronics. A rule for hotels will not necessarily work for automotive inventory. If your catalog mixes very different product families, create specific sets and rules.
Final checklist before sending the feed
Before copying the feed URL into an advertising platform, review this list:
- The
idis stable and does not change between exports without a reason. - The
titledescribes the product and does not contain unnecessary internal codes. - The
descriptionhas no visible HTML and no duplicated text. - The
pricematches the landing page and uses the expected format. - The
availabilityreflects the actual stock status in the store. - The
linkopens the correct product page, not a generic page. - The main image matches the advertised product.
- Excluded products are excluded by an intentional rule.
- Required channel attributes are present when they apply.
- You have tested edge cases, not only “perfect” products.
If you manage campaigns for several stores, document each rule in one plain-language sentence: what problem it solves, which products it affects and when it should be reviewed. For agencies, that discipline prevents a rule that works for one client from being copied into another catalog without context. The agency solution explains how the platform organizes projects, permissions and rules that can be copied between feeds.
What to do this week
- Export or review a sample of your product feed. Include varied products: best sellers, variants, out-of-stock items, discounted products and different categories.
- Mark three repeated issues. Good first candidates are HTML in descriptions, irregular price formatting and titles without brand.
- Write one rule per issue in plain language. Define the condition, affected field and expected result before implementing it.
- Compare before and after. Review normal products and edge cases. If the rule fails on an important case, adjust it before applying it to the full feed.
- Prepare the channel feed. Check required attributes and consistency with the store. If you want to centralize this workflow, you can try Feed Manager with your own catalog.
Feed rules are a practical way to turn messy catalog data into a more reliable source for campaigns. Start with small rules, always review the output and keep business decisions separate from the data cleanup layer.
Frequently asked questions
What is the difference between editing products and using feed rules?
Editing products changes the information in your store or original catalog source. Using feed rules creates a transformation layer before the data is sent to each channel. That layer is useful for adapting formats, cleaning text or filtering products without necessarily changing the original product page.
Can I use AI to create feed rules?
Yes. AI can help draft rules or product sets from a natural-language description. You should still review the proposal before saving it. Check the conditions, affected fields and output examples, because a poorly designed rule can change many products at once.
Does a clean product feed prevent Google or Meta rejections?
No approval is guaranteed, because every channel applies its own policies and requirements by product, market and destination. A clean feed helps reduce avoidable errors such as missing attributes, inconsistent prices, broken links, HTML in descriptions or data that does not match the store.
Sources
- Feed Manager de AdMotion — AdMotion
- Especificación de datos de producto de Google — Google
Related posts

Product feed format: CSV, XML or Google Sheets?
Choosing between CSV, XML and Google Sheets is not just a technical preference. It depends on catalog size, update frequency, team workflow and the ad channels you need to feed.

Product titles: how to clarify variants without stuffing your feed
Product titles help Google Shopping, Meta and other channels understand what each catalog item is. Learn a simple brand/type/attribute pattern to describe variants clearly without artificial keyword stuffing.

Multi-channel feed: how to organize one catalog for Meta, Google, TikTok and more
A multi-channel feed lets you start from one product catalog and create channel-ready versions for Meta, Google, TikTok, Pinterest and other platforms. This guide explains the fields, sets, rules, feed URLs and checks you need before activating a new destination.