For a product-feed disapproval, begin with the exact issue, affected product IDs, destination, country, and first-seen time. Determine whether the problem is item-level or account-level, preserve the current evidence, repair the authoritative data or website, and request a review only after the visible product experience and submitted data agree.
Define the scope before editing
In Google Merchant Center, open Products and the Needs attention view. Export or record the issue name, affected item IDs, data source, target country, language, destination, warning or disapproval status, deadline if any, and a few representative URLs. Google explains that this area groups warnings and disapprovals caused by product data, website, policy, or specification problems (Merchant Center issues).
Do not start by changing every product. Compare one affected item with one approved item from the same source. If the issue spans the account, treat it as a broader policy or website investigation rather than a feed-row cleanup.
Identify the authoritative value
For each affected item, write down which system owns title, description, price, sale price, availability, condition, variant, identifier, image, link, shipping, and tax data. The authoritative source might be the commerce platform, an app, a scheduled file, the Merchant API, or a supplemental source. Editing a value directly in Merchant Center can be temporary if the next sync overwrites it.
Record the feed fetch or sync time and the website deployment time. A stale feed, cached landing page, delayed app sync, or scheduled sale boundary can make individually correct systems disagree at the moment Google crawls them.
Compare the complete customer path
Open the exact submitted product link in a clean browser session and select the submitted variant. Compare the product data with the visible landing page, initial HTML or structured data, and checkout for price, currency, availability, condition, and variant. Google requires a consistent product experience and says landing pages should show the same product, price, availability, language, and currency as the submitted data (landing page requirements).
For price issues, compare the submitted `price`, visible product price, structured-data price, and checkout price. Google's price guidance says the amount and currency in product data must match the landing and checkout pages (price attribute). Check whether a member price, sale window, regional price, minimum quantity, or default variant is creating the mismatch.
For availability issues, compare the data source, landing page, structured data, and checkout. Google's availability guidance requires consistency across those locations and calls for an expected date on preorder or backorder offers (availability attribute).
Fix the source, not the symptom
Correct the system that will produce the next feed. Then regenerate or resync the item and confirm the new value appears in Merchant Center. If structured data conflicts with the visible page, update both. If JavaScript supplies critical values late, confirm the initial HTML and rendered result expose the same product information. If a third-party feed app owns the field, change its mapping or contact its support rather than layering an unexplained override.
Keep a short change log with item IDs, old and new values, source system, deployment or sync time, and the person who verified the page. Do not alter identifiers, brands, or policy-sensitive attributes merely to make an error disappear; they must describe the actual product.
Validate a representative sample
Check affected items across different variants, prices, stock states, devices, and countries. Confirm that links return successfully, the intended variant is preselected, the buy action works when the item is in stock, and shipping restrictions are visible. Re-fetch or reprocess the source if the platform provides that control.
Wait for the corrected data to reach Merchant Center before escalating. Some item issues are rechecked automatically after a crawl, while account or policy issues may present a review option.
Request review carefully
Google says a review should be requested after the issue has been identified and resolved, using the available review control for the product or account (review guidance). Before requesting it, confirm that the same problem is not still present on another affected item and save evidence of the corrected page and source. Repeated requests without a real fix can consume review opportunities or encounter a cooldown.
Completion check
Triage is complete when every affected issue has an owner, the authoritative source is corrected, the feed and customer-facing page agree for representative items, synchronization is confirmed, review is requested only where required, and the remaining disapproved count is recorded rather than assumed to be zero.
Sources
- Issues in Merchant Center — Google Merchant Center Help
- About landing page requirements — Google Merchant Center Help
- Price [price] — Google Merchant Center Help
- Availability [availability] — Google Merchant Center Help
- Request a review of your issues — Google Merchant Center Help