Uploading a product spreadsheet and waiting for orders is the default expectation plenty of global sellers bring to Google Shopping. What actually happens first is a wave of mild warnings. Some products show as not eligible, price and availability errors pop up every few days, and the Google Ads account sits there with little it is allowed to serve. Dig into it and the problem usually lives in the Merchant Center product data and the places where it disagrees with your website, not in the ads themselves.

The way Google Shopping works fits in one sentence, the unit of advertising is the product listing itself. Whether products can serve, which countries they serve in, and which campaign type carries them all follow from the eligibility and quality of that product data. So the sensible order is to get the data path in shape first, then talk about bids and creative. The path has five stages, account and website verification, the product feed and policy eligibility, feed fields and data consistency, product groups, and trade-offs around profit and inventory. None of the stages is hard on its own, and they depend on each other in order, which is why skipping ahead stalls. The data path is the foundation, and the account and campaign strategy layer above it is covered in the Google Ads optimization strategy guide.

Verify Your Website and Finish Account Setup

Registering the Merchant Center account itself is not complicated, business details, time zone, and currency as required. The part to handle early is verifying and claiming your website. Google offers several routes, verification through your e-commerce platform, email verification, an HTML tag or file on the site, Google Tag Manager, or Google Analytics. Teams running their own storefronts mostly use the platform integration or a tag, which takes minutes.

Two details get overlooked. A single URL can only be claimed by one Merchant Center account, so when an agency and a merchant each hold their own account, a multi-client account (MCA) is the route, with sub-accounts inheriting the claim from the parent. Selling across countries does not mean opening more accounts either, it means setting target countries and feed labels inside the same product source and configuring shipping policies in the matching currency for each country.

For where account-level settings sit in the wider structure, see the Google Ads account setup and structure guide.

After the Product Feed Upload, Check Eligibility and Policies

There are several ways to get product data in. A handful of products can be added by hand in the interface, the standard route is a file upload in CSV, TSV, or XML, or a Google Sheet, and larger catalogs use scheduled fetches, where you provide a file URL and a fetch schedule and the system pulls it at intervals. Beyond those sit the Content API and third-party platform integrations such as Shopify. The choice comes down to update frequency, and a catalog that reprices daily is steadier on scheduled fetches or the API than on manual exports.

Once the data lands, resist the urge to build campaigns and go through the Needs attention tab under Products first. The notices fall into a few types. Warnings leave products serving, though performance may be limited, and ignoring them can lead to disapprovals. A disapproval stops the product from showing until it is fixed. One more state is preemptive item disapproval (PID), triggered when the price or availability in your product data does not match the landing page, and the system errs on the side of caution.

Above all that sits policy itself. Eligibility comes down to three things lining up, target countries inside Google Shopping support, a verified website, and products that comply with policy. On what gets rejected, the policies split in two. Prohibited content cannot be listed at all, including counterfeits, dangerous products, items that enable dishonest behavior, and inappropriate content. Restricted content can be listed with limitations, and adult-oriented products fall in this group, sexual content, adult merchandise, sexually suggestive content, and images containing nudity, with the official examples running from sex toys and adult magazines to sexual enhancement products and suggestive lingerie promotions. These listings do not show to every user or in every location, and extra requirements may apply. Alcohol is restricted as well.

When a product is disapproved, there are two moves. If you fixed the problem, select I fixed the issue to request another review, and if the finding looks wrong, select I disagree with the issue to appeal. Before the buttons become available, identity verification has to be complete and the product source cannot be empty. Reviews typically take seven business days, with the outcome sent by email. The chances to disagree are limited, essentially one per issue, and two unresolved attempts can lead to a cool-down period of a week and up, with the button greyed out. So make the fixes first and treat appeals as a considered step rather than a probe.

One more thing on the unpaid side, the same product data can also enter free listings, which surface on Search, the Shopping tab, Maps, and Images, and coverage shifts by market, as recorded in this note on the EEA change. For recent movement in policy wording, see the roundup on the merchant policy consolidation.

Feed Fields and Data Consistency Decide What Can Serve

The required field list is honestly short, id, title, description, link, image_link, price, and availability, plus conditional attributes that fire depending on the product, such as condition, brand, GTIN and MPN, or the declaration you submit when those identifiers do not exist. The work is in a few rules that trip people up.

