google-merchant-product-feeds
Skill1 starsChanged 18 days agoMITView on GitHub
Build a Google Merchant Center product feed item with the required id, title, description, link, image, availability, and price fields. Use when exporting products to Merchant Center, Content API items, or a product feed file.
In this repository28 other files it gives its agents.
- b2b-pricingSkill
- catalog-import-and-migrationSkill
- checkout-ux-and-conversionSkill
- conversion-event-trackingSkill
- ecommerce-seo-structured-dataSkill
- fraud-and-risk-basicsSkill
- headless-nextjs-storefrontSkill
- inventory-and-multi-warehouseSkill
- iranian-payment-gatewaysSkill
- marketplace-search-and-rankingSkill
- mcp-store-toolingSkill
- multi-vendor-payoutsSkill
- order-and-webhook-reliabilitySkill
- payment-gateway-integrationSkill
- product-catalog-modelingSkill
- product-description-guardrailsSkill
- returns-and-refundsSkill
- rtl-and-persian-localizationSkill
- shopify-app-developmentSkill
- storefront-accessibilitySkill
- storefront-performanceSkill
- stripe-paymentsSkill
- subscription-billingSkill
- tax-and-shippingSkill
- vector-product-searchSkill
- woocommerce-plugin-developmentSkill
- woocommerce-rest-apiSkill
- wordpress-plugin-securitySkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Use this skill when a catalog becomes a Merchant Center item.
- Very specific: line 22
Run node scripts/check-feed-item.mjs --file item.json from this skill directory.
- Very specific: line 23
Keep id stable for the life of that unit.
- Very specific: line 58
Do not put "free shipping" or a competitor name in title or description.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Google Merchant product feeds
Use this skill when a catalog becomes a Merchant Center item. On-page JSON-LD is the structured-data skill. Generated titles and descriptions follow the description-guardrails skill, then the structured-title rules below.
Attribute names and limits below follow Google's Merchant Center product data specification. Re-check that specification when a disapproval cites an attribute this skill does not list. The local checker does not call Google.
Procedure
- Emit one item per purchasable unit. A variant gets its own
id. Variants that shoppers choose among shareitem_group_id. - Fill the required attributes:
id,titleorstructured_title,descriptionorstructured_description,link,image_link,availability, andprice. - Match the landing page. The title, description, price, and availability a shopper sees are the values in the feed.
- Run
node scripts/check-feed-item.mjs --file item.jsonfrom this skill directory. - Keep
idstable for the life of that unit. A new id on every export creates a new product and drops history.
Field limits and the variant rules are in the attribute notes. An item that passes the checker is in assets/example-item.json. Worked examples and checks are in evals/tasks.json.
Required values
| Attribute | Rule |
id | Unique, stable, at most 50 characters. Use the SKU when the SKU fits. |
title | Plain text, at most 150 characters, or structured_title when the title was generated. |
description | Plain text, at most 5000 characters, or structured_description when the description was generated. |
link | http or https URL of the product landing page on the verified domain. |
image_link | http or https URL of the main product image. |
availability | in_stock, out_of_stock, preorder, or backorder. |
price | Decimal major units with a period, a space, and an ISO 4217 code, such as 15.00 USD. |
availability_date is required when availability is preorder. Provide it for backorder as well. The product data specification asks for that date on both.
Variants
Set item_group_id to the parent id for every variant. Google's specification marks item_group_id as required for variants in free listings, and for variants targeted at Brazil, France, Germany, Japan, the United Kingdom, and the United States. Put the variant's color or size in color and size when those attributes distinguish the unit. Apparel in those countries has extra required attributes (color, size, gender, age_group). Do not guess them. Read them from the catalog or leave the item out of the feed until they exist.
Generated text
If a title or description was produced by a generative system, do not put it only in title or description. Use structured_title or structured_description and set digital_source_type to trained_algorithmic_media. The ordinary title and description attributes are for text that was not created that way. The content still has to match the landing page and stay within 150 and 5000 characters.
Images
Merchant Center has announced a minimum image size of 500 by 500 pixels, with enforcement beginning 31 January 2027. Export images that already meet that size instead of waiting for the disapproval. The checker validates the URL, not the pixel size. Check dimensions in the image pipeline.
Gotchas
- A formatted price such as
$15.00or15,00 USDis not thepriceattribute. Use15.00 USD. - Changing
idwhen the SKU gains a prefix splits the product in Merchant Center. - Out-of-stock items still need a price, and the landing page still needs to show that price.
- Do not put "free shipping" or a competitor name in
titleordescription. - GTIN is not universally required. Submit a real GTIN when the product has one. Do not invent digits.
identifier_existsis the attribute Google documents when you do not have a GTIN; confirm the current rule for that category before setting it false.
Verification
- The checker exits 0 on the feed file.
- Each variant id is unique and stable, and shares
item_group_idwith its siblings. - A spot-check opens
linkand sees the same price text and availability. - A generated description is in
structured_description, not only indescription.
Evaluation
Worked examples and the checks they must satisfy are in evals/tasks.json.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

