WooCommerce does not generate a product feed. Every channel that sells your\nproducts wants one \u2014 Google Merchant Center, Facebook and Instagram catalogues,\nMicrosoft\/Bing Shopping, price comparison sites \u2014 and each of them expects a\nfile your store does not produce.<\/p>\n\n
This plugin adds that file. One URL, generated when it is fetched, so it is\nnever out of date: change a price in WooCommerce and the next fetch has it.<\/p>\n\n
What goes into the feed<\/strong><\/p>\n\n What it deliberately leaves alone<\/strong><\/p>\n\n Do you need FeedRobin?<\/strong><\/p>\n\n No. The URL is yours: paste it into Merchant Center and you are done. FeedRobin\nadds what a feed on its own cannot \u2014 the other channels in their own formats,\nchecks for the errors that get products rejected, and rules to fix data without\ntouching the store. There is a button for it on the settings screen, and\nignoring it costs you nothing.<\/p>\n\n External services<\/strong><\/p>\n\n The plugin makes no outbound requests of any kind. It does not send your\ncatalogue, your settings or any usage data anywhere. The Connect to\nFeedRobin<\/strong> button is an ordinary link: pressing it opens feedrobin.com in a\nnew tab with your feed URL prefilled, and nothing is transmitted unless you\nchoose to connect there. FeedRobin is a separate paid service with its own\nterms<\/a> and\nprivacy policy<\/a>; using this plugin does not\nrequire it.<\/p>\n\n\n It is unguessable rather than secret: it carries a random token, and the page\nis served with a noindex header, so it will not be crawled or listed. Everything\nin it is already on your storefront. If the URL leaks, create a new one from the\nsettings screen \u2014 the old address stops working immediately.<\/p><\/dd>\n The feed is only built when something fetches it, in batches of 200 products,\nand it is never built while a shopper is on the site. Nothing is added to your\nstorefront pages.<\/p><\/dd>\n No. The feed tells page caches not to store it (the constant WP Super Cache,\nW3 Total Cache, LiteSpeed and WP Rocket all honour) and closes any output\nbuffer they have opened, so a channel always fetches the current catalogue\nrather than a copy. That matters more than it sounds: a cached feed does not\nlook broken, it looks empty.<\/p><\/dd>\n Go to Settings \u2192 Permalinks<\/strong> and press Save once. WordPress rebuilds its\nrewrite rules, and the pretty feed URL starts working. The plugin also serves a\nquery-string version of the same feed for stores with plain permalinks.<\/p><\/dd>\n The variations, not the parent \u2014 those are what a shopper buys and what carries\nthe price and stock. Each one keeps the parent's id as \n
item_group_id<\/code> \u2014 which is how a channel knows your blue Large and your red Small are one product.<\/li>\nbrand<\/code> attribute \u2014 wherever your store already keeps it.<\/li>\n\n
\n
\n
Is my feed URL public?<\/h3><\/dt>\n
Does it slow my store down?<\/h3><\/dt>\n
I use a caching plugin \u2014 does that break the feed?<\/h3><\/dt>\n
My feed URL returns \"not found\".<\/h3><\/dt>\n
Variable products: what appears in the feed?<\/h3><\/dt>\n
item_group_id<\/code>, and its\ntitle says which variation it is.<\/p><\/dd>\n\n<\/dl>\n\n\n1.0.0<\/h4>\n\n
\n