Google Merchant Center Compliance: the Rules Google Checks

Google Merchant Center compliance starts with a purchase a customer can actually complete. Your business details, product information, shipping promises and return process need to describe the same offer from the listing through checkout. This GClimb guide turns those requirements into checks you can carry out on your own store. Instead of treating a published policy as a finished task, you will compare what the policy says with the product page, account settings and purchase flow.

Start by separating product issues from account issues. A price mismatch on a particular variant calls for a close look at that item's landing page and feed. A misrepresentation issue also requires a wider review of the business, its claims and the customer experience. Editing a product title will not resolve a contradiction about who fulfills an order or how refunds work. Record the actual issue, its scope and the examples available in the account before deciding what to change.

This guide follows the order of a practical store audit: identify the seller, compare shipping and returns, check product data, walk through checkout and review commercial claims. It then covers changes to an established store and the steps before an account review. The same method works for a domestic store and for cross-border sales, provided you test the actual country, language and currency combination offered to the buyer rather than assuming your default storefront represents every customer.

Can customers identify the business and reach you?

Open your store in a fresh browser session, without an administrator login. Start on a product page and find the seller's details, contact options and purchase terms. You are checking both the information and the route to it. A page that exists in your content manager but is not linked from the customer journey does little to explain the business to a buyer.

• Identify the trading name and the business responsible for the order.
• Compare the published business details with your Merchant Center settings.
• Open the contact page and test the methods you advertise.
• Read the shipping, return and refund terms available to customers.
• Check the privacy information where customer data is collected.
• Repeat the visit in each language and destination country you actively support.

Explain the relationship between the brand and the seller

Your brand name and legal business name may differ. Explain the relationship clearly rather than replacing every business reference with the name on your logo. A customer should be able to connect the store, the contact page and the order summary to the business handling the purchase. Check for information left behind by a previous theme, an old address or a copied template. Those fragments can contradict otherwise accurate account details.

Test your contact form and confirm that messages reach the intended team. On mobile, check that email and telephone links work. Publish accurate support hours if you use them, and keep the contact information aligned when you change providers or staff. A professional email address can help customers recognize the business, but do not confuse that recommendation with a universal requirement to provide every possible contact channel. Focus on accessible, accurate contact information and the obligations that apply to your business.

Make the policies usable

Read the pages rather than checking only their titles. Replace unfinished template fields, outdated company names and promises that do not match your operations. Open each policy from a product page and from the cart. Test the mobile navigation too: a consent banner or promotional overlay can cover a link even when the underlying page is valid. After making a correction, repeat the visit in a clean session to confirm it is visible to a customer, not only to your editor account.

For an international store, keep the product data, landing page and buying experience aligned in the language you offer. A shopper arriving on an English product page should be able to understand the terms needed to buy it. Check country selectors and automatic redirects carefully. A visitor should not land on a different currency, product or storefront simply because their browser has saved an earlier preference. Record the behavior you actually observe for each tested destination.

Do shipping and return settings match the customer promise?

Compare the product page, announcement banner, cart, shipping policy and Merchant Center settings for the same destination. The offer needs to remain understandable as the customer moves through the store. A prominent free-shipping claim should not conceal an exclusion that appears only at the final step. Check the rule for the specific item as well as the default rule, particularly when bulky goods, made-to-order products or separate suppliers are involved.

Separate handling time from transit time

Handling time covers the period before a parcel is handed to the carrier. Transit time covers the journey after that handoff. A promise to dispatch an order quickly is therefore different from a promise about its arrival. Record each part separately, including the working days, processing schedule and order cutoff you use. Then compare the total customer-facing expectation with the shipping configuration for the destination country. If one part is missing, investigate it rather than treating the other part as the whole delivery window.

Check made-to-order and preorder items individually. A banner written for stocked products may create the wrong expectation for those purchases. Your business address, fulfillment location and return destination can also differ. Explain the differences that affect the customer, including costs and timing, instead of implying local fulfillment merely through a local domain or flag. If a supplier ships the order, confirm what that supplier can deliver before publishing the promise under your own store's name.

Walk through a return request

• Find the method a buyer uses to request a return.
• Read the return window and when that window begins.
• Check the stated condition of goods accepted for return.
• Identify who pays return shipping and how the parcel is sent back.
• Read the promised refund method and timing.
• Check exceptions for the product and destination country being tested.

Compare the published policy with the relevant Merchant Center return settings after the interface has finished loading. A list may contain separate countries or product groups, so open the applicable rule instead of inspecting only the table header. Then check the support instructions a customer receives. A policy offering a refund and a support process offering only store credit do not describe the same commitment. Resolve that difference in the process as well as in the text.

Do not copy a return period from a different jurisdiction and present it as a worldwide rule. Your legal obligations and voluntary commercial terms depend on the situation. For this operational audit, identify the policy your business has approved, compare it across the website and settings, and use your established process to validate country-specific obligations. The technical configuration should reproduce those terms rather than introduce an undocumented exception. Review translated versions whenever the underlying policy changes.

Does the feed describe the exact item a customer can buy?

Start from the URL submitted for the product, not from your home page. Select the advertised variant, read its price and availability, and add that same item to the cart. Keep the destination country constant throughout the test. Comparing the cheapest variant in a feed with a different default variant on the page creates a misleading audit result even if both values are individually correct.

Check identifiers and required attributes

Review the basic product information: a stable identifier, title, description, product link, image, price and availability. Additional requirements depend on the product and target country. Variant attributes should identify the item being offered, including size, color and grouping where required. An internal stock code does not become a GTIN because it is placed in that field. Use identifiers assigned to the actual product, and trace incorrect values back to the system generating them.

