Merchant Center · focused work
Merchant Center setup
Merchant Center is where a store's product data becomes eligible to appear on Google's shopping surfaces. Setting it up is a sequence of account facts that must be true before a single product can be reviewed: who the business is, that it owns the website, what it charges to ship, how it handles returns, and where the product data comes from.
This is the right work if
- The store is ready to advertise products and has no Merchant Center account yet
- An account exists but the website was never verified or was claimed by someone else
- Shipping and returns configuration was skipped and the catalog is being held back
- A second country is being added to an account that was built for one market
- Several stores or brands need serving and nobody has decided how the accounts should be arranged
What it is
The account facts that come first
The configuration divides into account level and data level. At account level: the legal business details and the name shoppers will see, website ownership verified and the address claimed for this account, shipping services and rates for every country sold to, tax settings where the market requires them, a stated returns policy, and users given the access their role needs rather than a shared login. These are not administrative boxes. Incomplete shipping or returns configuration holds back the entire catalog, not one product, which is why a store can sit with a perfect feed and no listings.
At data level: a source for the products, whether that is a platform connection, a scheduled fetch of a hosted file, an upload or the API, with the country of sale and language set for each market being served. The update schedule should match how quickly prices and stock move, and automatic item updates let price and availability be corrected from the page between runs. Then the connections that make the account useful: accepting the terms for unpaid listings, linking the advertising account, and any comparison shopping arrangement the region requires. Setup finishes with a monitoring routine rather than with a first approval, because the account only stays healthy if somebody reads it.
How it is done
The work, in order
What changes
- Products can actually be reviewed because the account level facts are complete
- Shipping and returns are configured once rather than fought product by product
- Prices and stock stay accurate between feed runs
- Account structure and access are decided deliberately rather than inherited
Get the business facts consistent
Set the legal name, the display name shoppers will see, the address and the contact details, and confirm the same information appears on the website. Review compares the two, and a mismatch here is a slow and avoidable reason for an account to sit unapproved.
Verify and claim the website
Verify ownership through the method that suits the platform and claim the URL for this account. Check that no other account already holds the claim, because a claim left behind by a previous agency or a test account has to be released before anything else works.
Configure shipping, returns and tax
Enter delivery services and rates per country, state the returns window and process, and complete tax settings where the market requires them. Do this before troubleshooting individual products, since these settings suppress listings across the whole account when they are missing.
Connect the product data properly
Choose the data source, set the country of sale and the language for each market, pick an update frequency that matches how often prices and stock change, and switch on automatic item updates so price and availability can be corrected from the page between scheduled runs.
Switch on destinations and links
Accept the terms for the unpaid listings programme, link the advertising account so campaigns can use the products, and add each person with the permission level their job needs. Shared logins make it impossible to see later who changed what.
Prepare the site, then set a routine
Check that the site shows contact details, a returns policy, a working checkout and prices matching the feed, since review looks at the website as closely as the data. Then put a weekly slot in someone's calendar to read item issues.
Platform notes
Shopify
The Google channel handles verification and creates the data source, but products only reach the feed if they are published to that channel and pass its own requirements, so an item live on the site is not automatically an item in Merchant Center.
WooCommerce
Verification is usually done through a meta tag or file upload while the feed comes from a plugin, so the two are separate jobs, and a plugin change can replace the data source without affecting the verification.
What actually happens during the account review?
The website and the product data are checked together against the requirements: that the business is identifiable, that checkout works, that returns and contact information exist, and that prices and availability match. It is not only a look at the feed, which is why site fixes often resolve what looks like a data problem.
Should delivery rates live in the account or in the product data?
Account settings suit stores with a manageable number of services and rate rules, and they are far easier to maintain. Per-product values in the data make sense when shipping genuinely varies by item, such as oversized goods. Mixing both without a rule is how contradictory rates appear.
Can one account serve several stores?
One account can hold multiple data sources and sell into multiple countries, and separate businesses with different websites are usually better in separate accounts under a shared structure. The deciding factors are who owns the website claim, how reporting needs to be split, and who should have access.
What suppresses a whole account rather than one product?
Missing or incomplete shipping and returns configuration, an unverified or unclaimed website, unresolved business information, and account level policy notices. When most of a catalog is invisible at once, the cause is nearly always at account level rather than in the individual products.
Related work and answers
Find the leak.
A free Growth Analysis ranks what your store should fix first, by revenue at stake.