| 开发者 | feedrobin |
|---|---|
| 更新时间 | 2026年9月28日 02:07 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
g:gtin from WooCommerce's own GTIN field; g:identifier_exists set to false when it is empty.)g:price including tax; g:sale_price only inside the sale's date range.)g:item_group_id.)g:color and g:size from product attributes, term names rather than slugs.)Activate this plugin, copy the link from WooCommerce → FeedRobin, and in Merchant Center go to Settings → Data sources → Add product source → Add products from a file and paste it there. Google then reads your products on its own and shows you, product by product, anything it still wants changed.
Almost always a caching plugin. Page caches store the first copy of a page they see and serve it to everyone after — and a feed that is streamed out in pieces can be cached as just its last piece, a well-formed file with no products in it. It does not look broken; it looks empty. This feed tells caches not to keep it, using the signal WP Super Cache, W3 Total Cache, LiteSpeed Cache and WP Rocket all respect, and closes any buffer they have already opened. Verified on a live LiteSpeed host. If you use a different cache and see an empty feed, tell us in the support forum with its name.
Not out of the box. WooCommerce runs your shop; the file Merchant Center asks for is added by a plugin, and this is one — the smallest one we could make.
Every time. There is no schedule to set and none to miss: the feed is built at the moment Google fetches it, from whatever your shop says right then. Google decides how often it fetches — daily by default, adjustable in Merchant Center.
They stay in the feed, marked out of stock, so channels pause them and resume when the stock returns.
Meta accepts Google's feed format as a file type, so the link can be added in Commerce Manager. A handful of values differ between the two specifications — the stock status is the notable one — so if Meta shows odd availability for your products, that is why. FeedRobin writes Meta its own file, in Meta's own words.
No, and you never will. The feed link works, keeps working, and is not limited, time-restricted or nagged about. FeedRobin is a separate subscription for the things one file cannot do: checking the catalogue and writing the other channels their own files.
Not by browsing your shop. The link contains a long random code, and the page asks search engines not to list it. Everything in it is already visible on your storefront anyway. If you ever share the link by mistake, create a new one from the settings screen — the old address stops working the moment you do.
No. It runs isolated from your theme, your store pages and your checkout: the feed is only built when a channel asks for it, in batches of 200 products, and a shopper browsing your shop never triggers it.
It should not, since 1.0.4: the feed answers to its address directly, whether
or not WordPress's list of pretty addresses knows about it. If you still see
"not found", your server is not sending unknown addresses to WordPress at all —
the usual cause is a missing .htaccess on Apache. Saving Settings →
Permalinks once rewrites it; or use the plain-permalink form of the link,
which the settings screen shows when pretty permalinks are off.
The feed uses the brand from WooCommerce brands, Perfect Brands, YITH, or the
product's brand attribute. If a product has none of these, the Brand field in
the settings is used. It is empty by default.
Each variation, not the parent product — those are what a shopper actually buys, and what carries the price and the stock. Every one is tagged with the parent's id so Google knows they belong together, and each title says which variation it is.
Yes. The feed has nothing to do with how your shop looks — it reads your products straight from WooCommerce.
brand attribute.