Google Merchant Center Feed Optimization: The PrestaShop Store Owner's Complete Guide

Why Google Shopping Ads Are Different -- And Why Feed Quality Is Everything

Before diving into feed optimization, it is worth understanding what makes Google Shopping ads uniquely powerful compared to other ad formats. When a Shopping ad appears in search results, the shopper immediately sees the product image, the exact price, and the product name -- all before clicking. This is fundamentally different from text ads where you have to convince someone to click based on a headline and two lines of description.

This visual immediacy means two things. First, shoppers who do click have already seen your product, your price, and your image -- they are pre-qualified, which leads to significantly higher conversion rates compared to text ads. Second, it means that your product data quality directly determines the quality of that first impression. A blurry image, a generic title, or a wrong price are visible before the click, not after. Your feed IS your ad creative.

Google is also constantly evolving this ad format. Shopping listings already require stock availability status (in stock, out of stock, preorder). The trend is clear: Google is moving toward displaying even more product data directly in search results. Stock quantity will likely be shown alongside price in the near future, giving shoppers real-time inventory visibility without visiting your store. The more complete and accurate your product feed is today, the better positioned you are for these coming changes.

Why Your Product Feed Determines Everything

Google Shopping does not work like Google Search. In Search campaigns, you choose keywords and write ad copy. In Shopping, Google decides which queries trigger your products -- and it makes that decision entirely based on the data in your product feed. There are no keywords to bid on. Your product titles, descriptions, categories, and attributes ARE your keywords.

This means a poorly optimized feed leads to three problems simultaneously: your products show for the wrong searches (wasting budget), they don't show for the right searches (missing revenue), and when they do show, they look worse than competitors' listings (lower click-through rates). Feed optimization is not a nice-to-have -- it is the foundation that every Shopping and Performance Max campaign is built on.

For PrestaShop stores, this is both a challenge and an opportunity. PrestaShop's product data model is flexible enough to support a rich feed, but most feed generation modules simply export whatever data exists in the database without optimization. The difference between a default export and an optimized feed can be a 2-5x improvement in Shopping campaign performance.

Product Titles: The Most Important Field in Your Feed

Google weighs the first words of your product title most heavily when matching products to search queries. A title that starts with your brand name wastes those critical first positions on information that doesn't help Google match your product to searches. The ideal title structure puts the most searchable terms first.

Title formula by product type:

• Generic products: [Product Type] + [Key Attribute] + [Size/Dimension] + [Material] + [Color] + [Brand]
  Example: "Linear Shower Drain 800mm Stainless Steel Tile Insert -- FlowLine Pro"
• Branded products (known brand): [Brand] + [Product Type] + [Model] + [Key Attribute]
  Example: "Geberit CleanLine60 Shower Channel 900mm Brushed Steel"
• Apparel: [Brand] + [Gender] + [Product Type] + [Attribute] + [Size] + [Color]
  Example: "Nike Men's Running Shoes Air Max 270 Black/White"

Title optimization rules:

• Maximum 150 characters -- but Google typically displays only 70 characters in Shopping results. Front-load the most important information.
• Include the exact words people search for -- "shower drain" not "drainage solution", "walk-in shower tray" not "shower receptor". Use Google's autocomplete and Search Console data to find real search terms.
• Include dimensions and sizes -- shoppers search for specific measurements. "800mm" and "80cm" are different queries; include both if space allows.
• No promotional text -- "Best Price", "Free Shipping", "Sale" are prohibited in titles and will get your product disapproved.
• No ALL CAPS -- Google will disapprove products with excessive capitalization. Use title case or sentence case.
• Don't stuff keywords -- "Shower Drain Drain Shower Floor Drain Linear Drain" will get flagged. Each word should add unique information.

PrestaShop-specific tip: Your PrestaShop product name is typically what gets exported as the feed title. But your product name is also what customers see on your website and is often written for humans, not for Google Shopping. The best approach is to use a feed generation module that lets you build titles from a template using product attributes -- combining the product name with attributes like size, color, and material automatically.

