How to Check WooCommerce Products Before Google Merchant Center
A WooCommerce catalogue may look complete inside WordPress and still contain information that is unclear, inconsistent or unusable for Google Merchant Center. A product can have an attractive page but lack a reliable price, stock status, identifier or purchasable variation. Another product may contain all required fields while its image, title or description represents a different offer. These problems affect customers as well as the quality of product data submitted to Google.
A useful pre-submission audit examines the stored WooCommerce data, visible product page, variations, cart and checkout. The objective is to describe each real product accurately, use manufacturer-assigned identifiers when they exist and keep the offer recognisable throughout the purchase path.
PW Merchant Check is a free local WordPress and WooCommerce preparation plugin. It can scan common product fields and highlight records that deserve review. It does not connect to a Merchant Center account, submit products, read account diagnostics or guarantee approval. Its findings are preparation signals; the merchant remains responsible for product accuracy and Google’s current requirements.
Why product data quality matters
Google uses submitted attributes to understand what an offer is, who made it, how much it costs, whether it is available and which searches may be relevant. A shopper who clicks a listing expects to see essentially the same item, price, availability, currency and variation on the landing page. If those elements conflict, the experience becomes unreliable and an item may be limited or disapproved.
High-quality data also improves the store itself. Clear titles help customers distinguish similar products. Accurate stock prevents failed orders. Correct variations reduce accidental purchases. Valid identifiers support catalogue matching. Strong images and descriptions answer questions before support is contacted. Merchant Center preparation is therefore part of ordinary e-commerce catalogue management, not a separate task performed only for Google.
Google’s current product data specification defines required, conditionally required and optional attributes. The exact set depends on the destination, target country, category and product. Always compare a general audit with the rules that apply to the store’s real market and inventory.
Start with catalogue scope
Decide which products should be offered through Merchant Center before correcting individual fields. Draft products, internal service items, discontinued records, test products, quotation-only pages and products that cannot be purchased online may not belong in the submitted catalogue. Sending everything creates unnecessary errors and makes quality work harder.
Create practical groups such as active simple products, active variable products, out-of-stock products, backorders, preorders, bundles, multipacks, digital goods and excluded items. Record which countries and languages each group serves. For a Türkiye-based e-commerce site, verify whether the offer is genuinely available throughout Türkiye or only in defined provinces and districts. Do not add İstanbul, Ankara, İzmir, Bursa or other location terms to product copy unless they describe a real delivery or service condition.
Review a representative sample manually before running a bulk audit. Include a high-value item, a discounted item, a variable product, an out-of-stock item and a product with an identifier. This reveals catalogue conventions and helps distinguish a systematic configuration problem from an isolated content error.
Check product status and visibility
An active offer should have a published, publicly accessible product page. Open the URL in a private browser session without an administrator account. Confirm that it does not redirect to the homepage, require a password, show maintenance mode, return a server error or display a generic product list.
The main product must be prominent. The page should display its title, description, image, price, currency, availability and an active purchase control when it is in stock. Google’s guidance on generic or dysfunctional landing pages identifies missing key product elements, obstructive pop-ups, construction pages and redirects for unavailable items as common problems.
Do not automatically redirect an out-of-stock URL to the homepage or a vaguely related item. Keeping the original page with an honest unavailable status may preserve clarity and allow the offer to return later. If a product is permanently removed, handle its catalogue exclusion and website redirect deliberately rather than disguising its status.
Product title
The title should identify the product a customer can buy. Include distinguishing information such as brand, model, product type, important feature, size, colour, capacity or pack quantity when relevant. Put the most useful terms near the beginning, but write for a human reader rather than creating a chain of keywords.
Avoid promotional phrases, repeated capital letters, excessive punctuation, internal stock notes and claims that are not part of the item’s identity. “Free shipping,” “best price,” telephone numbers and campaign messages do not replace descriptive product information. Do not create city variants of the same title merely for GEO visibility.
For variants, the title and selected option should make the advertised item clear. If the offer is a blue 128 GB model, the landing page must not open with a black 64 GB model selected while showing the submitted variant’s price elsewhere. Review naming consistency across parent and variation records.
Product description
A useful description explains what the product is, its purpose, important specifications, materials, dimensions, compatible uses and what is included. It should describe the actual offer instead of copying a manufacturer paragraph that includes options the store does not sell.
Remove empty templates, shortcode fragments, broken HTML, unrelated category text and promises that cannot be supported. Avoid a description made only of search phrases. Relevant terms can appear naturally, but the primary job of the description is to help a person understand the product.
Distinguish the product itself from shipping, warranty and store-wide promotion information. Those details may be valuable on the page, yet they should not obscure the core description. If a product has legal, safety, age or compatibility conditions, communicate them clearly and consistently.
Regular price, sale price and currency
Every purchasable offer needs a valid price in the store currency. Confirm that the regular price is numeric, greater than zero when appropriate and saved on the correct product or variation. A placeholder such as 0, 1 or 99999 used to invite enquiries is not an accurate retail offer.
When a sale price is used, ensure that it is lower than the regular price, active for the intended period and visible on the landing page. Remove expired campaign values. Test scheduled sales at their start and end because cache, timezone and synchronisation delays can leave the website and submitted data showing different prices.
The price, currency and purchasable quantity must be understandable without joining a paid membership or applying a private coupon. If a minimum quantity is mandatory, Google’s specification requires the submitted price to represent the total price of that minimum purchasable quantity and the landing page to show it prominently.
For Türkiye-focused stores, check that WooCommerce, visible pages, structured data and submitted data use the correct ISO currency value even if the customer-facing design displays “TL.” Formatting text does not replace a valid machine-readable currency code. Test tax-inclusive or tax-exclusive presentation according to the target country and ensure unavoidable charges are not hidden until checkout.
Price consistency across the purchase path
Open the product URL as a customer, select the advertised variation, add it to the cart and continue to checkout. Compare the price at every step. Check logged-out visitors, mobile devices, campaign rules and common target locations. A correct value in the WordPress database is not sufficient if a theme, pricing plugin or cache displays something else.
Google’s landing page requirements state that pricing and availability should remain consistent through page load and that the represented product should be essentially identical across relevant user conditions. Avoid changing the offer unexpectedly by IP address, cookie, device or browser.
Review structured product data as well. Schema markup should contain the same price, currency and availability as the visible page. Duplicate schema from a theme and an SEO plugin can expose conflicting values even when the screen looks correct.
Stock status and availability
WooCommerce stock status should reflect what can actually be ordered and delivered. An in-stock offer should have an active Add to cart or Buy button. An out-of-stock offer should not appear immediately purchasable. Backorders and preorders require honest wording and realistic fulfilment dates.
Check the relationship between Manage stock, quantity, backorder settings and status. A product may be marked in stock while its quantity is zero, or a variation may inherit a parent setting that does not match reality. Inventory integrations, ERP imports and cache layers can introduce further delays.
Google’s availability guidance says that availability in product data should match the landing page and checkout. Delivery restrictions such as store pickup only should be visible. Test whether the advertised item can be shipped to the locations represented by the store’s settings.
Main product image
The main image should show the actual product clearly. Use a stable, crawlable URL and a sufficiently large, sharp file. Avoid placeholders, broken links, tiny thumbnails and images that represent a different model, colour or pack quantity.
Do not place promotional text, price labels, shipping claims, watermarks or borders over the primary image for Google listings. Lifestyle imagery can support the product gallery, but the main image should make the item easy to recognise. Variant images should match the selected variant when colour, pattern or another visible feature changes.
Google has announced in its current image link guidance that a minimum size of 500 × 500 pixels for all products will begin on 31 January 2027, while recommending 1500 × 1500 pixels or larger for performance across listing formats. Because requirements can change, verify the official page before a large image migration.
Test direct image URLs without being logged in. Security, hotlink protection, CDN rules, WebP conversion or robots settings must not block legitimate crawling. Confirm that changing a product image also updates caches and any generated product data.
SKU and internal identifiers
A SKU is normally the merchant’s internal stock-keeping code. It helps WooCommerce distinguish records, manage inventory and connect orders to warehouse or accounting systems. Give active products and variations unique, stable SKUs when the operational workflow uses them.
Do not assume that a SKU is automatically a GTIN, EAN or manufacturer part number. The same digits should be copied between fields only when they genuinely represent the same identifier. Duplicate SKUs can cause imports, variation updates and stock synchronisation to affect the wrong record.
PW Merchant Check may flag missing SKU information as a catalogue-management recommendation. Whether an SKU is essential for a particular Merchant Center destination is a separate question from whether it is valuable to the merchant’s own operations.
GTIN, EAN, UPC and ISBN
A Global Trade Item Number is assigned to a specific commercial product. EAN, UPC and ISBN are GTIN structures used in different contexts. When a manufacturer has assigned a valid GTIN, submit that real value for the exact product and variation.
Never invent a barcode, copy one from a similar product or use the same identifier for every variation. Colour, size, capacity or pack changes may have separate manufacturer-assigned identifiers. Validate length and check digit, then compare the code with the packaging, manufacturer or authorised product information.
Google states that GTIN is required for products to which the manufacturer has assigned one. For products without a GTIN, other identifier rules may apply, including brand and MPN. Do not mark an ordinary branded product as lacking identifiers merely because the store has not entered them yet.
Custom, handmade or genuinely unique goods may not have a manufacturer-assigned GTIN. Describe that reality accurately. Purchasing unofficial barcodes simply to fill a field can create identity conflicts and is not a substitute for correct product classification.
Brand and manufacturer part number
Enter the brand that customers and the manufacturer associate with the product. Do not use the shop name as the brand for third-party goods. For an unbranded item, do not invent a brand merely to remove a warning. Private-label products can use the genuine private brand when that is how they are marketed.
The manufacturer part number, or MPN, should be the manufacturer’s real code for that product. It is not normally the WooCommerce post ID and should not be fabricated from the SKU unless the manufacturer genuinely uses the same value.
Google’s product data rules make brand, GTIN and MPN conditionally required according to the product’s identity. Correct combinations help Google recognise an established product. Incorrect combinations may associate the offer with the wrong catalogue record.
Product type and Google product category
WooCommerce categories organise the shop for customers. A merchant-defined product type can reflect that internal hierarchy, while Google product category refers to Google’s taxonomy. These concepts are related but not interchangeable.
Keep WooCommerce categories logical, concise and useful. Remove duplicate category trees created by imports. Map specialised products to the most accurate relevant Google category instead of automatically assigning the same broad category to the entire catalogue.
Google currently assigns product categories automatically, but its category guidance allows merchants to provide an appropriate value where useful. Accurate titles, descriptions, prices, brands and GTINs also help classification. Category mapping cannot compensate for weak core product data.
Variable products
Variable products require a separate review of every purchasable variation. Confirm that each active variation has the correct attributes, price, stock, image, SKU and identifiers. Remove impossible combinations and disable options that cannot be ordered.
Each submitted variant should open a URL or page state that clearly represents and preferably preselects that variant. The visible image, price and availability must update correctly. Test links in a private browser because selections sometimes depend on a cookie from a previous visit.
Use a stable grouping relationship for variations of the same underlying product, but do not group unrelated products merely because they share a category. Apparel commonly requires values such as colour, size, gender and age group depending on market and programme. Other categories may have different requirements.
A common WooCommerce error is a parent product that appears in stock even though no valid variation can be purchased. Another is a default option whose price differs from the submitted variant. Test the complete interaction on desktop and mobile.
Purchase and checkout test
A product is not ready merely because its page loads. Add it to the basket, select delivery and payment, and reach the final order review without completing payment. Confirm that the same item, quantity, variation, base price and expected availability remain visible.
Test mandatory fields, coupon rules, tax calculations, minimum order restrictions and shipping zones. If the product cannot be delivered to the target region, it should not be represented as available there. Avoid unexpected compulsory fees that appear only at the final step.
Repeat this test after changing payment, currency, multilingual or dynamic-pricing plugins. Use a mobile device as well as desktop. Broken variation selectors, sticky overlays and off-screen purchase buttons often appear only at smaller widths.
How PW Merchant Check helps
PW Merchant Check can perform a local review of common WooCommerce product information and organise potential issues by importance. Depending on the product structure, it can draw attention to records with missing or questionable price, purchase status, image, SKU, identifier, brand or variation information.
The controlled scan processes a defined number of products rather than claiming that one instant result represents every possible catalogue condition. The interface can show affected items so the administrator knows where to begin. After corrections, running the audit again provides a practical comparison.
The plugin does not send the store’s product data to Poyraz Web or PW Feed for analysis. It is not developed or endorsed by Google. It cannot determine every category-specific Google requirement, inspect Merchant Center account warnings, validate real-world inventory or know whether an entered GTIN belongs to the physical product. Manual verification remains necessary.
A practical correction order
- Remove test, duplicate and non-purchasable records from submission scope.
- Repair broken product URLs and pages that cannot be accessed publicly.
- Correct price, currency, stock and purchase failures.
- Fix variation selection and parent-child inconsistencies.
- Replace missing, blocked or inaccurate main images.
- Improve titles and descriptions so each offer is identifiable.
- Enter genuine brand, GTIN and MPN values where applicable.
- Review categories and category-specific attributes.
- Align structured data with visible product information.
- Retest cart and checkout, then run the product audit again.
This order prioritises whether a customer can identify and buy the promised item. Cosmetic optimisation comes after core accuracy. Correcting hundreds of titles first is inefficient if checkout or stock synchronisation is fundamentally broken.
Pre-submission product checklist
- The product is published and intended for the target market.
- The URL opens directly without login, error or obstructive overlay.
- The title identifies the exact item and variation.
- The description is factual, useful and product-specific.
- The main image is accurate, crawlable and sufficiently large.
- The visible price, submitted price and structured price agree.
- The currency and tax presentation are correct for the target country.
- The stock status agrees across product page, cart and checkout.
- An available item has a working purchase button.
- Each variation has correct attributes, price, stock and image.
- SKUs are unique where the store uses them.
- GTIN, brand and MPN values are genuine and product-specific.
- Bundles, multipacks and minimum quantities are represented accurately.
- WooCommerce and Google category information is sensible.
- The item can actually be delivered to the represented region.
Frequently asked questions
Does every WooCommerce product need a GTIN?
No. A GTIN should be submitted when one has been assigned by the manufacturer. Genuine custom or unique products may not have one. Do not invent an identifier; apply Google’s current identifier rules to the real product.
Is a WooCommerce SKU the same as a GTIN?
Usually not. An SKU is generally an internal merchant code, while a GTIN is a globally structured product identifier. They may contain the same digits only when that is genuinely how the product is identified.
Can I use my store name as the product brand?
Only when the product genuinely carries that private brand. Do not replace a manufacturer’s brand with the retailer’s name or invent a brand for an unbranded item.
Why does a price mismatch happen even when WooCommerce is correct?
Caching, scheduled sales, tax settings, currency conversion, dynamic-pricing rules, variation defaults or duplicate structured data may show another value. Compare the stored value with the public page, rendered schema, cart and checkout.
Should out-of-stock products be deleted?
Not automatically. A temporarily unavailable product can remain on its product-specific page with an honest status. Submission and availability should be managed accurately. Permanently discontinued records require a deliberate catalogue and redirect decision.
Does every variation need its own information?
Each purchasable variation should have enough accurate data to represent its offer, including relevant attributes, price and availability. Images, SKUs and identifiers should be variation-specific when the physical item differs.
What image size should I use?
Use high-quality images that meet the current Google requirements for the product category and programme. Google has announced a 500 × 500 pixel minimum for all products beginning 31 January 2027 and currently recommends 1500 × 1500 pixels or more for broad listing performance.
Can promotional text be placed on the main product image?
It should be avoided for Google product imagery. Use a clean main image without price, shipping, watermark or promotional overlays, and place supporting campaign information elsewhere on the page.
Does PW Merchant Check submit products to Google?
No. It performs preparation checks inside WordPress. It does not connect to Merchant Center, upload products or read Google account diagnostics.
Does a clean scan guarantee Merchant Center approval?
No. The scan covers selected local indicators and cannot assess every policy, account, market or product-category condition. Google makes its own decisions using its systems and current policies.
Is product data sent to PW Feed or Poyraz Web?
No product catalogue is sent to those services for the local checks described here. Administrators should still review the plugin’s current privacy information and version notes before installation, as they should with any WordPress plugin.
How often should the audit be repeated?
Repeat it after bulk imports, theme or plugin changes, currency changes, major sales, inventory integration updates and catalogue migrations. A regular schedule is helpful for active stores because product data changes continuously.
Final assessment
A Merchant Center-ready WooCommerce catalogue is built from real, consistent and purchasable offers. Product titles and descriptions should identify the item; price and availability should remain stable through checkout; images should show the correct product; identifiers should be genuine; and every variation should lead to the exact option represented in the data.
PW Merchant Check can make the first review faster by locating common omissions and organising affected products. It is most effective when combined with manual product-page tests, structured-data inspection and the official Google requirements for the target country and category.
No plugin can promise Merchant Center approval. A careful audit instead gives the merchant something more practical: a catalogue that is easier for customers and systems to understand, easier to maintain and better prepared for accurate submission.