Long-form playbooks for ecommerce product feed work — written for engineers and operators who want to ship clean feeds at scale.
Each guide is a maintained, source-checked playbook: exact issue names quoted from the live platforms, step-by-step fix workflows, the edge cases that cost real review cycles, and links into the free tools that automate the deterministic checks.
How to turn a valid product feed into one that wins clicks and sales: title structure, complete attributes, custom labels, and error fixes across every channel.
Read guideHow AI is reshaping product feed management — from AI-generated titles in 7 languages to vision-based image quality, taxonomy mapping, GTIN validation, and POAS signals.
Read guideA diagnostic guide to Google Merchant Center disapprovals: the 12 most common causes, how to fix each one, and how to stop them recurring before re-upload.
Read guideWhy Google Merchant Center suspends accounts (misrepresentation, policy), how to fix the root cause, complete verification, request a review, and avoid the cool-down trap.
Read guideHow to populate Google Shopping custom labels 0-4 from GA4 performance data — hero, bestseller and dead-stock segments that let you bid on what actually converts.
Read guideHow AI shopping agents read product feeds in 2026: the OpenAI ACP feed spec, Google’s Universal Commerce Protocol, and how one clean catalog serves both.
Read guideThe exact XML format Google Shopping requires — RSS 2.0 envelope, required g: attributes, a copy-ready example feed, and how to build and validate it by hand.
Read guideMeta rejects an entire feed row when one field is invalid — applink is the classic trigger. Diagnose Commerce Manager row-level validation and recover rejected products.
Read guideHow product feed management works in practice: the five-stage pipeline, channel specs as contracts, build-vs-buy, evaluation criteria, and what breaks at scale.
Read guideHow a Criteo product feed works: accepted formats, required fields, google_product_category, OneTag id matching, import schedules, and fixing rejected catalogs.
Read guideThe glossary defines one concept per page in a few hundred words; a guide is a complete working playbook — typically 2,500+ words with step-by-step workflows, edge cases, honest limitations, and an author who maintains it. Read the glossary to understand a term, read a guide to actually fix or build something.
Yes — each guide states what its claims are checked against (for example, the live Merchant Center documentation) and carries a visible last-updated date. When Google changes an enforcement flow or a spec, the affected guide is revised rather than left to rot; the sitemap reflects the real modification date.
No. Every workflow is written platform-agnostic first — the steps work whether you manage feeds by hand, with scripts, or with any feed tool. Where FeedArc automates a step, the guide says so explicitly, and the free browser tools (feed validator, GTIN validator, disapproval diagnostic) cover the deterministic checks without an account.