The id is unique per product and stays the same when you update data, and the same product keeps one id across countries. Titles cap at 150 characters, should not carry promotional text like free shipping, and should line up with the landing page title; descriptions cap at 5,000 characters. Images have a new rule, at least 500 x 500 pixels for all product images, with enforcement starting January 31, 2027. Availability uses the fixed values in_stock, out_of_stock, preorder, and backorder, matching the landing page and checkout. Condition uses new, refurbished, or used, submitted in English.

Price and availability consistency is what keeps eligibility intact. The system compares product data against the landing page and checkout pages, structured data included, and a mismatch produces a warning at best and a PID at worst. The usual sources of mismatch all sit on the website side, placeholder content left in place, broken links, descriptions that do not match, a robots.txt blocking Googlebot, or a landing page that opens but redirects to a generic page. Fix the website first, then update the data. For catalogs that reprice and restock often, turning on automatic updates in Merchant Center, which syncs price and availability from your site's structured data, cuts PID risk noticeably.

One timing parameter belongs in your schedule. Inclusion and eligibility changes between Merchant Center and Google Ads take 24 to 48 hours to sync, so seeing no movement in the ads side on the day you edit data is normal.

The landing page side of this handoff is covered in more depth in the keyword-to-landing-page guide, and this piece only picks up the premise that pages and ad promises should agree.

Wiring Products into Standard Shopping and Performance Max

The traditional route for product ads is a Standard Shopping campaign. It manages inventory with product groups, a new campaign auto-creates an All products group that inherits your default maximum cost-per-click, and you subdivide from there by attributes such as Google product category, product type, brand, condition, item id, and custom label. Two rules matter. Each product can only land in one biddable product group per ad group, so subdivisions must not overlap, and only products inside a product group are eligible to serve. To hold a product back, use a filter or set it to Excluded.

Performance Max runs a different shell, with listing groups that hang off the asset group, deciding which products are included and carrying the reporting. The subdivision attributes match the Standard set closely, category, brand, item id, condition, product type, channel, and up to five custom labels. The difference is bidding, since Performance Max bids through the system against your objective, and listing groups carry no manual pricing role by design.

Which of the two to use, how to concentrate budget, and how to experiment sit in a separate piece, the Standard Shopping versus Performance Max comparison, and this one stays on the data path.

Profit and Inventory Trade-Offs Live in Product Groups

With data clean and products eligible, the next question is which of them should spend money, and that runs back to the business math.

Start with the margin a product holds before ad spend. Whatever can absorb your target acquisition cost stays in the main push, and the thin ones get a separate group with tighter targets, or they step out of paid placement entirely and let the free positions carry them. The average across the whole catalog tells you nothing, and groups exist for exactly this split.

Clearance and seasonal items suit a dedicated group, concentrated budget for a stretch, then switched off once sold. For slow-moving inventory, keep an eye on how out_of_stock periods affect serving so items do not idle with stale prices. Products with volatile pricing are the high-incidence zone for PIDs. Either wire up automatic updates to keep data and site in step, or hold them out of the feed until prices settle. Forcing it usually produces a loop of warnings and disapprovals that eats the team's time.

One last note, promotions on your site now feed automatically into Shopping and Performance Max ads, so coupons and discounts on the page have to be real, valid, and redeemable, and this action checklist lays out the decision path. For angles on longer-term Shopping performance, see the note on AI performance insights.

Common Misconceptions

Treating the product feed as a one-time project. Upload and walk away, and repriced items, stockouts, and expired promotions all go unnoticed, followed by the mystery of new product issues appearing daily. Product data is something you maintain, and automatic updates plus a weekly pass through Needs attention is the minimum.

Editing ads while leaving the website alone. The website's price and availability decide eligibility, because the system compares against the landing page, not the ads backend. When something mismatches, check the site's real state first, and once the site is right, the data can be right.

Deleting and reuploading disapproved products, or firing off a bulk appeal. The order should be, read the policy, decide whether the case is prohibited or restricted, fix the website and the data, and let the automatic re-review run; disagree only when the finding genuinely looks wrong, and there is essentially one chance per issue. Before any bulk appeal, clear the violating items out of the feed, because a failed batch can limit later appeals.

Expecting traffic the moment products go up. Product data settles whether you can serve and whether you serve correctly; impressions and orders also depend on demand, price competitiveness, bidding, and landing page experience. Nobody can promise a given number of impressions per SKU, and what you can do is clear the eligibility and data errors so system-level problems stop eating the impressions you would have earned.