Product Descriptions: Your Hidden Keyword Opportunity

While titles are the primary matching signal, Google also uses descriptions to understand what your product is and match it to long-tail queries. Most PrestaShop stores export their product description as-is, which is often either too short (a single sentence) or too long (the entire product page content with HTML).

Description optimization rules:

• 500-1000 characters is the sweet spot -- enough for Google to extract keyword signals, short enough to be focused.
• Lead with the most important product attributes -- material, size, use case, compatibility. Think about what someone would type into Google to find this exact product.
• Include synonyms and related terms -- if your title says "shower drain", your description should also mention "floor drain", "channel drain", "linear drain", "drainage system". This captures queries you can't fit in the title.
• Plain text only -- strip all HTML tags. Google's feed specification requires plain text descriptions. Most PrestaShop feed modules handle this automatically, but verify.
• No promotional language -- same rules as titles. No "best", "cheapest", "free shipping", or calls to action.

PrestaShop-specific tip: PrestaShop has both a "Short description" and a "Description" field. For the Merchant Center feed, the short description is often the better choice because it is typically more concise and doesn't contain HTML-heavy formatted content. If your short descriptions are empty or too brief, this is the first thing to fix -- write a proper 2-3 sentence description for every product that includes key attributes and common search terms.

Google Product Category: Be Specific

Google maintains a taxonomy of over 6,000 product categories. Your feed must include a google_product_category for each product, and the more specific you are, the better Google understands and matches your products.

Common mistake: Selecting a broad parent category like "Home & Garden" (ID: 536) instead of the specific category "Home & Garden > Bathroom Accessories > Shower Drains" (ID: 7220). Google uses your category selection to understand the product type and apply the correct attribute requirements.

Rules:

• Always use the most specific subcategory available in Google's taxonomy.
• Use the numerical category ID, not the text path -- IDs are language-independent and less error-prone.
• You can also include a product_type attribute with your own category hierarchy from PrestaShop. This is not the same as google_product_category and serves as additional classification data. Use your PrestaShop category breadcrumb: "Bathroom > Shower Accessories > Linear Drains".

Product Identifiers: GTIN, Brand, and MPN

Google requires unique product identifiers to match your products to its global product database. For most products, this means providing at least two of the three identifiers:

• GTIN (Global Trade Item Number) -- this is the EAN-13 barcode number in Europe, UPC in the US. In PrestaShop, this maps to the "EAN-13 or JAN barcode" field on the product page.
• Brand -- the manufacturer or brand name. In PrestaShop, this maps to the "Brand" (formerly "Manufacturer") field.
• MPN (Manufacturer Part Number) -- the manufacturer's own product reference. In PrestaShop, this maps to the "Reference" field.

Critical rules:

• If your product has a GTIN, you must provide it. Google will eventually disapprove products where a GTIN exists but is not provided.
• The GTIN must be valid -- Google validates the check digit. A random 13-digit number will be rejected.
• For custom or handmade products without a GTIN, set identifier_exists to false. This tells Google the product is legitimate but unique.
• Never use the same GTIN for different products or variants -- each unique product (size, color, configuration) should have its own GTIN.

PrestaShop-specific tip: PrestaShop stores EAN-13 at both the product level and the combination (variant) level. Make sure your feed module exports the combination-level EAN for products with variants (sizes, colors), not just the parent product EAN. A common issue: all color variants of a product export with the same EAN, which Google will flag as an error.

Product Images: The Visual First Impression

Google Shopping is fundamentally a visual experience. Shoppers scan product images before reading titles or prices. Your images directly impact click-through rates, and Google has strict image requirements that can lead to disapprovals.

Image requirements:

• Minimum resolution: 100x100 pixels for most products, 250x250 for apparel. But aim for at least 800x800 -- higher resolution images look better in Shopping results and are required for the image zoom feature.
• Main image must show the product on a white or light background -- no watermarks, no promotional overlays, no logos, no text on the image.
• The product must fill 75-90% of the image frame -- no excessive white space, no tiny product in a large frame.
• No placeholder images -- generic "image not available" placeholders will get your product disapproved immediately.
• Supported formats: JPEG, PNG, GIF, BMP, TIFF, WebP. JPEG is recommended for photographs.
• Maximum file size: 16 MB per image.

