Google Merchant Center: Make Product Data Reliable Before Shopping

Google Merchant Center is the foundation that connects a retailer’s catalogue with the store customers actually use. Before considering Google Shopping or free listings, the product, landing page, price, availability, and checkout must describe the same purchasable offer.

For “Google Merchant Center,” the Ahrefs Morocco estimate, 22 October 2026 is 1,100 volume and KD 79, with commercial/transactional intent. This Ahrefs estimate for Morocco is not a prediction of rankings, visibility, traffic, orders, revenue, or leads.

What Merchant Center is for

Merchant Center lets a retailer submit product information to Google and manage settings associated with its use. It does not make an inaccurate catalogue or unfinished shop retail-ready. If the feed, product page, and checkout disagree, the mismatch can affect an item or a wider account review.

Free listings may make eligible products available for certain Google experiences without media spend. That is not a promise that an item will appear: Google says it relies on supplied product data to match products with searches. Read Google’s official free-listings guide at configuration time because the available experiences and interface can change.

Review the store before importing a feed

Test an actual purchase journey

Google’s account guidelines state that Shopping products should be available for direct purchase through the online store. Test a representative set of products as a customer would: load the product page, choose the intended variant, add it to cart, review the charges, and proceed through checkout.

The same Merchant Center account guidelines call for clearly available contact details, at least one conventional payment method at checkout, clear disclosure of relevant conditions and the full cost, and an accessible returns/refunds policy. Publish the delivery, cancellation, return, and refund terms the business actually applies. This is not legal or regulatory advice; the retailer should confirm obligations relevant to its products and target markets with suitable advisers.

Match the submitted language to the page

Product data should lead to a landing page in the submitted language. In a multilingual store, do not only translate a feed title while routing the shopper to a page in another language. Plan the localised URL, product title, and description for each published version. Check currency, price, stock, selected variant, and delivery message on mobile as well as desktop.

Build reliable product data

Google’s product data specification defines required and conditional attributes. The details vary by product, programme, and target context, but an online retail baseline generally needs:

a stable id for each sellable product or variant;
factual title and description values that match the landing page;
a verified-domain link to the final page and an accessible image_link that shows the item;
price and availability matching the page and checkout;
brand, gtin when issued by the manufacturer, or mpn where applicable; and
relevant variant fields, including item_group_id, colour, or size.

Describe the item, not a promotion

A useful title identifies what is being sold: relevant brand, product type, model, and distinguishing variant detail. The description should help someone assess the product itself. Google asks retailers to match those fields to the landing page and cautions against promotional wording such as “free shipping” in them.

Choose a source of truth and an update route

Assign one source of truth for price, stock, and variants. If checkout shows a different value from the feed, trace the cause to the commerce platform, tax or pricing rule, variant logic, feed transformation, or update schedule. Correct the underlying source, wait for refresh, then retest.

Support the feed with structured data

A Merchant Center feed and page-level Product structured data have different but complementary roles. Google Search Central says that using both can improve eligibility for shopping experiences and help Google understand and verify the data. Page markup must still reflect what a shopper can see and buy. See Google’s introduction to Product structured data.

Prioritise notices and decide what comes next

Approved products alone do not make paid activity appropriate. Before connecting Merchant Center to media, check fulfilment capacity, customer-facing delivery and return terms, page quality, and the commercial question a campaign will measure. Catalogue activity can then connect to the Google Ads service. Separate catalogue health from site events: product view, add to cart, checkout start, confirmed order, and failed payment are distinct signals when they support a decision. Validation scope can be defined through Tracking & Analytics.

Limits that matter

Merchant Center does not correct an unclear offer, inaccurate inventory, weak service, or difficult checkout. It cannot create demand or ensure an item appears in a specific experience. Policies and interfaces change, so use official documentation rather than an old tutorial or screenshot when making changes.

The central question is whether the business can consistently send the same truthful product, price, availability, and purchase conditions the customer will encounter. A documented answer makes it easier to select a data source, correct exceptions, and decide whether free listings or Shopping campaigns are suitable.

FAQ — Google Merchant Center foundations

Do I need Merchant Center before Google Shopping campaigns?

Product-led Shopping activity requires the appropriate Merchant Center configuration and product data that meet applicable requirements. Establish the store and data baseline first, then define the campaign and measurement.

Which fields should be checked first?

Start with ID, title, description, landing-page link, main image, price, and availability. Then review identifiers and conditional attributes, especially variants. Compare them with the actual page and checkout.

Do free listings ensure free traffic or sales?

No. They may make an eligible product available for relevant experiences, subject to applicable rules and supplied data. Google says enabling free listings does not mean a product will be displayed.

Can one catalogue serve several languages?

The catalogue may include the same product in several localisations, but the submitted language and destination page need to match. Plan language-specific titles, descriptions, and URLs instead of applying a blanket redirect to one language.