Merchant Center Disapprovals and Suspensions: A Fix List for Salla and Zid Stores

A Google Merchant Center disapproval means one product's data doesn't match what Google sees on its page, or breaks a specific policy, so you fix the feed or the page. A suspension stops every product, and the fix usually starts on the store's own pages, not in the feed. Treat them as two different problems with two different routes.

Policy and interface details here are current as of October 2026. Salla and Zid, mentioned throughout, are the two main hosted e-commerce platforms in Saudi Arabia. This article belongs to the store growth map: what to fix before raising ad spend.

Product disapproval or account suspension: why the difference matters

A disapproval sits on a product or a group of products; a suspension covers every product in the account for the target country. Mixing them up costs at least a week, because each review takes days and a review requested in the wrong place fixes nothing.

	Product disapproval	Account suspension
Where it shows	Needs attention tab, next to the product	Banner at the top of the account and under "View setup and policy issues"
Scope	One product or a set	All products in the country
Typical cause	Price or availability mismatch, broken landing page, missing data	Misrepresentation, or attempts to bypass review
Fix	Correct the product data or page, then request a website check	Correct store pages, business data and feed, then request an account review
Timing Google publishes	Up to 7 business days	Wait 7 business days
Identity verification	Needed when the review button is inactive	Often required before the review

My working rule: if a handful of products are disapproved, the problem is data. If a banner sits on the account, the problem is trust in the store itself.

What causes product disapprovals, and how do you read the diagnostics?

Open the Needs attention tab, sort issues by the number of affected products, and start with the one that covers the most. Each issue names the attribute involved. The fix happens at the source, in the store or the feed, not in Merchant Center alone.

Price mismatch. Googlebot visits the product page and compares its price with the price in your product data or the page's structured data, and it expects an exact match. Google lists the usual causes: the feed updating later than the site, faulty structured data, wrong sale-price dates or time zones, and prices loaded by JavaScript. It also warns that mismatches can lead to account suspension. In Saudi Arabia this peaks around sales seasons: a White Friday or Founding Day sale starts at midnight Riyadh time while the feed carries dates in another time zone, or refreshes hours later.

Landing pages that don't work properly. Google wants ads to lead to useful, usable pages and rules out sites that are under construction, broken, or that disable the browser's back button.

Product identifiers. Salla's help centre has an article on adding MPN and GTIN to improve product visibility in search, and Google recommends GTIN in product-page structured data. A branded product with a barcode that never gets sent is harder for Google to match.

Unrealistic claims. Titles or descriptions such as "permanent cure" or "guaranteed results from the first use" fall under unreliable claims in the misrepresentation policy. It is common in beauty and supplement stores.

Misrepresentation: what does Google look for in your store?

The misrepresentation policy asks that listings be clear and honest and give shoppers what they need to decide. Google says it may review your listings, website, accounts and third-party sources. In practice the review reads your store the way a careful customer would, not just the feed.

Google splits violations into two tiers:

• Egregious, suspended on detection without warning: a false identity, business name or contact details; hiding your real location or where orders ship from; not showing the full price with taxes and fees; hidden shipping costs; refusing returns your stated policy allows; impersonating a brand.
• Warned at least 7 days before suspension: offers users can't actually get, unreliable claims, and media manipulated to mislead. Warning emails usually give you 7 or 28 days to fix the issue.

What does that look like in a Saudi or Jordanian store? A cash-on-delivery fee that appears only at the last step. Shipping to outlying cities revealed only after the address is typed. "Delivered in 24 hours" on every product when delivery takes a week. Items shipped from abroad presented as if they sat in a local warehouse. A return window counted from the order date; Google's own example of a violation is an international return window that starts at purchase rather than delivery.

Hypothetical example, rounded numbers: a product is priced at SAR 120 in the feed and on its page. At checkout the store adds SAR 18 for cash on delivery and SAR 22 for shipping, neither shown before the final step, so the customer pays SAR 160. The feed price matches the page, so the product isn't disapproved for price, but the full cost was never shown before purchase, which the policy treats as dishonest pricing. The fix: state shipping and cash-on-delivery fees on the shipping page and the product page, and enter them in Merchant Center's shipping settings.

The store-trust checklist before you request a review

This checklist maps each line of Google's guidelines and misrepresentation policy to the place you change in your store, and to the evidence you keep. Don't request an account review until all ten pass.