Image optimization tips:

• Use the highest quality image available -- do not downscale for the feed. Google handles resizing on its end.
• Use the additional_image_link attribute to include up to 10 additional images per product. Include lifestyle shots, close-ups, different angles, and installation photos. Multiple images improve engagement.
• Image URLs must be stable -- changing image URLs forces Google to re-crawl and re-process. Use consistent, permanent URLs.

PrestaShop-specific tip: PrestaShop generates multiple image sizes (small, medium, large, etc.) from your uploaded originals. For the Merchant Center feed, always export the largest available image size or the original. Never use thumbnail-sized images -- they will be too small and may get disapproved. Check your image type settings in PrestaShop's back office under Design > Image Settings to ensure your largest format is at least 800px.

Price and Availability: Accuracy Is Non-Negotiable

Google crawls your product pages and compares the price and availability shown on your website against the data in your feed. Any mismatch leads to product disapproval. This is one of the most common reasons for Shopping feed issues.

Rules:

• The price in your feed must exactly match the price on your landing page -- including tax treatment. In the EU, prices are typically shown including VAT on the product page and in the feed. In the US, prices are typically shown excluding tax.
• Currency must match your target country. If you sell to Germany, the price must be in EUR.
• Availability must be accurate -- if a product is out of stock on your website, the feed must show out_of_stock. Google crawls your pages and will disapprove products where the feed says "in stock" but the page shows "out of stock".
• Sale prices must use the dedicated sale_price and sale_price_effective_date attributes, not simply changing the price attribute. This allows Google to show strike-through pricing in Shopping results.

PrestaShop-specific tip: If you use PrestaShop's "Specific Price" feature for sales, ensure your feed module exports these as sale_price with the proper date range, not as the regular price. Also watch out for customer-group-specific pricing -- your feed should export the price visible to non-logged-in visitors (the public price), not a wholesale or VIP price.

Shipping Configuration: Set It Up Properly

Google Shopping listings show shipping costs to shoppers. This information can come from your feed (product-level) or from your Merchant Center account settings (account-level). Getting this wrong leads to either disapprovals or misleading pricing that hurts conversion rates.

Two approaches:

• Account-level shipping (recommended for most stores) -- configure your shipping rates, carriers, and delivery times in Merchant Center under Settings > Shipping and Returns. This applies to all products unless overridden. Best for stores with uniform shipping rules.
• Product-level shipping -- include the shipping attribute in your feed for each product. Use this when different products have different shipping costs (e.g., oversized items, free shipping thresholds).

For EU stores, you must provide shipping information for each country you target. If you sell to DE, FR, and NL, you need shipping rates configured for all three countries.

Delivery time is increasingly important -- Google shows estimated delivery dates in Shopping results, and faster delivery improves your ranking. Include min_handling_time, max_handling_time, min_transit_time, and max_transit_time in your feed or configure them at account level.

Free shipping: If you offer free shipping (universally or above a threshold), make sure it is reflected in your feed or Merchant Center settings. "Free shipping" badges in Shopping results significantly improve click-through rates.

Custom Labels: Segment for Smart Campaign Management

Google Merchant Center supports five custom label fields (custom_label_0 through custom_label_4) that you can use to segment your products for campaign management. These labels don't affect how Google matches your products to searches -- they are purely for your own organizational use in Google Ads.

Recommended custom label strategy:

• Custom Label 0: Margin tier -- "high_margin", "medium_margin", "low_margin". This lets you create separate Performance Max campaigns or ad groups with different ROAS targets based on profitability.
• Custom Label 1: Seasonality -- "spring", "summer", "evergreen", "christmas". Increase budgets for seasonal products during their peak period and reduce them off-season.
• Custom Label 2: Performance category -- "best_seller", "new_arrival", "slow_mover", "clearance". Best sellers get higher bids; clearance items get aggressive pricing.
• Custom Label 3: Price range -- "under_50", "50_to_200", "200_plus". Different price points often have different conversion patterns and ROAS expectations.
• Custom Label 4: Product type grouping -- your own categorization that may differ from Google's taxonomy. "drains", "enclosures", "accessories".

