A Google Shopping setup service puts 5 parts in order: a Merchant Center account with a claimed domain, a product feed, product pages that match the feed, 1 campaign, and conversion tracking.
Condition: this order applies if you sell physical products online. You also need public product pages and access to your domain.
Limit: Google decides the review time, not the person who does the setup. Merchant Center documentation states the initial review for Shopping ads can take up to 3 to 5 business days. Data changes during the review can delay it.
I wrote this note for a shop owner who does not read code. I keep Google terms as they are, then explain each one in plain words. I took each requirement below from Google documentation that I opened myself, and I list the links under Sources.
At a glance: 5 stages and who owns them
People often treat Google Shopping like a normal ad campaign. It is not. A normal ad uses keywords that you write. Shopping ads use your product data. Google Ads documentation states that Shopping ads use your Merchant Center product data, not keywords, to decide how and where ads show. So the main work is clean data, not ad copy.
| Stage | Visible result | Work owner |
|---|---|---|
| 1. Merchant Center | Claimed domain and verified business address | Shop owner |
| 2. Product feed | All products read with required attributes | Data team or installer |
| 3. Google review | Product status moves from Pending to active | |
| 4. Campaign | 1 Shopping or Performance Max campaign runs | Ads operator |
| 5. Conversion tracking | Order value reaches Google Ads reports | Web team |
Look at row 3. That stage belongs to Google, not to you and not to your installer. Anyone who promises a date when your products appear in Shopping is promising a Google decision. He cannot keep that promise.
Stage 1: Merchant Center and the domain claim
Merchant Center is the store of your product data at Google. Think of a catalogue that you leave with Google, separate from your own shop.
Before that catalogue helps you, Google must trust that the domain is yours. Google documentation uses 2 words that are easy to mix up. Verify means you prove that you own the site. Claim means you tie that site address to 1 Merchant Center account. The documentation states that a single URL can only be claimed by one account.
This matters if a past agency set up Merchant Center for you. Your domain can still sit inside their account. You must release it first.
Google documents 5 ways to verify: through your e-commerce platform, through email, by adding an HTML tag or file to the site, through Google Tag Manager, or through Google Analytics. When Google already holds the data it needs, for example because your site uses Google Analytics, the verification happens automatically after you enter your store address.
Stage 2: the product feed and the required attributes
A product feed is 1 long list. Each row is 1 product. Each column is 1 attribute, such as price or stock. Google calls this list your product data.
Nearly all the failures I see sit here, not in the ads. The product data specification uses 3 states: Required, It depends, and Optional. Google spells out what Required means. If you do not submit that attribute, your product cannot serve in ads and free listings.
| Attribute | State in the documentation | Note from the documentation |
|---|---|---|
| id | Required | Max 50 characters. Unique per product. Keep it the same when you update data. |
| title | Required | Max 150 characters. No promotional text such as free shipping. |
| description | Required | Max 5000 characters. Product information only, no store links. |
| link | Required | The product page. Use your verified domain. Start with http or https. |
| image_link | Required | Main image. Google states a minimum of 500 x 500 pixels applies from 31 January 2027. |
| availability | Required | Values: in_stock, out_of_stock, preorder, backorder. Must match the product page. |
| price | Required | Number plus ISO 4217 currency. Must match the page and the checkout. |
| brand | Required for new products | Except movies, books, and musical recording brands. Do not write Generic or No brand. |
| condition | Required if not new | Needed when the product is used or refurbished. |
| item_group_id | Required for variants | Needed for free listings on all product variants. |
| gtin | It depends | The documentation recommends it when available. It is not a Required state. |
| google_product_category | Optional | Give 1 most relevant category. Use the category ID, not 2 formats at once. |
People misread the last 2 rows often. I am often told that gtin and the Google category are compulsory. In the documentation I read, gtin holds the It depends state and google_product_category holds the Optional state. Even so, Google documentation names wrong google_product_category and gtin values as common problems. So separate 2 ideas: what you must submit, and what must be correct once you submit it.
Stage 3: product pages must match the feed
Google compares your feed against your product page. When those 2 numbers differ, the product gets an issue. The documentation states that price and availability must match across your product data, your landing page, and your checkout pages.
One mechanism deserves its name: preemptive item disapproval. Merchant Center documentation explains that it happens when the price or availability in your product data does not match your landing pages. Google errs on the side of caution and disapproves products that are likely to violate the requirements. A review is required to clear it.
This is why shops that run frequent discounts get hit most. The page price changes each week and the feed does not follow.
The documentation also lists common website issues that lead to product disapprovals: placeholder content, broken links, missing or inconsistent information, inaccurate product descriptions, mismatched categories between site and product data, a robots.txt configuration that blocks Googlebot or Googlebot-image, a landing page that is unavailable through server errors or slow loading, and a landing page that redirects to a generic page instead of the specific product page.
Check the robots.txt line first. If that file blocks Googlebot-image, Google cannot fetch your product images, and a correct image_link attribute stops being useful.
Stage 4: the Google review and why products get rejected
Products do not appear as soon as the data arrives. Merchant Center documentation states that a first upload goes into an initial review. Before a data source can be sent for review, your account must meet the requirements below.
| Requirement before review | Applies to |
|---|---|
| Shipping settings | Countries where shipping data is required |
| Data source for the target country | All accounts |
| Claimed and verified URL | All accounts |
| Verified business address | All accounts |
| Tax settings | United States |
Here are the timings, each one from Google documentation. The initial review for Shopping ads can take up to 3 to 5 business days, and products stay in a Pending status during it. For account-level issues, a review can take up to 7 days. After you make a technical fix live, a review request starts a fresh crawl, and those crawls usually finish within 24 to 48 hours.
There are 2 levels of issue and the difference is large. A product-level issue affects that product alone. An account-level issue affects all of your products. At each level there are 2 flavours: a warning and a disapproval. Products with warnings still show, but their performance can be limited, and unresolved warnings can turn into disapprovals.
Read one sentence in the documentation twice. When Google detects an egregious account-level issue, the account can be suspended immediately with no warning first. That is why I never upload a full feed to a new account before I check the Shopping ads policies.
Those policies cover 4 areas: prohibited content, prohibited practices, restricted content, and site requirements. Google states that enforcement uses a combination of Google AI and human evaluation. Complex or severe cases go to specially trained experts.
What a Google Shopping setup service does in stage 5
Stage 5 holds 2 parts: link the accounts, then build 1 campaign.
Google Ads documentation states that you need to link your Google Ads account and your Merchant Center account before you can create Shopping campaigns. It also gives 1 condition before you link: make sure neither account holds account-level policy violations.
Then you pick a campaign type. Google Ads documentation compares the 2 types, and I keep the rows that change a decision.
| Comparison | Performance Max | Shopping campaign |
|---|---|---|
| Where ads appear | Most Google Ads channels | Selected channels only |
| Billing | Campaign performance, such as clicks or CPM | Cost-per-click |
| Bidding | Automated strategies only | Automated or manual CPC |
| Creative assets | Asset groups plus the feed | The feed alone |
My reading of that table: Performance Max covers more placements, and a Shopping campaign gives you manual control. The documentation states that additional creative assets such as text, image, or video are not available yet for Shopping campaigns. When your feed data is new and still unstable, manual control makes cause and effect easier to read.
The last part is conversion tracking. Treat it as a recorder: it tells Google what people did after they clicked an ad. Google Ads documentation states that the first step is to choose what you want to track, then to create a separate conversion action for each type of conversion. For purchases on your site, the type is a web conversion.
Without this part, your report holds clicks alone. Clicks are not revenue. I explain the reason in my note on busy clicks and quiet sales, and the profit threshold maths in how to calculate ROAS and break-even ROAS.
A worked example with dummy data
The numbers below are dummy data that I made up to show the repair path. This is a simulation, not a client result.
| Part of the simulation | Content |
|---|---|
| Starting condition | An example shop with 40 products. The feed is uploaded. 12 products are disapproved. |
| Input | The feed says price 89000 IDR. The product page shows Rp 79.000 after a discount. |
| Step 1 | Open the Needs attention tab. Download the list of affected products. |
| Step 2 | Name the pattern: the feed price differs from the page price. |
| Step 3 | Fix price on the 12 rows. Upload the feed again. |
| Step 4 | Request a review. A fresh crawl starts. |
| Output | The documentation states crawls usually finish within 24 to 48 hours. |
| Decision | Turn on automatic updates so the prices stop drifting apart. |
The decision in the last row is not my invention. Merchant Center documentation states that automatic updates help reduce the risk of preemptive product disapproval for issues such as price and availability mismatches.
A checklist before you start
- Gather admin access to the domain, the hosting, and the shop platform.
- Check whether an old Merchant Center account still claims your domain.
- Open your robots.txt. Confirm that Googlebot and Googlebot-image are not blocked.
- Confirm that each product has a public page with a price, stock, and an image.
- Match price and stock across the feed, the product page, and the checkout.
- Pick 1 target country and 1 currency for the first upload.
- Read the Shopping ads policies for your product category before you upload.
- Decide who owns the campaign after handover.
- Prepare 1 conversion action for purchases on the site.
Questions and answers
How long until my products appear in Google Shopping? Merchant Center documentation states the initial review for Shopping ads can take up to 3 to 5 business days, and products hold a Pending status during the review. Product data changes during the review can delay it further.
Must I fill in gtin for each product? No. The Google product data specification gives gtin the It depends state and recommends it when available. Attributes in the Required state include id, title, description, link, image_link, availability, and price.
Why are my products disapproved when the feed looks complete? Disapprovals often come from the website, not the feed. Google documentation names broken links, placeholder content, slow pages, and a robots.txt that blocks Googlebot as common triggers.
What is the difference between a Shopping campaign and Performance Max? Performance Max reaches most Google Ads channels and uses automated bidding. A Shopping campaign uses selected channels and offers a manual CPC option.
Does the setup fee include my ad budget? No. The setup fee and the media budget stay separate. You pay Google for media, and the installer for the setup work.
Who runs the campaign after the setup ends? Your team becomes the operator after handover. Daily management is not part of the setup work, and it is quoted separately.
Next step
If you want 1 Google Shopping path built through to handover, read the scope on the Google Shopping Setup page. That service covers setup and handover, not daily management, and the media budget is paid separately.
Before you contact anyone, do 1 item from the checklist: open robots.txt and compare 3 product prices across the feed, the page, and the checkout. What you find there decides whether your job is light or heavy.
Sources
- Product data specification, Google Merchant Center Help supports the state and rule of each feed attribute, including the meaning of Required and the character limits.
- Issues in Merchant Center, Google Merchant Center Help supports the 3 to 5 business day review, the account review of up to 7 days, the 24 to 48 hour crawl, the pre-review requirements, and the website issue list.
- Shopping ads policies, Google Merchant Center Help supports the 4 policy areas, the site requirements, and how Google enforces the policies.
- About Shopping ads, Google Ads Help supports the statement that Shopping ads use product data instead of keywords, and the Performance Max against Shopping campaign comparison.
- About online store URL verification, Google Merchant Center Help supports the meaning of verify and claim, the rule of 1 URL for 1 account, and the 5 verification methods.
- Link a Google Ads account to Merchant Center, Google Ads Help supports the account link requirement before you create Shopping campaigns.
- Different ways to track conversions, Google Ads Help supports the step of choosing conversions and using 1 conversion action per type.
- Fix a disapproved ad or appeal a policy decision, Google Ads Help supports the fix and appeal path, and the In progress appeal status that you check after 24 hours.
Note: the failure pattern that I call the one I see most often is my own observation, not a figure from Google documentation.