For an item without an assigned identifier, handle that specific case rather than inventing a barcode or declaring the entire catalog exempt. Check the manufacturer's information and the issue details in Merchant Center. A manual correction can disappear at the next synchronization if the feed application still holds the old value. Record the application or field responsible for the data so the fix survives future imports. Keep the item's identity stable when updating its price or description.

Recheck promotions, availability and images

A sale price must match the offer available on the landing page. Discounts that require membership, a coupon or a particular quantity need to be handled as the offers they actually are, rather than presented as an unconditional price. Test the end of a promotion as well as its launch. Your feed, site cache and checkout can update at different times, leaving the customer with a price that no longer matches the submitted data. Revisit the item after synchronization completes.

Images should represent the item and variant being sold, without misleading promotional additions. Descriptions should explain the product, its condition and what is included. If an image shows accessories that are sold separately, make the offer clear. For a broad catalog, include variants, sale items, preorders and products fulfilled differently in your audit. Testing only a straightforward, in-stock product does not verify the other purchase flows. Keep untested combinations visible in your record instead of extending one successful result to the whole catalog.

For US and UK storefronts, confirm the currency and the way applicable taxes are presented throughout the journey. Do not copy a domestic configuration into a new destination without checking it. Use a destination address for the market you are testing, then read the final order summary. The useful result is the observed relationship between the submitted offer and the amount the customer is shown, not a general assumption based on the country selected in an administrative menu.

Can a buyer complete a clear and secure checkout?

The checkout review starts before the payment form. Confirm that the selected product reaches the cart unchanged and that the store can accept an address in the advertised destination. Collect personal information over a secure connection, and check the certificate and redirects on pages involved in that collection. Test the necessary page resources as well: a secure page that cannot load its address selector still leaves the purchase flow broken.

• Add the advertised variant to a fresh cart.
• Enter an address in a destination you actually serve.
• Read shipping charges, applicable taxes and additional fees.
• Check the complete expense and payment model before confirmation.
• Confirm that a conventional payment method is available.
• Open purchase terms and contact information from the checkout journey.

If the offer involves recurring payments, customers need to understand the amount and billing interval before committing. For a one-time purchase, make sure an optional add-on does not silently change the order. Address-dependent costs should be disclosed clearly when they can be determined. If a destination is unsupported, the store should explain that rather than displaying an arbitrary charge and failing later. Review error messages too: they should help the buyer understand what must be corrected.

A completed test order can confirm more than a visit to the order summary, but it may also create a charge, send messages or trigger fulfillment. Run that check through your authorized testing process with the relevant teams. If you are only reviewing the interface, stop before an action that commits money and record the boundary of the test. Saying that the summary was checked is more useful than claiming the entire payment process passed when no transaction was completed.

Repeat important steps on a phone and in a fresh browser session. Saved addresses, administrator privileges and existing customer cookies can hide problems that a first-time buyer encounters. Also check that your country and language remain consistent when moving from the storefront to a hosted checkout. A successful domestic desktop test should not be used as evidence for an international mobile purchase until that path has been exercised.

Are commercial claims accurate and products eligible?

Matching the feed to the website is not enough if both contain a misleading promise. Review statements about the business location, fulfillment, stock, reviews, endorsements, guarantees and discounts. Each claim should describe something your business can support. A stock indicator should reflect real availability rather than manufactured urgency. A discount should not rely on an invented reference price. A trust badge should not imply an affiliation that the business does not have.

Check product eligibility for the destination country and the program you use before submitting restricted or regulated items. Permission to sell an item on your own website does not automatically establish its eligibility for Shopping. Review the rights to use photographs, trademarks and other material as part of this process. If your store claims to be an authorized reseller or to hold a certification, retain the supporting information and make sure the wording accurately reflects its scope.

How should you maintain compliance after store changes?

Trigger a fresh check when you change a theme, feed app, carrier, domain or commercial policy. Add a recurring review that fits the rate at which your catalog changes. Prices and availability need closer attention when they move frequently, while business details should be rechecked whenever the organization changes. A calendar helps assign responsibility, but it does not replace the issues and notifications visible in Merchant Center. Give each unresolved item an owner and a concrete next action.

During a migration, verify the website association in Merchant Center, new product URLs, images and policy links. Test redirects from the submitted URLs in the target country. A redirect may preserve an old address while choosing the wrong language or variant. Keep identifiers stable for existing items, and examine the result of the next import rather than assuming a successful deployment means the product data is correct. Check both the storefront and the account after the change.

Keep a small audit log with the date, item or URL, country, check performed, result and corrective action. Use Not verified when a setting has not been opened or a page fails to load. An incomplete screenshot does not prove that a setting is missing. Useful evidence includes the context of the observation: selected variant, destination, displayed text and corresponding feed value. A screenshot can illustrate a check, but should not stand in for the complete purchase path.

When a correction applies to many items, test the shared mechanism and then inspect products that exercise its different branches. For example, a shipping fix may behave differently for a standard item and an oversized one. Keep the list of tested cases in the log so a colleague can reproduce them. This approach makes the audit reusable after the next catalog update and prevents the team from repeatedly checking the easy path while the exceptional path remains unresolved.

What should you do before requesting an account review?

• Identify the issue and its scope in the account.
• Check the relevant website pages, product data and settings.
• Correct the system that generates the inaccurate information.
• Wait for the changes to appear, then repeat the customer journey.
• Document the live corrections with their locations and dates.
• Use the available review action after completing the displayed prerequisites.

Continue through the account affected by the issue; do not create another account to bypass a suspension. After submission, record the actual review status and response. A submitted request is not an approval. If the response identifies remaining problems, compare them with the correction log before making another change. This keeps the next action tied to an observed issue rather than to a guess about what might persuade a reviewer.

Conclusion: verify the purchase, not just the policy page

FAQ: Google Merchant Center compliance