Introduction — the problem in plain terms

Getting product listings rejected by Google Merchant Center is frustrating and costly. For UK CBD merchants in 2026 the usual culprits are image problems, mismatches between your feed and on‑page structured data, inaccessible lab certificates (COAs) and missing or weak age‑verification. This guide walks through the most common causes and gives a clear, practical checklist to get listings approved — and stay approved.

Problem statement

Google will disapprove listings for a range of technical and policy reasons. For CBD products the most common item‑level issues we see are: image overlays or watermarks, too‑small or poor‑quality images, inconsistencies between the product feed and your website’s schema.org structured data, broken or hidden COA links, and absent or ineffective age‑verification. Left unresolved, repeated disapprovals harm account health and can lead to temporary suspension.

Example product types often affected

• Oil tinctures such as Wylde Natural Cold‑Pressed Drops 1000mg CBD Oil 10ml
• Gummies like Wylde CBD Gummy Bears 30x 10mg CBD per bear (Full Spectrum)
• Vapes and e‑liquids such as Blue Cheese Canavape CBD Vape Cartridge and Canavape Blue Dream Complete CBD E‑Liquid 1800mg
• High‑strength tinctures like CBD Living Tincture 30ml 4500mg 0% THC

Common causes

• Image overlays, watermarks or obstructing elements: promotional badges, logos, text overlays or stickers on the primary image will trigger disapproval.
• Image size or quality: Google requires minimum sizes (generally 100×100 px; certain categories like apparel require 250×250 px). Too‑small or low‑resolution images frequently fail.
• Feed vs on‑page inconsistencies: Merchant Center validates feed attributes against your website’s machine‑readable schema.org structured data (JSON‑LD or microdata). Differences in price, availability, identifiers (GTIN/MPN) or title cause item‑level rejections.
• Hidden, blocked or gated COA links: Google and shoppers must be able to access proof of lab testing where permitted — if COA PDFs are behind a login, blocked by robots.txt, or only reachable via javascript popups, the listing can be flagged.
• Insufficient age‑verification: CBD is treated cautiously. Lack of visible age‑restriction at product or checkout level raises policy concerns.
• Unaddressed policy issues and repeated disapprovals: these degrade account health and can escalate to suspension if not corrected.

Step‑by‑step solutions (images, descriptions, COAs, age checks)

1. Fixing images

• Replace any primary image that contains logos, promotional banners, watermarks or obstructing elements with a clean, unobstructed product‑only image on a plain background.
• Ensure the file meets Google’s size and quality requirements (>=100×100 px; use larger for clarity). Save as high‑quality JPG or PNG and keep filenames logical (avoid excessive characters).
• Use the same image URL in your feed and on the product page. If you update the image, update the feed immediately and clear CDN caches where applicable.

2. Correcting descriptions and structured data

• Open Merchant Center → Diagnostics → Item issues (or Needs attention). Note each attribute flagged (price, availability, id, gtin).
• Compare feed attributes to the page’s schema.org JSON‑LD. Use Google’s Rich Results Test or the Structured Data Testing Tool to validate.
• Update either the feed or the on‑page markup so both match exactly (price format, currency, availability values, identifiers). Commonly missed items: sale price, shipping annotations and canonical URLs.

3. Making COA links accessible and transparent

• Host COAs on permanent, crawlable URLs (PDFs or HTML) that do not require a login. Ensure the URL is accessible to Googlebot (check robots.txt).
• Link the COA clearly from the product page — use a visible “Certificate of Analysis” anchor and also include the COA URL in structured data (example: product.customerSupport or additionalProperty pointing to the certificate).
• Where a full COA is not permitted to be displayed, provide a clear summary on the product page and a visible method for buyers to request the full report.

4. Implementing robust age‑verification

• Add an unobtrusive age gate that appears before product pages or at add‑to‑cart for 18+ verification. Use reputable third‑party age‑verification providers to reduce false negatives and show clear intent to comply.
• Ensure the age gate is visible to users but does not hide essential machine‑readable data; allow Googlebot to crawl product pages while keeping purchase flows protected.

5. Resubmission and follow‑up

• Once fixes are live, update your feed immediately (manual upload, scheduled fetch, automated feed or Content API). Using the Content API or automated feed reduces turnaround and recurrence of errors.
• Request a review in Merchant Center. Account and item reviews typically take 24–72 hours after resubmission — plan your inventory and ads accordingly.
• Track the Diagnostics tab; if the same issue reappears, investigate caching, CDN settings or third‑party image processors that might be reintroducing overlays.

Prevention tips — keep your account healthy

• Maintain a single source of truth: automate feed updates from your live product database so feed and on‑page markup remain in sync.
• Keep a public compliance page with contact details, returns, and a brief statement on lab testing and age limits — transparency reduces policy risk.
• Run periodic checks with Google’s Structured Data tools and Merchant Center Diagnostics; automate alerts for new disapprovals.
• Archive and version COAs per batch and make them findable; ensure any external lab link is permanent and GDPR‑compliant.
• Monitor account health closely: repeated item‑level disapprovals can escalate. Treat each flagged issue as high priority.

Conclusion

Disapprovals in Merchant Center are fixable with a methodical approach: clean, unobstructed product images of sufficient size; exact alignment between feed and schema.org structured data; accessible COAs; and properly implemented age‑verification. Use Merchant Center diagnostics, keep automated feeds or the Content API active to reduce delays, and request reviews once fixes are live. Address issues promptly — the sooner you resolve item‑level problems, the less risk to account health and the faster your products will return to visibility.

If you’d like, we can run through a diagnostic checklist for a specific product page — for example, checking image attributes and schema.org JSON‑LD for a Wylde Natural Cold‑Pressed Drops 1000mg CBD Oil 10ml listing — and suggest the exact changes to feed and page markup.