PrestaShop-specific tip: Custom labels must be populated by your feed generation module. Most modules let you map custom labels to PrestaShop attributes, features, categories, or even custom SQL queries. If your module doesn't support custom labels, consider a module that does -- the ability to segment your Shopping campaigns by margin or performance tier is worth the investment.

Supplemental Feeds: Fix Data Without Changing Your Store

A supplemental feed is a secondary data source that enriches or overrides data from your primary feed. You upload it to Merchant Center and link it to your primary feed using the product ID as the key.

Use cases:

• Overriding titles -- your PrestaShop product names are written for on-site shoppers, but you want different (more keyword-rich) titles for Shopping. A supplemental feed with just id and title columns lets you override titles without touching your store.
• Adding custom labels -- if your feed module doesn't support custom labels, create a spreadsheet with product IDs and label values, upload it as a supplemental feed.
• Fixing GTINs in bulk -- if you have EAN/GTIN data in a spreadsheet from your supplier but haven't imported it into PrestaShop yet, a supplemental feed gets it to Merchant Center immediately.
• Adding promotion IDs -- link products to Google Merchant Promotions without modifying your primary feed.

Supplemental feeds can be Google Sheets (auto-updated), scheduled file fetches, or manual uploads. Google Sheets is the easiest option for small catalogs that need manual adjustments.

Feed Rules: Transform Data Inside Merchant Center

Merchant Center has a built-in "Feed Rules" feature (under Products > Feeds > your feed > Feed Rules) that lets you transform and modify feed data without changing the source. This is powerful for PrestaShop stores where modifying the feed export module is not practical.

Useful feed rules:

• Append brand to title -- if your PrestaShop product names don't include the brand, create a rule that appends the brand attribute to the title.
• Map PrestaShop categories to Google categories -- create rules that map your product type values to google_product_category IDs based on pattern matching.
• Set availability based on price -- automatically set products with price 0 to "out_of_stock".
• Extract attributes from titles -- if your product titles contain color or size information, create extraction rules to populate the color and size attributes.
• Standardize values -- if your color attribute has "SS", "Stainless", and "Stainless Steel" as values, create a rule to normalize them all to "Stainless Steel".

Feed rules are processed in order after your feed is uploaded. They are stored in Merchant Center, not in your PrestaShop store, so they persist across feed updates. This makes them ideal for quick fixes while you work on a proper solution in your store.

Common Disapproval Reasons and How to Fix Them

Product disapprovals are the most frustrating part of Merchant Center management. Here are the most common reasons and their fixes:

1. Price mismatch

The price in your feed doesn't match the price on your landing page. Fix: Ensure your feed updates frequently (at least daily) and that your feed module reads the current active price including any specific prices or cart rules. Check your tax configuration -- if your landing page shows prices with VAT but your feed sends prices without VAT (or vice versa), Google sees a mismatch.

2. Availability mismatch

Your feed says "in_stock" but the product page shows out of stock or has no add-to-cart button. Fix: Update your feed more frequently, or implement real-time availability updates via the Content API for Shopping.

3. Missing required attributes

Certain product categories require specific attributes. Apparel requires gender, age_group, color, and size. Fix: Check Google's attribute requirements for your product category and ensure your feed includes all mandatory fields.

4. Image quality issues

Promotional text on images, watermarks, too-small images, or placeholder images. Fix: Use clean product photography without overlays. Ensure image dimensions meet the minimum requirements.

5. GTIN issues

