Short answer: To move from a feed plugin to RSS Feed Creator without surprises, build the new feed first and run both side by side. Compare the product counts, IDs, titles, prices and availability, recreate the rules that the old feed applied, and make sure the product IDs match so that Google and Meta recognise the same products. Only then change the address that Merchant Center and Meta fetch, keep the old feed available for a couple of weeks and watch the diagnostics. The new feed needs no plugin on your store, which is the main reason to switch.
Why stores switch
A feed plugin lives inside your store. It has to be updated with the platform, it can clash with other plugins and it adds work to a server that is supposed to serve customers. RSS Feed Creator works from the outside: it reads the product data that your WooCommerce or Shopify storefront publishes, or a CSV link, and builds the feed on its own servers. Nothing is installed on your store and no keys are shared.
Other reasons are practical. A store may be changing platform and want a feed that does not depend on it, an agency may want one tool for many clients, or the owner may simply want a feed that is easy to understand and that has a free plan to test with. Whatever the reason, the move is a change of data source for the channels, and channels are sensitive to changes in the data they track, so it should be planned.
Step 1: write down what your old feed does
Before you touch anything, document the old feed. Open its address in a browser, or download the file, and note:
- how many products it contains and whether it includes variants as separate items;
- which identifier it uses as the product id: SKU, database ID or something else;
- whether titles are rewritten, for example brand first or size at the end;
- whether prices include or exclude tax, and whether any price adjustment is applied;
- whether out-of-stock products are removed;
- which extra attributes it adds, such as colour, size or categories mapped to Google’s taxonomy.
This list is your specification. Everything on it is either something RSS Feed Creator does in the same way, something you recreate with a rule, or something you need to handle in another way. Knowing which before the switch is the difference between a smooth move and a scramble.
Step 2: build the new feed next to the old one
Create the new product feed exactly as for a new store: choose “My store”, enter the address or the CSV link, read the preview and press Create. The route is described in connect WooCommerce, Shopify or a CSV to RSS Feed Creator. Do not give the new address to Google or Meta yet. For now it is only a file you can open and compare.
The free plan is enough for the comparison if your catalogue has up to 50 items. For larger catalogues, the preview shows the first products and the total found, which is already a good test; the Store or Business plan is needed to carry the whole feed.
Step 3: compare side by side
Put the two files next to each other and check the same list for both:
| Check | What to look for |
|---|---|
| Product count | Similar numbers; differences explained by out-of-stock, no price or no image |
| IDs | The same value for the same product |
| Titles | Same wording, or an intentional improvement |
| Prices and sale prices | Equal to the product page, in the same currency |
| Availability | Same status for ten sample products |
| Images | Main image loads and is the right one |
| Brand, GTIN, category | Present where the old feed had them |
Pick a sample of products that includes a sale item, a sold-out item, a product with variants and one with a very long title. These are the cases where feeds differ most. The tour of every field in inside an RSS Feed Creator product feed tells you where each value comes from.
Step 4: make the IDs match
This step matters most. Google and Meta track a product by its identifier. If the new feed uses different IDs, the channels see new products and the history of the old ones, including approval status and performance data, is lost. RSS Feed Creator uses the SKU for WooCommerce products, and the product ID if there is no SKU. For Shopify it uses the variant SKU, or the variant ID if there is none. For a CSV it uses the id column.
If your old feed used the database ID and the new feed uses the SKU, you have a mismatch. Fixing it is easiest at the source: set SKUs equal to the old IDs, or add an id column with the old values in a CSV. If you cannot match them, accept that the channels will treat the products as new and plan the switch for a quiet period. Duplicate products in your feed: IDs, GTINs and cleanup covers what to do about leftovers.
Step 5: recreate the rules
RSS Feed Creator has three product rules on the management page: skip out-of-stock products, a title template with the product title, brand and category as building blocks, and a percentage price change, plus a currency fallback. Map the old behaviour onto them. If the old feed removed out-of-stock products, leave the skip option on, which is the starting setting. If it built titles as brand plus name, write that in the template. Leave the price change at zero unless the old feed really applied one, and then compare the result with the page. See product rules in RSS Feed Creator: stock, titles and prices for the practical details.
For the extras that the old feed added and the new one does not, such as clothing sizes or custom labels, decide whether a supplemental feed in Merchant Center is the right home for them, as described in supplemental feeds in Merchant Center.
Step 6: switch the channel
When the comparison is clean, change what the channels fetch. In Google Merchant Center, if the existing feed allows you to edit its file location, replace the old address with the new one in the same feed, because that keeps the feed’s identity and history. In Meta Commerce Manager, do the same in the existing data source if possible, or add the new data feed and remove the old one after the first successful fetch. Then start a fetch by hand and look at the result. The paths are Products, Feeds, Scheduled fetch in Merchant Center and Catalog, Data sources in Meta Commerce Manager.
Keep the old plugin and its feed in place for now. It costs nothing and gives you a way back if something looks wrong.
Step 7: watch for two weeks
For the first two weeks, look at the diagnostics every few days. Expect small differences in the number of products, and investigate anything that affects many products at once, such as a price mismatch after a tax setting or a wave of missing images. The reads counter on the management page confirms that the channels are fetching, and the update time shows that the feed is refreshing, every 3 hours on the free plan and every 30 minutes on paid plans.
When everything has been stable for two weeks, deactivate the old plugin feed, and later remove the plugin if you no longer need it. Delete the old feed only when you are sure that no channel still fetches it. The plans for the new feed are on the pricing page.
Common pitfalls to avoid
Four mistakes cause most of the trouble in a feed switch. The first is changing IDs, covered above. The second is switching on a day with a big sale, when prices and stock move quickly and any difference is amplified. The third is deleting the old feed at once, which removes your way back. The fourth is changing three things together, for example the tool, the title pattern and the price rules, so that nobody can tell which change caused a warning. Change the tool first, keep everything else equal, and improve titles or prices afterwards, one step at a time, with a note of the date.
Related reading
- Product Feed Checklist: 25 Checks Before You Submit
- Feed Rules vs Fixing Store Data: Where to Make Changes
- Merchant Center Disapproved Products: Causes and Fixes
The bottom line
Switching feed tools is safe when you treat it as a controlled move: specify the old feed, build the new one next to it, match the IDs, recreate the rules, change the channel’s fetch and watch for two weeks. RSS Feed Creator needs nothing installed on your store, so the old plugin can stay until you are sure.
FAQ
Will my product history in Google be lost if I switch?
Not if the product IDs stay the same. Match the IDs first, because channels track products by their identifier.
Which ID does RSS Feed Creator use?
The SKU or product ID for WooCommerce, the variant SKU or ID for Shopify and the id column for a CSV.
Can I run both feeds at the same time?
Yes. The new feed is just a file until you give its address to a channel, so you can compare it with the old one first.
Do I need to install anything on my store?
No. RSS Feed Creator reads the public product data from outside, so no plugin and no keys are needed.
What if some old rules cannot be recreated?
Use the title template, the stock option and the price percentage for what they cover, and consider a supplemental feed in Merchant Center for extra attributes.


