Skip to main content
CyberLab.Team

Sample deliverable

Merchant Center feed diagnostic, attribute by attribute

Most disapprovals are not mysterious. They come from a handful of attributes that disagree with the product page or were never filled in at all. This sample shows how each attribute is reviewed, what the fix is, and who is actually able to make it.

Example, not a client's data

Invented setup: an online store with a catalog of about a thousand products, exported by a platform plugin once a day, selling into two countries. Part of the catalog is disapproved and an account warning has been sitting unread for a while. Every link points at example.com, and no real store or account is involved.

Attribute review

Status is read from the feed and the product page together, because most blocking errors are a disagreement between the two rather than a field left empty.

AttributeStatusExample of the errorFixWho does it
titleBlocking on part of the catalogThe supplier code leads the title and the product type never appearsRebuild the title as type, brand, key attribute, variant, and apply it through a feed ruleUs
descriptionWarningSupplier text repeated across every variant of the same modelWrite it from the product page content and let variants differ where they actually differClient, we specify
linkBlockingThe feed points at a URL that redirects to the current product pageExport the final URL and tie the export to the live URL setClient dev
priceBlockingThe feed carries the price without tax while the page shows it with taxMatch the feed to the page and set the tax configuration for each countryClient, store settings
availabilityBlocking on part of the catalogStock is exported once a day in a store where popular items sell out within hoursShorten the fetch interval, or push availability updates as they happenClient dev, we specify
image linkBlockingThe main image carries a promotional overlay and a watermarkSupply a clean image for the feed and keep the promotional version for the siteClient, we specify
gtin and brandBlockingIdentifiers are missing on items that have them, and the store name is used as the brand on third party goodsFill identifiers from the supplier data and set the manufacturer as the brandClient, we map
identifier existsWarningSet to false across the whole catalog to silence an earlier errorUse it only for products that genuinely have no identifier, such as custom made itemsUs
product type and categoryWarningOne generic category assigned to the entire catalogMap the store taxonomy to the platform category taxonomy and keep product type as your own structureUs
shippingBlocking in one countryNo shipping setting exists for the second country the store sells toConfigure shipping per country, or carry it in the feed where the rules are complexClient, store settings
condition and age groupPassesNothing found on this catalogNo action, rechecked on the next exportUs

One disapproval, step by step

The account showed a policy warning on a group of products. The message named the policy, not the cause, which is the usual starting point.

  • Read the message and take the list of affected items, instead of assuming the problem is catalog wide.
  • Open a few of the affected product pages next to their rows in the feed and compare the fields that policy touches.
  • Find the disagreement: the page showed a discounted price while the feed still carried the previous one, because the export ran before the pricing job.
  • Confirm it is a timing problem and not a currency or tax problem, by checking an item that was never on promotion.
  • Fix the cause: run the export after the pricing job, and align currency and tax settings so the two sources cannot drift apart again.
  • Fix the symptom: refresh the affected items so the current price is in the feed before anything is resubmitted.
  • Request the review with a short note naming the cause and the change, then watch the item level status rather than the account banner.

Checklist before you resubmit

  • The export ran after the last pricing and stock job, not before it.
  • Price, currency and tax in the feed match what a customer sees on the page in that country.
  • Availability in the feed matches the page for a sample of fast moving items.
  • Every link in the feed answers directly, with no redirect in between.
  • Images are clean, large enough, and free of text and watermarks.
  • Identifiers are present wherever they exist, and the identifier flag is used only where they genuinely do not.
  • Shipping and returns are configured for every country the feed targets, and the site states them where a customer can find them.
  • No account warning is left unread, including the ones that do not block products yet.

Where a fix belongs

The same error can be fixed in several places, and the choice decides whether it comes back on the next export.

  • In the store, when the data is wrong at the source. Slower to change, and the only fix that holds.
  • In the feed rules, when the data is right but the format is not: titles, category mapping, a default for a field the store never fills.
  • In a supplemental feed, when a field has to be added for a subset of products and the platform cannot carry it.
  • In the export plugin settings, when the mapping between store fields and feed attributes is simply wrong.
  • Not by hand in the account interface. A manual edit there is overwritten by the next fetch and hides the real problem.

Synthetic example, not a client's data

  • The attribute list here is the common one. A real diagnostic covers the attributes your catalog and your target countries actually require.
  • Statuses are invented. On a real account they come from the item level report, which names the products behind every line.
  • Nothing here is counted. A real diagnostic states how many items each line affects and which ones they are.
  • Whether a review reinstates a group of items is decided by the platform, and no diagnostic can promise that outcome.

A real diagnostic arrives with the item level lists behind each row, the feed rules already written, and a walkthrough of what changed and why. What the audit covers, and what a launch adds, is described on the service page.

Google Ads for E-commerce

Want it handled every month?

Tell us what you run and what it needs. We reply with a plan and a monthly price; month to month, no lock-in.

Discuss a retainer

No commitment. Response within one business day.