Invalid GTIN (fails check digit validation), incorrect GTIN (doesn't match the product), or missing GTIN for products that should have one. Fix: Validate all GTINs using a check digit calculator. Contact your supplier for correct EAN/UPC codes.

6. Misleading or promotional title/description

"Best price", "Free shipping", or excessive capitalization in titles or descriptions. Fix: Remove all promotional language. Use sale_price for discounts and shipping attributes for shipping information.

7. Landing page issues

The landing page URL in your feed returns a 404, redirects to a different product, or requires login to view. Fix: Ensure all product URLs are valid, accessible without login, and point to the correct product. Disable URL redirects for discontinued products.

Merchant Center Verification: What Happens Before You Can Advertise

Before your products can appear in Google Shopping results, your Merchant Center account must pass Google's verification process. This is something many store owners don't expect, and it can delay your Shopping campaigns by days or even weeks.

What Google verifies:

• Website ownership -- you must prove you own the domain by adding a meta tag, uploading an HTML file, or verifying through Google Search Console.
• Business information accuracy -- your business name, address, and contact information must be visible and consistent across your website and Merchant Center account.
• Checkout process -- Google will actually attempt to place a test order on your store. They verify that prices match, shipping costs are clear, the checkout process works, and refund/return policies are accessible. If your checkout is broken, requires unusual steps, or shows different prices than your feed, verification will fail.
• Policy compliance -- your website must have visible privacy policy, return/refund policy, and terms of service pages. These must be accessible from the checkout flow.
• Product data accuracy -- Google crawls your product pages and compares them against your feed data. Significant mismatches in price, availability, or product information will block approval.

This verification process typically takes 3-7 business days but can take longer if issues are found. During this period, your products are in a "pending" state and cannot serve ads. This is why it is critical to have your website, policies, and feed data properly configured before submitting for review -- every failed verification attempt adds days to your timeline.

Tip: While waiting for Merchant Center approval, you can immediately start running Google Search text ads to drive traffic to your store. Search campaigns don't require Merchant Center approval and can be live within hours. This is particularly valuable for new stores that need revenue while their Shopping feed is being verified. See our guide on Google Search Ads for E-Commerce for details.

Feed Update Frequency: How Often Should You Refresh?

Google requires that your feed data be refreshed at least every 30 days, or products expire. But for active stores, daily or more frequent updates are strongly recommended.

• Daily scheduled fetch -- configure Merchant Center to fetch your feed URL once daily. Suitable for stores where prices and stock change infrequently.
• Multiple daily fetches -- if your stock levels change throughout the day (high-volume stores), schedule 2-4 fetches per day.
• Content API for Shopping -- for real-time updates, use Google's API to push product changes immediately when they happen in PrestaShop. This is the most accurate method but requires development.
• Automatic feed delivery -- some PrestaShop feed modules support pushing the feed to Merchant Center via SFTP or the API on a schedule you control.

The faster your feed reflects reality, the fewer disapprovals you get and the more accurately Google can serve your products. For stores with frequent price changes or limited stock, hourly updates via the Content API are worth the implementation cost.

Free Listings: Your Products on Google Without Paying

Google Merchant Center is not just for paid Shopping ads. Once your feed is approved, your products are automatically eligible for free listings across Google surfaces -- the Shopping tab, Google Search (organic product results), Google Images, and Google Lens.

Free listings use the same product feed as paid campaigns, so every optimization you make for Shopping ads also improves your free listing visibility. The key differences:

• Free listings are organic -- you don't pay per click
• They appear in the Shopping tab, Search, Images, and Lens
• Ranking is based on relevance and product data quality, not bids
• Products must meet the same data quality standards as paid listings

For many PrestaShop stores, free listings generate meaningful traffic at zero cost. The better your feed quality, the more visibility you get in these free placements.

Structured Data Markup: Reinforce Your Feed

Product schema markup (JSON-LD) on your product pages is not a substitute for a Merchant Center feed, but it serves two purposes: it helps Google verify that your feed data matches your landing page (reducing disapprovals), and it enables rich product results in organic search.

At minimum, your PrestaShop product pages should include:

• @type: Product with name, image, description, sku, gtin13, and brand
• An Offer object with price, priceCurrency, availability, and url
• AggregateRating if you have product reviews

Many PrestaShop themes include basic product schema out of the box, but it is often incomplete (missing GTIN, missing availability, wrong price format). Verify your structured data using Google's Rich Results Test tool and fix any issues.

Multi-Language and Multi-Country Feeds

If your PrestaShop store sells in multiple countries or languages (common in the EU), you need separate feeds or feed targets for each country/language combination.

Setup options:

• Separate feeds per country -- generate a separate XML feed for each target country with the correct language, currency, and shipping information. This is the cleanest approach.
• Single feed with multiple targets -- upload one feed and configure multiple target countries in Merchant Center. Works only if prices and language are the same across targets.
• Feed rules for localization -- use feed rules to transform a single feed for different countries (currency conversion, language translation).

PrestaShop-specific tip: PrestaShop's multi-language architecture makes it straightforward to generate per-language feeds. Ensure your feed module respects the language context and exports titles, descriptions, and URLs in the correct language for each feed. Don't export German product titles in a feed targeting France.

Feed Quality Score: Measure and Improve

Google provides diagnostic reports in Merchant Center that show the health of your feed. Monitor these regularly:

• Diagnostics page -- shows all active issues, warnings, and disapprovals with affected product counts.
• Product data quality -- indicates how complete your product data is and where gaps exist.
• Price competitiveness report -- shows how your prices compare to competitors for the same products (requires sufficient data volume).
• Best sellers report -- shows which products in your category are trending, helping you prioritize which products to optimize first.

Aim for:

• Zero disapprovals and zero warnings
• 100% of products with GTIN/brand identifiers
• 100% of products with images that meet the resolution requirements
• All product descriptions populated (no blank descriptions)
• Custom labels assigned to enable campaign segmentation

Using Standard Shopping Campaigns to Unlock Search Term Insights

One of the biggest frustrations with Performance Max campaigns is that you cannot see what people searched for before clicking your product ads. PMax provides only aggregated "search themes" in its Insights tab -- not individual search queries. This makes it nearly impossible to identify wasted spend or discover new keyword opportunities directly from PMax data.

There is a practical workaround: run a standard Shopping campaign alongside your Performance Max campaign. Standard Shopping campaigns provide full search term reports showing every query that triggered your product listings, the cost per click, and whether it converted. This gives you the granular keyword data that PMax hides.

How to set this up:

• Create a standard Shopping campaign targeting the same product feed
• Set a lower priority than your PMax campaign (PMax takes precedence for the same products, but standard Shopping will pick up queries PMax doesn't cover)
• Alternatively, split your catalog: run your best-sellers in PMax and your long-tail or test products in standard Shopping to get search term data
• Review the search terms report weekly -- look for high-spend, zero-conversion queries to add as negative keywords

Negative keywords from these insights can be applied in two ways:

• Account-level negative keywords -- added through Google Ads interface, these apply to ALL campaigns including Performance Max. Use this for broadly irrelevant terms.
• Campaign-level negative keywords -- for standard Shopping campaigns, you can add these directly. For Performance Max campaigns, you must contact Google Ads support (approximately 1 business day turnaround). Use the search term data from your standard Shopping campaign to build targeted negative keyword lists for PMax.

This combination -- PMax for automated reach and standard Shopping for search term intelligence -- is the most effective way to run Google Shopping in 2026. Your feed quality determines performance in both campaign types, but the standard Shopping data gives you the insights to continuously improve your feed titles, descriptions, and negative keyword lists.

For a detailed guide on Performance Max campaigns, audience signals, bidding strategies, and the products-only Smart Shopping trick, see our companion article: Performance Max for PrestaShop: The Complete Guide.

The Bottom Line

Your Google Merchant Center feed is not a technical requirement to check off a list -- it is the most powerful lever you have for Google Shopping performance. Every improvement you make to your product data compounds across both paid Shopping campaigns and free listings, affecting which queries trigger your products, how they appear, and how they perform against competitors.

Start with titles. Then fix images. Then add proper identifiers. Then implement custom labels for campaign segmentation. Each step incrementally improves your feed quality and, with it, your Shopping campaign results. The stores that invest in feed quality consistently outperform those that throw money at bids and budgets while ignoring the data foundation.