What is probably happening
Merchant Center sees a different truth than the store
Price, availability, currency, shipping, variants or product identifiers can be correct in the back office but different in the feed, landing page or crawler view.
A policy issue is being treated like a campaign issue
Misrepresentation, restricted products, destination quality and account trust problems will not be fixed by bids, budgets or Performance Max restructuring.
The feed source keeps recreating the same error
Manual Merchant Center edits can be overwritten by Shopify, WooCommerce, feed rules, supplemental feeds or scheduled uploads if the upstream source is not corrected.
Approved inventory is still not competitive or eligible enough
A product can be approved and still receive little visibility if identifiers, titles, images, price, shipping, country, language or listing groups are weak.
How to check it without breaking anything
Review Merchant Center diagnostics by item, destination and country.
Compare feed price, availability, shipping, GTIN, MPN, brand, images and landing-page content.
Check Google Ads linking, listing groups, product filters, CSS, country, language and campaign eligibility.
Separate feed data issues from policy, website trust and product competitiveness.
Define the exact symptom and the date when it started.
Compare ad platform, analytics, CRM, ecommerce or backend data before assuming the cause.
Review status, eligibility, policies, budget, bidding, targeting, measurement and recent changes.
Check consent, tags, events, identifiers and deduplication when conversions are involved.
How I would solve it step by step
Separate policy, feed and campaign layers
Start in Merchant Center diagnostics, then verify feed attributes and only after that inspect campaign inclusion, listing groups, bids and budgets.
Compare the live product page with the submitted feed
Open affected examples in incognito/mobile and compare title, price, availability, currency, shipping, images, variants and structured product data.
Fix the source of truth
Correct the ecommerce platform, feed connector, supplemental feed or feed rule so the error does not return after the next synchronization.
Request review only when the root cause is documented
For policy or suspension cases, keep screenshots and change notes, then request review after the account and website are genuinely aligned.
If it gets technical
You can follow this path yourself. If the diagnosis reveals a strange data mismatch, a delicate tracking setup, a risky bidding decision or a blocker that needs account access, Lia keeps this context and brings it to CreatikLab so you do not start from zero.
Take this context to LiaWhat I would not do
Changing budget or bids before understanding the cause.
Confusing missing data with a real absence of sales or leads.
Publishing or scaling a fix from one screenshot.
Ignoring recent changes in the website, CRM, checkout, feeds, consent or tracking.
Frequently asked questions
Can I solve this without help?
Yes, if you can follow the diagnostic sequence and validate each layer with data. If the case mixes tracking, bidding, feeds, CRM or policy, a specialist review is safer.
When should I talk to Lia?
When the symptom does not fit, the data contradicts itself or you need to turn several screenshots and metrics into a clear decision.
Why does this page exist?
This topic combines 2 source(s) or signal(s) already registered in AGOS. The page should help first, then route to Lia if the case needs specific context.
