If you sell through WooCommerce, you already have most of what you need to auto-post new products to social media the moment they go live — you just need to find the right feed URL and connect it correctly. WooCommerce runs on WordPress, which means it inherits WordPress’s built-in RSS infrastructure, but the default blog feed and a genuinely useful product feed are not the same thing, and mixing the two up is the single most common reason product-launch automation quietly fails. This guide covers exactly where to find your WooCommerce product feed, why the default feed usually isn’t the right one to automate from, and how to set up reliable auto-posting for new product launches without flooding your social accounts with unrelated blog content.
Every WordPress site, WooCommerce included, ships with a site-wide RSS feed at yourstore.com/feed/. That feed pulls in blog posts by publish date — and by default, WooCommerce products are a custom post type that WordPress’s default feed does not automatically include. This is the single most common point of confusion for store owners trying to set up product-launch automation: they grab /feed/, connect it to their auto-posting tool, and then wonder why new products never show up in their social feeds.
WooCommerce does register its own feed endpoints, but they’re not always obvious, and which one is “correct” depends on what you’re trying to accomplish.
| Feed URL Pattern | What It Contains | Good for Product Auto-Posting? |
|---|---|---|
/feed/ | Blog posts only, by default | No — products are excluded unless you modify the query |
/product-feed/ oder /?post_type=product&feed=rss2 | Products only, ordered by publish date | Yes — this is the standard WooCommerce product feed pattern |
/product-category/{category}/feed/ | Products from a single category | Yes — useful for auto-posting only specific product lines |
| A dedicated SEO/feed plugin’s product feed | Configurable — often includes price, stock status, and images | Yes — often the richest option if you already run one |
https://yourstore.com/?post_type=product&feed=rss2 in your browser. If WooCommerce’s product post type is registered as feed-visible (the default in most modern WooCommerce installs), you’ll see a valid RSS XML document listing your products.functions.php) that hooks into WordPress’s request filter to include the product post type whenever a feed is requested. Store owners who aren’t comfortable editing code should use the plugin route below instead.Auto-posting from the wrong feed doesn’t just mean missing products — it can mean the opposite problem too. If your blog and your product catalog both feed into a single automated pipeline without separation, you can end up flooding your social accounts with routine blog content when what your audience actually wants notified about is new inventory, or vice versa. Keeping a dedicated product feed separate from your blog feed lets you control cadence, tone, and destination independently: new products might go straight to Facebook and Pinterest (where product discovery drives real traffic), while blog content might be better suited to LinkedIn and X.
A well-configured WooCommerce product feed item typically includes the product title, a short description (usually pulled from the product excerpt or short description field, not the full product description), the product’s featured image, and the permalink to the product page. When that feed is connected to RSS auto-posting, each new product publish triggers a post to your connected social accounts built from exactly that data — title as headline, image as the visual, link driving straight to the buy page.
Some feed plugins also let you include price and stock status directly in the feed’s description field, which some store owners choose to surface in the auto-posted caption (useful for “new arrival, $XX” style posts) and others deliberately leave out (if prices change frequently and they don’t want stale pricing showing up in old social posts).
WooCommerce’s variable products (a shirt in five sizes and three colors, for example) are typically represented as a single parent product in the feed, not as one feed item per variation — which is generally the right behavior for auto-posting, since you don’t want ten separate social posts for ten variations of the same item. Be aware, though, that most RSS-based automation triggers off new publish dates or GUIDs, not content edits — so updating an existing product’s price or restocking it typically won’t trigger a new auto-post unless your feed setup specifically treats that as a new item. If you want restocks or price drops to generate their own posts, that usually requires a separate, deliberately configured feed or workflow rather than relying on the standard new-product feed.
/feed/ URL. Switch to the product-specific query or a dedicated feed plugin as described above.Because auto-posting is triggered by publish events, it pairs naturally with WooCommerce’s native scheduled publishing. Instead of manually posting a product to social media the moment it’s ready, you can set the product’s publish date and time in advance inside WooCommerce, let it go live automatically at that moment, and let your feed-based automation pick it up and post it within minutes — no one has to be at a keyboard when a product actually launches. This is particularly useful for planned drops, restocks announced ahead of time, or coordinating a product launch across time zones without anyone getting up at an inconvenient hour to hit publish manually.
It’s worth testing this end-to-end once before relying on it for a real launch: schedule a low-stakes product a few minutes into the future, and confirm it actually appears on your social accounts automatically once it goes live, before trusting the same setup for a launch that matters.
Stores running more than one WooCommerce site — separate brands, regional storefronts, or a wholesale and retail split — often want independent control over what posts where. Because each WooCommerce install generates its own feed, this is usually just a matter of setting up separate feed-to-social connections per site, each pointed at its own product feed and its own set of connected social accounts, rather than trying to merge multiple stores into a single feed and filtering downstream. Keeping the feeds separate at the source is almost always simpler to maintain than trying to reconstruct that separation after the fact.
WordPress’s core feed system supports feeds for any registered post type, and WooCommerce registers products as a post type, but whether that feed is exposed cleanly at a predictable URL depends on your specific WooCommerce version and theme. Testing the direct query URL is the fastest way to check.
Yes — WooCommerce’s category feed pattern (/product-category/{category-slug}/feed/) lets you scope a feed to just one product line, which is useful if you only want, say, new arrivals in one category triggering social posts while other categories stay silent.
Only if your feed’s description field includes price data and your automation setup is configured to use that description text in the post caption. Standard WordPress product feeds don’t include price by default; a dedicated feed plugin is usually needed to add it.
Set a featured image on every product before publishing — this is what most feed generators and auto-posting tools pull as the visual for the post. Products published without one typically post as text-only, which performs worse on visually-driven platforms like Pinterest and Instagram.
No — auto-posting from your product feed to social media doesn’t create duplicate content in the way it can for blog posts, since social posts aren’t indexed the same way as web pages. If anything, the resulting traffic and backlinks back to your product pages are generally beneficial, and consistent social activity around new inventory can also support broader brand-signal and engagement metrics over time.
Only with additional configuration. Standard product feeds are built around publish date, so a restock of an existing product usually won’t generate a new feed item on its own — you’d need a feed plugin or workflow specifically designed to flag stock-status changes as feed-worthy events.
Yes. Google Shopping (Merchant Center) feeds use a specific XML schema built for shopping ads, with required fields like GTIN and shipping data that social auto-posting doesn’t need. A standard RSS product feed is simpler and generally the better source for social media automation, even if both can technically be generated from the same plugin.
No — a single, well-formed WooCommerce product feed can typically drive multiple connected platforms at once. The feed itself doesn’t need to be platform-specific; formatting differences between Facebook, X, LinkedIn, and Pinterest posts are usually handled by the automation layer on top of the feed, not by maintaining separate feeds for each destination.
Auto-posting new WooCommerce products to social media works well once you’re pointed at the right feed — the mistake almost every store owner makes once is assuming the default blog feed already includes products, when it usually doesn’t. Set up a dedicated product feed (via a query URL, a code snippet, or a feed plugin), confirm it includes clean titles, images, and links, and connect that — not your blog feed — to your social automation. From there, every new product launch reaches your audience automatically, without anyone on your team having to remember to post it — and as your catalog grows, that reliability compounds into a meaningful, hands-off channel for driving traffic straight to your buy pages.