A product can be competitively priced, genuinely in stock and backed by a strong campaign structure, yet never earn a single Shopping impression. Google Shopping feed errors are often the reason. They are not minor admin notices to clear when someone gets round to them. They determine whether Google can list your products, understand what you sell and match an item to a commercially valuable search.
For established eCommerce brands, the cost is larger than a few disapproved SKUs. A weak feed restricts reach on bestsellers, sends budget towards less profitable variants and makes Performance Max optimisation less reliable. The goal is not a Merchant Centre account with zero alerts at any cost. It is a feed that gives Google accurate, commercially useful product data while protecting margin.
Why Google Shopping feed errors damage profitable growth
Merchant Centre diagnostics can look technical, but every issue falls into one of three commercial problems: products cannot serve, products serve with poor relevance, or the data creates distrust between your website and Google.
A disapproved bestseller is obvious lost revenue. Less obvious is the product that remains approved but has a generic title, missing GTIN or weak category mapping. Google has less confidence in where to place it. That usually means fewer eligible auctions, weaker query matching and a higher cost to generate qualified traffic.
Feed quality also affects how efficiently campaign data accumulates. If 20 variants of a hero product are missing from the feed, your bidding system is learning from an incomplete range. It may push spend into products with easier conversion paths but lower contribution margin. That can make reported ROAS look acceptable while profit stalls.
Not every warning warrants the same urgency. A missing optional attribute on a low-volume accessory is different from a price mismatch across your highest-revenue collection. Treat diagnostics as a prioritised profit task, not a compliance exercise.
The Google Shopping feed errors worth fixing first
Price and availability mismatches
Google compares feed values with the live product page. If the feed says £49.99 but the landing page shows £59.99, or the feed says in stock while the item cannot be purchased, Google may disapprove the product. Repeated discrepancies can escalate into account-level problems.
These errors commonly come from delayed feed schedules, sale prices that have ended, currency settings, regional pricing rules or stock systems that do not update quickly enough. Fixing the feed field alone is not enough. The product page, structured data and submitted feed must all tell the same story.
For brands with volatile inventory, increase update frequency and ensure the feed source handles stock changes reliably. For promotions, use sale price fields with accurate effective dates rather than overwriting the core price and hoping every system refreshes in time.
Missing or incorrect GTINs
GTIN errors are especially damaging for branded products sold by multiple retailers. A valid GTIN helps Google identify the exact item and compare it accurately across the market. Submitting a made-up number, reusing a GTIN across variants or marking identifiers as unavailable when they exist creates avoidable friction.
If you manufacture private-label goods and no GTIN exists, set the identifier exists attribute correctly. Do not invent a barcode to silence a warning. Where official identifiers are available, use the manufacturer-assigned value for each distinct variant. Size, colour and pack quantity can all require their own identifier.
This is not just a compliance point. Clean identifiers support stronger product matching and often improve the quality of traffic for products that compete in crowded categories.
Titles that cannot win the query
A title can be technically accepted and still be commercially poor. “Classic Trainer” or “Hydrating Serum” gives Google very little to work with. It also loses the detail shoppers use to decide whether to click.
The right title format depends on the category. For fashion, brand, product type, key style, colour, gender and size can make sense. For homeware, brand, product type, material, dimensions and key use case may matter more. For consumables, quantity and flavour or formulation are often decisive.
Do not stuff every possible keyword into every title. Overloaded titles reduce clarity and can misrepresent the item. Start with the language customers use when they are ready to buy, then confirm it matches the product page. The best feed titles are specific enough to qualify demand, not broad enough to attract irrelevant clicks.
Invalid category, product type and attribute data
Google product category and product type do different jobs. The Google category uses Google’s taxonomy. Product type is your own taxonomy and should reflect how you organise the range. Both help Google understand the item, particularly where a title alone is ambiguous.
Errors occur when retailers use outdated categories, submit malformed values or force every product into a broad catch-all label. Apparel has further requirements around gender, age group, size and colour. Missing attributes can limit eligibility or create warnings that later become more serious as policy enforcement changes.
Build rules by product group rather than applying one blanket template to the catalogue. A skincare range, a furniture range and a clothing range need different levels of attribute detail. That is slower to set up, but it produces cleaner data and better control over campaign segmentation.
Image problems that weaken approval and click-through rate
Google’s image policies are strict for good reason. Images with promotional text, watermarks, borders or misleading bundles can trigger disapprovals. So can low-resolution files, images that fail to load or pictures that do not clearly show the sold product.
Even approved images can underperform. A poorly cropped main image may lose clicks against a cleaner competitor listing before price or brand consideration enters the decision. Use the primary image to make the product immediately recognisable. Put alternate angles, lifestyle shots and details in additional image fields where appropriate.
Be cautious with lifestyle-led brands. Editorial photography can support the product page, but a clean product-led primary image is usually safer for Shopping visibility and comparison.
Shipping, tax and policy errors
Shipping settings are often ignored until products stop serving. If delivery costs shown in Google do not align with checkout, or shipping is not configured for a target country, the issue can suppress products or create a poor customer experience. The same applies to returns information and destination-specific requirements.
Policy disapprovals need more care than simple data errors. Restricted products, unsupported claims, missing contact details and unclear business information can affect the wider account. Do not repeatedly resubmit unchanged data. Identify the policy trigger, update the site and feed where required, then request review once the issue is genuinely resolved.
A practical triage process for Merchant Centre diagnostics
Start with the account-level status, then move to item-level disapprovals and warnings. Account problems take priority because they can stop the entire catalogue. Next, sort affected products by revenue, margin and campaign spend. The item with 300 impressions a day deserves attention before 50 dormant long-tail SKUs.
Use a simple commercial order of operations:
- Account suspensions, misrepresentation concerns and country-level shipping failures.
- Disapproved products that are proven sellers or form part of a priority collection.
- Price, availability and identifier faults affecting a material share of spend.
- Title, category and image improvements on high-opportunity products.
- Low-impact warnings that are genuinely optional for the category.
Then trace each error back to its source. A Merchant Centre rule may patch a one-off data issue, but it is a poor substitute for fixing the eCommerce platform, product information system or feed app when the same fault will recur. Temporary rules are useful for normalising format or filling stable data. They are risky when they mask live stock, price or variant logic.
After publishing a correction, confirm three things: the feed has processed, the product page reflects the same information and the affected item is approved and eligible in Merchant Centre. Do not assume a successful feed upload means the issue is fixed. Processing delays and website crawls can mean the status changes later.
Build a feed that supports campaign control
The strongest Google Shopping feeds are maintained as operational assets, not exported once and forgotten. Set a weekly check for disapprovals, but monitor price and availability changes more frequently when stock moves fast. Keep custom labels tied to commercial decisions such as margin band, bestseller status, seasonality or clearance risk. Those labels allow you to separate profitable scale from inventory you need to control more tightly.
Feed optimisation also needs restraint. More fields do not automatically mean better performance, and a beautiful title cannot compensate for weak pricing, poor landing pages or an uncompetitive offer. It depends on catalogue size, product complexity, data quality and the level of campaign control your business needs.
At Oxedent, feed work is assessed alongside spend, margin and product-level performance because that is where the real value sits. Clearing a warning is useful. Making sure your most profitable products are eligible, discoverable and correctly prioritised is what turns feed management into growth work.
The next time Merchant Centre reports an error, ask a harder question than “How do we remove this alert?” Ask which products are being held back, what profit is at risk and whether the underlying data process will fail again next week. That is the standard a scaling catalogue requires.