Google product feed integration — generate and maintain an XML feed for Google Merchant Center: Shopping, Performance Max, and free listings. Prices, stock, and images sync via URL without manual exports. VivaCoding in Cyprus (Paphos) connects feeds from €290 in typically 3–7 days: WooCommerce, Shopify, Laravel, and custom catalogues.
A Google product feed is an RSS 2.0 XML file with namespace xmlns:g="http://base.google.com/ns/1.0": each <item> describes a SKU — id, title, link, image_link, price, availability, and more. Merchant Center fetches the feed over HTTPS and uses it in Shopping, Performance Max, free listings, and local inventory. Without a valid feed and verified domain, products will not enter Google ads or organic product surfaces.
Below: why the feed matters, 2026 specification requirements, VivaCoding packages, alignment with on-site Product schema, comparison with Yandex feeds, and when Content API beats a file.
Key takeaways
- Primary feed over HTTPS with cron is the main path; manual upload is for testing only.
- VivaCoding ranges: Start from €290, Business from €490, Custom from €890+; basic integration usually 3–7 days.
- Core minimum: id, title, description, link, image_link, price, availability; prices and stock must match the site.
- For Cyprus/EU: EUR, shipping in the feed; from September 2026 — minimum_order_value for EU/UK/CH when you enforce a minimum order.
What Google product feed integration means
Integration means generating Merchant Center–compatible XML from your CMS/ERP and publishing a stable URL. Scope covers: field mapping → g: attributes, export filters, schedule, Merchant Center Diagnostics, and fixes for disapprovals (broken links, GTIN, images, price mismatch).
Where the feed connects
- Google Shopping / Performance Max — product ads with prices and images from the feed.
- Free listings — organic product cards in Shopping and search.
- Dynamic remarketing — creatives from the catalogue.
- Local inventory (LIA) — with physical stores and a separate local feed.
2026 spec requirements that break exports
From the 2026 Merchant Center specification update and integrator practice:
- RSS 2.0 +
g:namespace; UTF-8; public URL reachable by Googlebot. - Seven core fields per SKU: id, title, description, link (200 OK), image_link, availability, price with ISO currency (EUR for Cyprus).
- brand / gtin / mpn — per category rules; brand required for new branded products.
- Images: from 31 Jan 2027 minimum 500×500 px; warnings appear earlier in Needs attention.
- 2026 additions:
handling_cutoff_time,video_link; from 30 Sep 2026minimum_order_valuefor EU/UK/CH when you have a minimum order. - Price and availability on the landing page must match the feed — or policy violations follow.
Platforms we support
| Platform | Typical path | When custom |
|---|---|---|
| WooCommerce | Google Listings & Ads / feed plugin + tweaks | Variations, multi-warehouse, B2B |
| Shopify | Native sync + custom fields | Multi-region, currencies |
| OpenCart / Bitrix | Export module + mapping | Non-standard attributes |
| Laravel / custom | RSS XML generator + cron | Large catalogues, Content API |
Packages
Prices cover technical integration. Google Ads spend and platform fees are separate. Similar band to Yandex feed integration and other Cyprus integrations.
| Package | From | Timeline | Includes |
|---|---|---|---|
| Start | €290 | 3–5 days | Primary XML feed, URL, basic mapping, Diagnostics, Merchant Center guide |
| Business | €490 | 5–10 days | Start + shipping/tax, variations, GTIN/brand, GA4 enhanced ecommerce, failure alerts |
| Custom | €890+ | 2–4 weeks | Content API, multi-country feeds, LIA, dual YML+Google from one catalogue |
How we connect — 4 steps
- Catalogue audit — CMS, SKUs, currency (EUR), shipping, goals (Shopping / PMax / free listings).
- Merchant Center — account, domain and site verification, country/currency setup.
- Generator and test — XML at URL, staging, Diagnostics pass, price parity with the site.
- Go-live and monitor — primary feed in GMC, fetch schedule, Product schema on PDPs; 14–30 days support.
Feed and on-site structured data
Google recommends both a Merchant Center feed and Product schema (JSON-LD) on product pages — easier to verify price, stock, and title. We align feed fields with markup to avoid Diagnostics mismatches. This complements but does not replace the feed for Shopping/PMax.
Google vs Yandex
Yandex uses YML; Google uses RSS XML with g: attributes. Moderation, required fields, and currencies differ. Cyprus stores with RU audiences often need both — shared catalogue layer, two exporters (Custom package). Google-only — Start or Business is enough.
When it fits — and when it does not
Fits: online store with a live catalogue; you plan Shopping/PMax or free listings; you can fix cards (photos, GTIN, copy).
Does not fit: a handful of SKUs with no growth — manual upload may suffice; no HTTPS; you only need SEO without product ads — see website promotion and paid search.
Related services
- Yandex product feeds
- WooCommerce customization
- online store development
- online store promotion
- paid search & ads
- contacts
FAQ
What is a Google product feed?
An RSS 2.0 XML file of products for Merchant Center. Google fetches it from a URL and surfaces items in Shopping, PMax, and free listings.
How much does integration cost?
From €290 for a basic CMS feed, from €490 with shipping and GTIN, from €890 for API and multi-feeds. Ad spend is separate.
Do I need Google Merchant Center?
Yes — without a GMC account and domain verification the feed will not run in Shopping/PMax. We help with initial setup in Start.
How often does the feed refresh?
Generation via cron (often hourly or more for stock). In GMC you set fetch schedule — from daily to every 15 minutes on eligible plans.
Is a WooCommerce plugin enough?
For a simple catalogue — often yes, with field mapping. Complex variations, shipping, and policy errors usually need custom mapping.
Can you also build a Yandex feed?
Yes — see Yandex product feed integration or dual export in Custom.