Connecting Shopify to Google Merchant Center
Little Legs Pet Co. — Setup Attempt and Analysis
Introduction
Little Legs Pet Co. is a dachshund-themed pet boutique built as a practice Shopify store for this course. The store carries 8 products organized into three collections — Health & Comfort, Food & Treats, and Accessories & Toys — with product titles, descriptions, images, prices, and availability filled in from the Week 5 Product Catalog Development assignment. Basic navigation and collection structure were completed in Week 4.
For this assignment, I attempted to connect Little Legs Pet Co. to Google Merchant Center using the Google & YouTube sales channel built into Shopify. The goal was not to reach full Google approval, but to walk through the real setup flow, document what a retailer would encounter, and identify what a business needs to prepare before actually launching Google Shopping Ads.
Connection Attempt Evidence
The process began in the Shopify admin under Sales channels → Google & YouTube, which opens a guided app setup flow.
The first step is connecting a Google account, which Shopify uses to manage and sync store data with Google. After connecting the account, the onboarding checklist appeared, showing this as a multi-stage process rather than a single click — 2 of 5 tasks were completed at this point, with the option to connect an existing Google Merchant Center account or create a new one.
After clicking Create new to generate a fresh Merchant Center account, the checklist advanced to 3 of 5 tasks completed. At this stage, Shopify surfaced a new required step: “Check your online store requirements.” Google requires four specific things before it will treat a store as trustworthy enough to sync products:
- Add a valid payment method
- Create an online store (remove the store’s password protection)
- Add a refund policy and terms of service
- Confirm that contact information has been added to the store
Product Sync or Product Listing Evidence
I was not able to reach a product sync or product listing screen. The onboarding flow is gated — Shopify will not let a merchant proceed to product sync until the store requirements checklist above is satisfied. Because two of the four requirements (a valid payment method and a publicly accessible, unpassworded store) are not appropriate to complete for a practice/dev store, my products never reached the point of being evaluated by Google for sync eligibility.
This is a useful finding in itself: it shows that Google Merchant Center enforces store legitimacy checks before product data quality is even assessed. A retailer cannot skip straight to checking whether their product titles or images meet Google’s standards — they first have to prove the store itself is a real, operating business.
Setup Barriers and Warnings
Two of the four requirements were resolved during this assignment; two remained as genuine barriers.
Resolved:
- Refund policy and terms of service — Initially, the Shopify Settings → Policies page showed “No policy set” for Return and refund policy, Terms of service, and Shipping policy, while Contact information was flagged as “Required.”
I generated a refund policy and terms of service from Shopify’s built-in templates, and wrote a short shipping policy manually since a template option wasn’t available for that field. Contact information was also added to the store.
Returning to the Google & YouTube onboarding checklist confirmed the fix took effect: “Add a refund policy and terms of service” now shows as complete.
Not resolved (real barriers):
- Add a valid payment method — This requires connecting a real bank account or payment processor through Shopify Payments. For a practice store not tied to an actual registered business, this is not something that can or should be completed.
- Remove the online store password — Google requires the store to be publicly viewable (not password-protected) in order to verify it. This is technically possible to do for a practice store, but was left in place here to avoid presenting a non-operating business as a live, publicly accessible storefront.
Fixes Needed
Before a real retailer could move past this stage of Google Merchant Center setup, they would need to:
- Set up an actual payment method through Shopify Payments or a supported processor, which requires a registered business entity and bank account.
- Take the storefront public, removing any password protection so Google’s crawlers and reviewers can access it.
- Verify and claim the store’s domain, which usually happens once the payment and store-visibility requirements are met and Merchant Center moves into website verification.
- Ensure product data is complete and accurate (titles, images, prices, availability, GTIN/barcode data where applicable) since even after passing the store-level checks, Google separately reviews individual product listings for policy compliance before approving them for free listings or ads.
None of these are unusual or unreasonable requirements — they reflect the baseline trust and safety bar Google sets for any business wanting free product placement or paid ad space, and they make sense given how much traffic and purchase intent flows through Google Shopping results.
CPP Farm Store Reflection
Based on this experience, CPP Farm Store would need to treat Google Merchant Center setup as a business-readiness project, not just a technical integration. The clearest lesson from this attempt is that Google evaluates the store before it ever evaluates the products. CPP Farm Store would need a real payment method connected through Shopify Payments, which means having its business legally registered and a bank account tied to the store — not something that can be improvised at the last minute before a launch.
Store credibility signals matter just as much as the product catalog itself. CPP Farm Store would need its refund and return policy, terms of service, shipping policy, and contact information fully written out and visible in the site footer, not left as Shopify’s default blank fields. Customers and Google alike use these pages as trust signals, and their absence is one of the fastest ways to get flagged during setup. The store would also need to be live and publicly accessible, without any password gate, since Google’s verification process depends on being able to crawl and confirm the site.
On the product side, CPP Farm Store should audit its catalog for consistent, complete data before attempting to connect: accurate pricing, current availability, clear product images, and descriptive titles that match what Google expects for Shopping listings. Category tagging also matters, since Google Shopping relies on product categories to match listings with shopper searches, and a farm-goods store selling a mix of food, gifts, and seasonal items would need thoughtful categorization to avoid mismatches or disapprovals.
Finally, CPP Farm Store should not expect an instant launch. This assignment showed that Google Merchant Center is a multi-stage gated process, and rushing into Shopping Ads before the store itself is verified and trustworthy would likely result in wasted time and repeated setup failures rather than any real advertising benefit. Building in a preparation phase — policies, payment setup, product data cleanup — before ever opening the Google & YouTube channel would save the business significant friction.
Appendix
- GitHub Repository: https://github.com/espinacecilia-design/itp-assign-6
- GitHub Pages (Published Report): https://espinacecilia-design.github.io/itp-assign-6/