The move to Merchant Center Next Generation changed more than the interface. Many stores found their feeds breaking, attributes going missing, or policy flags appearing after migration. Useful Patch audits the specific patterns the new platform introduces.
Google decides approvals and reinstatements. The audit identifies likely causes and gives you a prioritised fix list.
Merchant Center Next Generation is Google's rebuilt platform, replacing the classic Merchant Center interface for most accounts. The migration was largely automatic, but the underlying data model changed in ways that affect feeds, policies, and campaign eligibility.
| Area | Classic Merchant Center | MC Next Generation | Risk |
|---|---|---|---|
| Feed management | Primary feed plus supplemental feeds, manually managed | Data sources with automatic update schedules; some feed types deprecated | Changed behaviour |
| Shipping settings | Shipping tables in Merchant Center settings | Shipping settings moved; some configurations require re-entry after migration | Common breakage |
| Returns policy | Returns policy set per account or per product | Returns policies now linked to Shopping Ads surfaces separately; missing linkage causes disapprovals | Common breakage |
| Product identifiers | GTIN, MPN, brand as optional for some categories | Stricter validation on GTIN format and brand presence for many categories | Stricter enforcement |
| Account structure (MCC) | Sub-accounts visible in classic MCC view | Sub-account migration timing varies; some data visible in one view but not the other during transition | New complication |
| Policy enforcement UI | Issues listed under Diagnostics tab | Policy issues now appear under a different section; some issues only visible to the account owner, not in sub-account view | Visibility gap |
| Automatic item updates | Optional feature for price/availability | Automatic item updates behaviour changed; can override submitted feed data causing mismatches | Common source of mismatch |
These patterns appear repeatedly in accounts that were migrated to MC Next Generation. None of them require the full classic documentation to fix, but each requires identifying the specific failure point first.
After migration, shipping settings that existed in classic Merchant Center sometimes need to be re-linked or recreated in the new interface. Products appear ineligible without a clear policy error in the feed itself.
The new platform separates returns policies by surface (Shopping, Surfaces across Google). A policy that was fine before migration may not carry across correctly, triggering disapprovals on returning-product eligibility.
Automatic item updates can pull price and availability from the product page and override the submitted feed. If the landing page shows a different price (sale price logic, geo pricing, cookie-based prices), this creates a mismatch flag.
MC Next Generation enforces GTIN check digits and format validation more strictly than the classic platform. GTINs that were accepted before migration may now generate warnings or disapprovals at the product level.
When products become ineligible in the new platform, Performance Max campaigns lose those products silently. The campaign continues to serve but coverage drops without an obvious error in Google Ads itself.
For agencies managing sub-accounts, the migration timing varied by account. Some sub-accounts show data in the classic view but not the new interface, and vice versa. This causes confusion about where the live policy issues actually are.
The audit looks at the surface-visible evidence first, then maps which MC Next Generation change is the most likely cause. The goal is a ranked fix list, not a generic checklist.
The audit is a structured diagnostic. You buy the audit, send the intake details (store URL, screenshots of the issues, list of affected products), and Useful Patch produces a ranked report. No generic best practices. No invented fixes. Just a clear diagnosis of the specific patterns visible in your account.
MC Next Generation enforces some policies more strictly and uses different crawl signals than the classic platform. The most common causes are shipping or returns config that did not carry across correctly, GTIN validation that is now stricter, and automatic item updates creating price mismatches. The audit identifies which of these applies to your account.
No. The audit works from screenshots, the issue text shown in your account, and your product URLs. You do not need to grant login access. Sending clear screenshots of the warnings and the affected product pages is usually enough to identify the pattern.
For most accounts, the migration is one-way. Google has been rolling accounts over to MC Next Generation since 2023, and classic Merchant Center access has been removed for most users. The audit covers the new interface and its specific policy and feed behaviours.
No. Google decides approvals and reinstatements. The audit gives you a ranked list of the most likely causes and the clearest fix path. Whether a review request succeeds depends on what you submit and Google's current enforcement stance. Useful Patch does not invent identifiers or fabricate compliance evidence.
Yes. If you manage sub-accounts through a Google Ads manager account, the audit can cover the specific sub-account where the issue is occurring. Send the sub-account name or ID along with the screenshots and affected products. The MCC data gap issue (where data appears in one view but not the other) is something the audit specifically checks for.
The main audit service covering disapprovals, feed errors, misrepresentation, and price mismatch.
If the account itself has been suspended rather than individual products disapproved.
Specific feed validation errors that appear in the diagnostics section.