#	Check	What Google asks	Where to fix it	Evidence to keep
1	Contact	Clear contact details: a form, email, phone, or a business social profile	Footer on every page and a Contact page: a WhatsApp number that answers, an email on the store's domain	Dated screenshot
2	Identity	No false name or contact details; no hidden business location	One store name across Merchant Center, the footer and invoices; the real city of operation	Commercial registration or other proof of the business
3	Payment	At least one conventional method; payment on delivery is one of Google's examples	Checkout lists mada, cards and cash on delivery exactly as offered	Screenshot of the payment step
4	Full cost	Total price with taxes and fees visible before purchase	Cash-on-delivery and any other fees shown before the final step	Screenshot of a cart with every fee
5	Shipping and delivery	All shipping costs, delivery times and delays, and the true ship-from location	Shipping page: cost by city, realistic times, origin if shipped from abroad	Courier rate card
6	Returns and refunds	An easy-to-find policy: what the customer does, when returns are accepted, the window, when money arrives; required even if you take no returns	Return policy page linked from the footer and the product page	Dated copy of the policy
7	Checkout	Users can add to cart and complete purchase; payment data collected over SSL	A full test order from a phone, in a browser without your admin session	Invoice of the test order
8	Product claims	No improbable or exaggerated results	Product titles, descriptions and images	List of phrases removed
9	Availability	Don't list what you can't deliver	Store stock matches the feed; sold-out items show as sold out	Stock report on the day of the request
10	Language	Supported language, one feed per language, linking to pages in that language	Arabic feed to Arabic pages, English feed to English pages	Data source settings

Keep the evidence in one folder dated today. If you later dispute the decision, that folder is what you attach.

The product feed: price, availability, language and identifiers

The product feed is the file or link that carries your product data to Google, and any gap between it and the product page surfaces as a disapproval. Four things I check before anything else:

1. Price and currency. The same price in the feed and in the page text, in riyals for Saudi Arabia, refreshed on a schedule or by integration rather than by hand. Sale prices carry correct start and end dates.
2. Availability. An item out of stock in the warehouse is out of stock in the feed the same day, not a week later.
3. Language. Google wants a separate feed per language, each linking to pages in that language. An Arabic and English store needs two data sources.
4. Identifiers. GTIN and MPN where they exist, and the product's real brand.

On Zid, the help centre (updated September 2026) explains that Product Catalog, under Online Store then SEO, generates a product data link for platforms including Google, Snapchat and TikTok, with a chosen language and currency. On Salla, check the Merchant Center article in its help centre for the current steps. Either way the link carries your store as it is: if the page hides fees or shows the wrong availability, the feed carries the same problem.

Requesting a review: when to ask and what to submit

Request the review after you have fixed everything, not only the item named in the email. Google says an account review covers website transparency, business data consistency and feed accuracy together.

1. Fix all ten checks above and keep the evidence.
2. Complete identity verification if asked, and make sure the data source holds at least one product; some review buttons stay inactive otherwise.
3. Pick the right path. "I fixed the issue" if you fixed it; "I disagree with the issue" if you believe the finding is wrong. Google says you may get only one chance to disagree.
4. When you disagree, give a specific reason and attach proof: commercial registration, supplier invoices for branded products, screenshots of the corrected pages.
5. Wait for the result, 7 business days, before any new request.

Mind the cool-down. If issues aren't resolved by the second attempt, a one-week cool-down may begin, it may lengthen with each unsuccessful review after that, and Google support cannot shorten it. During a 7- or 28-day warning period you get one courtesy review. So I treat every review request as a limited chance, not a button to try.

Why "guaranteed approval" is a red flag

Approval can't be bought. Google makes the decision, so anyone who guarantees it either doesn't know the policy or plans to get around it, and getting around it is worse than the suspension. Google prohibits manipulating product data or site content to bypass its automated checks and creating new accounts to return after a suspension; it treats both as egregious, with suspension on detection and no warning, and says accounts are reinstated only in compelling circumstances.

What a serious specialist can promise: a list of what will change in your store, the evidence for each change, and a review request at the right moment. Nothing more.

After approval: where the return starts

Once approved, Google says products can show within 24 hours. Then the work that makes money begins: a clean feed refreshed before every season, campaigns built on it, and results read as profit rather than platform-reported sales. I cover campaigns built on the feed in Performance Max for online stores, and making sure the product pages themselves are indexed in technical SEO for online stores.

From my work: At Argan Package in Saudi Arabia, where I was Digital Marketing Manager, Google Merchant Center returned 25% ROI within three months of launch. I report it as recorded, return on investment, not return on ad spend; the details are in the Merchant Center and SEO case study. It is also why my Merchant Center setup takes at least 72 hours: the store-page review comes before the feed goes up.

What to do next

Print the store-trust checklist, open your store on a phone without your admin session, and walk through the ten checks the way a stranger would. If your account is suspended, don't request a review until every check passes. If you want someone to review the store and the feed and prepare the review request with you, that is what I do in Google Merchant Center setup.

Want your team trained on this? Training programs are built on your own store and accounts.