Written and reviewed by Bc. Petr Kučera, MSc., MBA


When Google Merchant Center flags a problem, we recommend first determining its scope. An item disapproval, a warning, a preemptive item disapproval (PID) and an account suspension differ in scope. A product-level issue can affect a single item, while an account-level issue can affect every product you sell. Google explains these levels in its overview of issue scope.
Work through the problem in this order: establish its scope, identify where the data source and website disagree, verify the correction, and only then submit another review request. A price or availability mismatch between the feed and landing pages can trigger PID. That preventive action may also cover other offers Google considers likely to be noncompliant, so the fix may extend beyond the first example shown.
All data and settings in this guide reflect their status as of November 12, 2026.
Google Merchant Center is the current name of the tool where you manage the product data behind Google’s shopping offers. If you remember Merchant Center Next, Google confirmed on October 1, 2024 that the move to the new interface was complete. In July 2026, it announced that the “Next” label would be dropped over the following weeks (naming). What used to be called Feeds now appears as Data sources, and diagnostics sit under Products > Needs attention (navigation). Names and menus can keep changing.
Shopping ads use product data from Merchant Center to match offers. Product campaigns, including product-based Performance Max (PMax), need a Google Ads connection. Linking the accounts establishes that connection; product approval and eligibility are assessed separately.
Standard Shopping remains available. Performance Max replaced Smart Shopping in 2022. When both campaign types promote the same products in the same account, Ad Rank determines which takes precedence. Google announced this principle on October 23, 2024.
| How the data is used | Supported surfaces |
|---|---|
| Standard Shopping | Selected surfaces such as Shopping, Search and Images, plus Search partners where they apply (Shopping campaigns). |
| Performance Max | Shopping, Search, Images, Display, YouTube, Gmail, Demand Gen and other supported surfaces (Shopping campaigns). |
| Free listings | Eligible products can appear in Google Search, Shopping, Images, Lens, YouTube, Maps, Gemini and the product module of a Business Profile (free listings). Whether they do depends on product eligibility and on which surfaces are available in a given country. Czechia is supported with CZK as the currency (supported countries). |
If you want to go further with this campaign type, read our guide to advanced Performance Max management.
Before you begin, have the right access, verifiable business details, a domain you control, a data source, shipping settings and a return policy ready. The setup itself covers creating the account, adding business details, verifying and claiming the website, and adding products. Google also uses your business details to inform shoppers (requirements, returns).
| Area | What to have ready |
|---|---|
| Access | Access to Merchant Center and the relevant Google Ads account. |
| Business | Verifiable business and identity details. |
| Website | The ability to verify and claim the domain. |
| Products | A chosen method for supplying product data. |
| Shipping | Prices and conditions that match the online store. |
| Returns | Clearly published return and refund terms. |
Website verification establishes your authority to manage the site. Website claiming connects it to Merchant Center. A claim is exclusive, although advanced account structures allow sharing through specific arrangements.
Google offers several verification methods, depending on what is available to you: your e-commerce platform, email, an HTML verification tag in the page code, an uploaded file, Google Tag Manager or Google Analytics. Not every method is open to every account.
A claim on example.com restricts other accounts from separately claiming merchant.example.com or example.com/merchant. Check both the holder and the level of the claim. A multi-client account (MCA) can support inherited claims and sharing between accounts, so account structure matters when resolving a conflict.
If someone else administers the Google Ads account, you send the link request with that account’s customer ID, and the administrator approves it in Google Ads. If you are an administrator of both accounts, the link is approved automatically (linking accounts).
Before linking, both accounts must be free of account-level policy violations. The connection is to an advertising account; a Google Ads manager account (MCC) cannot be linked. Under Google’s linking conditions, one Merchant Center account can connect to a maximum of 500 Google Ads accounts.
If you need to sort out who can access which account, read our article on managing Google Ads access.
A data source, often still called a feed, delivers information about your offers to Merchant Center. Google supports several methods: adding products automatically from your online store, an e-commerce platform integration, a file, Google Sheets, adding products manually and the Merchant API. The Merchant API is a programmatic interface for connecting your own systems. Each method has its own availability conditions.
Choose your data source together with the account link and a check of price, availability and identifiers against the website (product data specification). Choose the submission method and the update schedule based on how often your catalog actually changes and what your integration can handle.
| Method or situation | What to consider |
|---|---|
| Adding products automatically from your online store | Google reads products from Schema.org structured data. Your website must be verified and claimed (adding from your website). |
| E-commerce platform | A platform integration is one of the supported methods for supplying products (methods overview). |
| File via URL or Google Sheets | Google’s overview of methods states a fetch every 24 hours (overview). The detailed scheduling guide offers daily, weekly or monthly fetches (scheduling). |
| Updates several times a day | Run a manual fetch, upload a new file or use the Merchant API (scheduling). |
| Adding products manually | According to Google’s guide, this option is for accounts that already have offers (manual adding and API). |
| Many data sources or frequent changes | Google strongly recommends the Merchant API. A successful insert response through the API confirms that Google accepted the data for processing (product submission). |
Google requires updates at least every 30 days. Prices and availability must also match the website and checkout. For a changing catalog, the appropriate interval follows those changes; the minimum alone does not ensure current data.
With adding products automatically from your online store, Google creates offers straight from your website. According to Google, it checks the site at least once every 24 hours. If the same product also arrives through an uploaded data source, Google keeps the uploaded version. Crawl errors can lead to an offer found on the site being archived, and Google may restore it once you fix the problem. Local inventory ads (LIA) need an eligible local inventory data source that meets the applicable rules.
Automatic item updates can use the landing page to help address mismatches in existing items. Regular updates to the data source remain a separate responsibility.
When prices or stock change many times a day, the changes can outrun what automatic updates can handle (limitations). Google may still disapprove a product, and with many mismatches it may switch the feature off.
For older integrations, we recommend checking which interface they use and how far their migration has progressed. Build new integrations on Merchant API. It supports programmatic management of accounts, products, inventory, reports, and data sources.
| Milestone | Status |
|---|---|
| Merchant API | Generally available since August 2025 (Merchant Center announcements). |
| Merchant Center for Agencies | Google announced worldwide availability on May 11, 2026 (Merchant Center announcements). |
| Shopping policies | On July 15, 2026, Google announced that its policies would be brought together under Shopping policies in September 2026. According to Google, this involves no substantive changes and no stricter enforcement (Merchant Center announcements). |
| Performance reports | Announced on August 11, 2026, with changes taking effect from August 24, 2026 (Merchant Center announcements). |
| Content API sunset | August 18, 2026 (deprecation and sunset). |
| Requests without an active extension | From September 1, 2026, these requests occasionally fail with HTTP 410 Gone (deprecation and sunset). |
| Full shutdown of Content API for Shopping v2.1 | Google plans it for early 2027, and the schedule may still change (deprecation and sunset). |
An older plugin or Content API integration may stop delivering products even when the file itself is correct. Check the connection against the sunset guidance and Merchant API updates, alongside the product content.
Attribute names and predefined values use English; free-text content follows the data source’s language. The Product data specification adds requirements by product, category, country, and marketing method. The following attributes are a starting reference, with further requirements depending on the offer.
| Attribute | What it does |
|---|---|
id | A stable identifier for the offer, up to 50 characters. |
title | The product name shown to shoppers, up to 150 characters. |
description | The product description, up to 5,000 characters. |
link | The landing page of that specific product. |
image_link | A link to an image that shows the correct product. |
price | The price of the product. |
availability | The product’s availability status. |
The link should lead straight to the product. An interstitial page is acceptable only when the law requires it (specification).
For Czechia, submit prices in CZK, using a decimal point and including applicable value-added tax (VAT). The data source, product page, structured data, and checkout must agree. Czech VAT belongs within the product price; the tax attribute does not add it.
According to the Czech Financial Administration, the standard VAT rate as of January 1, 2026 is 21% and the reduced rate is 12% (Czech tax system). Which rate applies depends on how the supply is classified. Some supplies, such as books that meet the statutory conditions, are exempt with the right to deduct input VAT.
Google supports four availability values: in_stock, out_of_stock, preorder, and backorder. They must agree with the page, checkout, and structured data. Both preorder and backorder also require availability_date, with that date published on the landing page. Use out_of_stock according to actual availability and the Product data specification.
Shipping information is required for Czech Shopping ads and free listings. You can provide it at account level or through the product’s shipping attribute. Correct account settings can cover products without individual shipping values. Keep shipping charges separate from price.
The shipping structure can include country, region or postal code, service, price, handling time, and transit time. Which components are required depends on the configuration and situation.
Google has added two logistics attributes worth knowing (changes). handling_cutoff_time sets the daily cutoff for handling online orders, and minimum_order_value sets the minimum a shopper must spend before you sell and ship. From September 30, 2026, products marked in_store with pickup enabled in the European Economic Area (EEA), the United Kingdom or Switzerland must include the relevant pickup fees and minimum order value, if your website applies them. The requirement covers local inventory ads and free local listings.
When a manufacturer has assigned a GTIN, supply that actual value. The general specification recommends it. For local products, it is required for new products with an assigned GTIN. For free listings, the requirement covers all products with an assigned GTIN.
An EAN-13 submitted in gtin must be the actual 13-digit code for that product. MPN is required when no manufacturer-assigned GTIN exists, with exceptions: it is optional for custom products and products without a clearly assigned MPN.
According to the specification, an incorrect GTIN or MPN leads to disapproval. Incorrectly setting identifier_exists=no, which declares that the identifier does not exist, can also lead to disapproval. We recommend submitting GTINs without spaces or hyphens, even though Google accepts such characters and ignores them (GTIN). Convert ISBN-10 codes to ISBN-13.
The brand attribute is required for new products, with the exception of movies, books and music recordings. If a product has no real brand, do not fill in placeholders such as “N/A” or “Generic”.
Depending on the category and situation, variants may require a shared group identifier in item_group_id, color in color, size in size, GTIN, and images. The specification also makes google_product_category mandatory in specific cases. Check the requirements for the particular product.
A title should make the product and its variant clear, including details such as color or size. Descriptions should provide product information. Google’s specification requires you to leave out promotional messages, text written entirely in capitals, store links in descriptions, sales promotions, and information about competitors.
When a text attribute was written with generative artificial intelligence (AI), Google requires the corresponding structured alternative (specification). For an AI-generated title, use structured_title with digital_source_type=trained_algorithmic_media and place the title itself in content.
The condition attribute is required for used and refurbished products. It remains optional when the goods are new.
Each image must show the correct product and follow the rules on overlays (image requirements). Google accepts JPEG, WebP, PNG, non-animated GIF, BMP and TIFF (specification). Both Googlebot and Googlebot-image must be able to reach the files.
Google has announced a minimum image size of 500 × 500 px. Warnings have been showing since April 14, 2026, and enforcement is planned from January 31, 2027. Google also announced that it will optimize some smaller images.
Images created with generative AI must carry metadata about their origin (specification). One way to do this is the IPTC DigitalSourceType field with the appropriate value. If an image already has AI provenance metadata embedded, keep it.
Our take: The biggest risk in Merchant Center is product data that does not match the website. Price, VAT and availability must agree in the data source, on the product page, in structured data and at checkout. Until they do, there is no point in fine-tuning titles or the campaign. Your feed should be a continuous output of your online store, not a file someone edited by hand once.
We strongly recommend replacing every image smaller than 500 × 500 px now. Do not wait for the planned enforcement date of January 31, 2027. Putting it off only turns the task into a bulk fix under time pressure.
Start in Products > Needs attention. Establish the scope and record the exact message before deciding what to fix.
| Message | What to check |
|---|---|
| Mismatched price / availability | Compare the data source, product page, structured data and checkout (specification). |
| Preemptive item disapproval (PID) | Check the scope of preemptive item disapproval. Google may include other offers it considers likely to violate the requirements. |
| Inaccurate prices (VAT) | Make sure the applicable VAT is included and the final price matches everywhere (VAT). |
| Missing shipping | Confirm that account-level settings or the shipping attribute cover the product (shipping). |
| Misrepresentation | Review your business details, contact information, products, return policy and whether the website works properly (Misrepresentation). |
| Missing identifiers | Check that you use real identifiers and follow the rules of the program in question (identifiers). |
| Image issues | Confirm the image shows the correct product, crawlers can access it and it meets the image rules (images, specification). |
| Online store URL not verified / claimed | Check verification, the claim, who holds it and at what level (website, claim conflicts). |
| CSS not selected | Explicitly select a representative for Free listings in Europe in the correct verified account (CSS). |
| Linked account suspension | If your Merchant Center account is suspended because a linked Google Ads account is suspended, resolve the Google Ads suspension first (announcements). |
Compare the price in four places: the data source, the product page, structured data and checkout. One possible cause is a time lag between updates. Also look for a price entered manually in Merchant Center, because a manual change overrides the value from your data source.
Google’s documentation describes how a product can regain approval after you fix the price and Google crawls the page again, provided the website price matches your data (process). You can request a crawl, or it may happen automatically later.
Check availability along the same path: data source, product page, structured data and checkout. A PID can affect more than one offer, so we recommend reviewing the full scope shown in diagnostics rather than a single example.
Misrepresentation concerns misleading information and the credibility of the store’s presentation. Review the business details, contacts, product information, return terms, website, checkout, and HTTPS against the store requirements.
Contact requirements depend on which Google guide applies to your situation:
| Context | Contact requirements |
|---|---|
| General guide | At least one contact method on the website and a business phone number in Merchant Center (general guide). |
| Google & YouTube on Shopify, when fixing an issue | Legal name, address, phone number and email that match the details in Merchant Center (Shopify). |
| Suspension for Misrepresentation or business transparency issues | Visible and accurate contact details, including your address, phone number and email (suspension). |
Google requires a clear return and refund policy, including information on the cases in which you do not accept returns. You can set return policies by country and mark product exceptions with return_policy_label (settings). Platform settings do not decide your customers’ statutory rights. Those follow the applicable law.
Since September 2026, Google has been consolidating its policies for Shopping ads and free listings under Shopping policies. According to the announcement, some rules still apply only to ads. Prohibited categories include counterfeit goods and specified dangerous products, such as a range of weapons, explosives, recreational drugs, and tobacco products. Healthcare and sexual content restrictions vary by country. Some healthcare offers require prior approval from Google.
The following examples come from individual cases we handled at PPC ONE.
| Situation | What we saw |
|---|---|
| Images | In our analysis of one online store account in February 2026, we assessed images with added cartoon figures as both a way to stand out and a risk of disapproval during Google’s review. |
| Stock levels | In one account, we switched off a Shopping campaign that had stopped delivering results. When we analyzed it, the best-performing product was out of stock. |
| CPC | In one account analysis from February 2026, average cost per click (CPC) rose 54% year over year while the PMax budget grew by only 2.8%, and the campaign brought in significantly fewer users. |
| Access | While analyzing one account we took over, we noticed that Merchant Center access had not been shared with us. |
| Shipping | In May 2026, Merchant Center disapproved the shipping policy page in our account for products displayed in a brick-and-mortar store. |
| Account block | In February 2026, an online store contacted us about a Google Ads block over alleged counterfeit goods. The store said its goods were authentic. |
Fix the cause before submitting a request (process). Choose “I fixed the issue” if you have corrected the problem. Choose “I disagree with the issue” if you believe Google assessed it wrongly. The process can include merchant or identity verification (reviews).
Access to a review may depend on completing merchant verification, and the data source must contain products. During a warning period, one additional account review is available. After an unsuccessful second attempt, a one-week cooldown period may begin.
For most violations, Google first issues a warning and gives you 7 or 28 calendar days to fix the problem. Serious violations may trigger suspension without warning. For unavailable offers and unreliable claims, its Misrepresentation guidance states that warnings last at least seven days. In October 2025, Google clarified existing enforcement with examples involving nondelivery and return or refund processes that do not work.
Keep the repair aligned with the actual problem. Google may treat a substantial catalog reduction before review, followed by a rapid reupload after approval, as circumvention under Abuse of Network. That behavior can lead to account suspension.
Review times depend on which review process you are in:
| Context | Time stated by Google |
|---|---|
| Google & YouTube on Shopify | Usually 3 to 7 business days (Shopify). |
| General guide | Up to two weeks (reviews). |
| Some reviews under the general process | Up to 7 business days (reviews). |
A cooldown period may follow exhausted review attempts and may grow longer after unsuccessful reviews. Support cannot bypass or shorten it under the remediation and review guidance.
Czechia is part of the European Comparison Shopping Services (CSS) program. Shopping ads and free listings in Europe run through a CSS. Google Shopping is one of these services, and a merchant can work with more than one CSS (CSS services).
In the EEA, the United Kingdom and Switzerland, not explicitly selecting a CSS can lead to products being disapproved or the visibility of free listings being limited (CSS selection). Select a representative for Free listings in Europe in the correct verified account. That representative can be Google Shopping or an external CSS.
According to Google, Google Shopping as a CSS deducts a fixed percentage margin from the merchant’s bid before entering the auction. Other CSS providers charge according to their contracts. Google’s provider guidance lists fixed fees, percentage CPC markups, commissions, and combinations. It also identifies country, industry, language, and certain technical services as considerations when choosing a provider.
We recommend assessing auction participation separately from provider fees. Calculate the total cost using the online store’s actual CSS contract.
In this auction, when Google sets the price of the winning click, it excludes a competing bid that another CSS placed for the same merchant (auction).
Google reports that more than 700 CSS groups run ads and that over 600,000 merchants use CSS in the EEA and the United Kingdom. These are Google’s own European figures. They do not provide a benchmark for the Czech market.
We recommend a shared product data foundation with a separate transformation for each platform. Google, Heureka, and Seznam each have their own specifications. Google uses product data to match Shopping offers, so check both eligibility and whether each offer is matched correctly.
In July 2025, Seznam renamed its campaigns on Zboží.cz to Seznam Nákupy (Seznam Blog).
Keep these differences in mind when you prepare each export:
| Area | Heureka | Seznam Nákupy | |
|---|---|---|---|
| Required fields | Depend on the product, its category, the country and how you promote it (Product data specification). | Heureka Help marks PRODUCTNAME, ITEM_ID, URL and PRICE_VAT as required (activation terms). The developer specification adds IMGURL, CATEGORYTEXT, DELIVERY_DATE and DELIVERY, for eight fields in total, inside the SHOP and SHOPITEM wrappers (developer specification). Category requirements also apply. | Six fields inside SHOPITEM: PRODUCTNAME, DESCRIPTION, URL, PRICE_VAT, DELIVERY_DATE and IMGURL. In the relevant categories, EPREL_ID is also required. It identifies the product in the EPREL database (Seznam specification). |
| Title | title can have up to 150 characters (Product data specification). | PRODUCTNAME can have up to 200 characters (Heureka documentation). | Around 70 characters is recommended for PRODUCTNAME, with a maximum of 255 (Seznam specification). |
| Offer identifier | A stable id of up to 50 characters (Product data specification). | ITEM_ID of up to 36 characters, using letters without diacritics, digits, a slash, an underscore or a hyphen (Heureka documentation). | Defined in Seznam’s own specification of the core fields (Seznam specification). |
| Price | price for Czechia uses CZK with a decimal point and the applicable VAT included. Shipping is submitted separately (price). | The final price in CZK, with the correct VAT and any applicable fees. Separately charged postage, delivery and packaging can be left out. PRICE_VAT accepts a dot or a comma with no more than two decimal places. On Marketplace, prices are in whole CZK amounts (Heureka terms and conditions, Heureka feed). | PRICE_VAT is the final positive price in CZK, including VAT and fees (Seznam specification). |
| Availability | Google also accepts out_of_stock (Product data specification). | The main export is meant for goods that are for sale and available (Heureka documentation). | DELIVERY_DATE is an integer representing the period from order to dispatch. Preorders and upcoming products use their release date in YYYY-MM-DD format. The value -1 means availability is unknown (Seznam specification). |
| Category | google_product_category is required only in specific cases (product category). | The developer specification makes CATEGORYTEXT required (developer specification). | CATEGORYTEXT is recommended. A standalone offer needs the full category path from the Zboží.cz category list (Seznam specification). |
| Product identifiers | Real GTINs, according to the rules of the relevant program (GTIN). | EAN for EAN-13 codes and a separate ISBN field for ISBN-10 and ISBN-13 (Heureka documentation, Heureka Help). | Requirements of the relevant categories, as set out in Seznam’s own specification (Seznam specification). |
Heureka also sets its own operational and image requirements:
| Area | Requirement |
|---|---|
| Main XML feed, PPC | Downloaded every two hours (Heureka Help). |
| Main XML feed, FREE | Downloaded every four hours (Heureka Help). |
| Availability feed | Available for PPC only, downloaded every ten minutes (availability feed). |
| Feed size | The main feed can hold at most 500,000 items for sale. Splitting it into several files does not raise the limit (Heureka Help). |
| Image formats | WebP, JPEG, PNG and BMP (Heureka Help). |
| Minimum image size | 20 × 50 or 50 × 20 px and 30 kB (Heureka Help). |
| Recommended image size | At least 175 × 175 px (Heureka Help). |
According to Heureka Help, changing URLs, product names or categories can cause products to become unmatched. The documentation says that matching them again may take roughly four business days.
Return to diagnostics after making changes. Check account status, PID, and individual items separately, then compare the corrected data with the website. For price issues, revisit all four locations: source, product page, structured data, and checkout.
Meet every applicable required and conditionally required attribute in the specification, along with the relevant advertising policies. Add truly optional attributes based on what each product needs.
Moving from Standard Shopping to Performance Max will not fix disapproved products. A product-based Performance Max campaign relies on the same Merchant Center link, so you still have to resolve the disapprovals (Shopping, campaign overlap).
We recommend bringing in a specialist for an account suspension, repeatedly failed reviews, a dispute over a website claim or changes to your integration.
For a broader review of your advertising, read our article on auditing a Google Ads account.
At PPC ONE, we provide Google Ads and Sklik services. We have worked in the field since 2011. Petr Kučera is the founder of PPC ONE.
Verification establishes your authority to manage the website. Claiming connects it to Merchant Center. For a conflict, check who holds the claim, its level, and whether a multi-client account structure is involved.
No. Linking provides the connection a product campaign needs. Products still undergo processing and eligibility checks. A successful insertion confirms that the data was accepted for processing.
Google’s minimum is once every 30 days (minimum), but price and availability also have to stay current. A file can be fetched daily, weekly or monthly (scheduling). If you need updates several times a day, use a manual fetch, a new upload or the Merchant API. Set the interval according to how often your catalog changes.
No. The requirement depends on the program and whether a GTIN has been assigned. For local products, it applies to new products with an assigned GTIN. For free listings, it covers all products with an assigned GTIN. Use the manufacturer’s actual values and check the applicable MPN requirements.
Supply availability_date for both preorder and backorder. The landing page must also display the availability date.
Not yet, as of the date of this article. Google has been issuing warnings since April 14, 2026, and plans to enforce the 500 × 500 px minimum from January 31, 2027 (timeline). Follow the specific message in your account and the published timeline.
For Google & YouTube on Shopify, reviews usually take 3 to 7 business days. The general guide allows up to two weeks and gives up to 7 business days for certain reviews. Merchant verification and a cooldown period may also form part of the process.
No. When Standard Shopping and Performance Max campaigns promote the same products in the same account, Ad Rank decides which ad is shown.
Let’s talk about your online store and your ad campaigns. Send us an inquiry and describe the problem you are trying to solve. You can also include the exact Merchant Center message and the products or accounts affected to help us understand the situation.
Contact us
About the author
Bc. Petr Kučera, MSc., MBA
AI Systems & Marketing Strategist, founder of PPC ONE
Petr discovered the power of performance campaigns back in 2011, and they have been an inseparable part of his professional life ever since. His edge comes from working with more than a hundred companies.
Data verified as of 12/11/2026.