Google product listing ads: How Shopping ads work now
Learn how Google product listing ads, now Shopping ads, use Merchant Center data, differ from free listings, and improve eligibility and visibility.
Google product listing ads, or PLAs, are product-focused ads for shoppers searching to buy. Google now calls them Shopping ads. A Shopping ad can show an image, title, price, store name, and related details before the click. It is assembled from product data in Google Merchant Center, so product-record quality shapes eligibility and performance.
Catalog treats that record as infrastructure. Keep IDs, variants, attributes, price, availability, and product context structured upstream, then map the result to Google and the other surfaces where your products need to appear.
Product listing ads are now Google Shopping ads
“Product listing ad” is the older name for what Google documents as a Shopping ad. Google's original Product Listing Ads announcement introduced the term. The change in terminology does not change the basic workflow:
- Put your product data into Merchant Center.
- Link Merchant Center to Google Ads.
- Create a Shopping or Performance Max campaign.
- Let Google match eligible products to relevant shopping queries and serve the ad.
Unlike a text Search ad, a Shopping ad does not start with a keyword list and a block of ad copy. Google uses attributes such as title, category, brand, condition, price, and availability to understand the offer and match it to a query. The shopper can see the product and price before clicking, which gives the click more context.
The product data and the campaign do different jobs. Merchant Center describes what you sell. Google Ads decides where to promote eligible products, how much to bid, and how to measure the campaign. A successful upload or API response means Google accepted the input for processing. It does not mean the product is approved or serving.
Google's Shopping ads documentation covers the current ad format, campaign types, and billing behavior. Use Shopping ads in a current setup, while keeping PLA for the older term.
Shopping ads vs free product listings
Paid product listing ads and free product listings can use the same Merchant Center product data. They are different programs with different controls and economics. Running one does not automatically guarantee the other will show.
| Shopping ads, formerly PLAs | Free product listings | |
|---|---|---|
| Cost to the merchant | Paid Google Ads campaign. Charges depend on the campaign and billed click or engagement. | No ad charge for the listing itself. Normal store, fulfillment, and platform costs still apply. |
| Setup | Merchant Center product data, linked Google Ads account, campaign, budget, and bidding or targeting settings. | Merchant Center product data, eligibility for free listings, policy compliance, and required store information. |
| Control | You can set budget, bids or goals, locations, product groups, campaign filters, and reporting. | Google decides when an eligible product matches a shopper and where it appears. |
| Common surfaces | Shopping inventory and eligible Google Ads placements. Performance Max can use wider Google Ads inventory. | Google Search, the Shopping tab, Maps, Images, Lens, YouTube, Gemini, and other eligible surfaces. |
| Visibility | A product still needs approved data, campaign eligibility, budget, relevance, and auction eligibility. | Eligibility permits Google to consider the product. It does not guarantee an impression or click. |
| Measurement | Google Ads campaign metrics such as impressions, clicks, conversions, revenue, and return on ad spend. | Merchant Center free-listing reporting and the traffic and conversion data available in your analytics setup. |
Google says free listings can appear alongside paid campaigns and that their status does not guarantee customer visibility. Read its free listings guidance for current surfaces and eligibility requirements.
A practical rule is to use both when they fit your goals. Free listings create an unpaid discovery path. Shopping ads buy additional campaign control and reach. Neither makes poor product data useful.
Merchant Center data sources replaced the old “feed” label
Google now calls the place where you submit product information a data source, previously known as a feed. A feed is still a normal way to deliver data, but it is one of several inputs.
Google lists these current methods in its data source documentation:
- automatic discovery from your online store;
- an ecommerce platform connection, such as Shopify;
- a
.txt,.xml, or.tsvfile uploaded once or retrieved from a hosted URL; - a Google Sheets template;
- products entered one at a time in Merchant Center;
- the Merchant API for programmatic updates.
Choose the source around data ownership and change frequency, not around the word “feed.” A small catalog with a stable assortment can work with a Sheet or platform connection. A larger catalog may need a scheduled file or API. A store with complete Product structured data may use automatic discovery, although you still need to inspect what Google extracted.
What each source is good for
| Source | Good fit | Trade-off to manage |
|---|---|---|
| Online-store discovery | A store whose product pages expose complete, accurate structured data. | Google extracts what the page publishes. It is harder to add channel-specific fields that do not exist on the page. |
| Ecommerce platform connection | Merchants who want the platform to own product information and sync it to Google. | Platform sync rules and update delays become part of the operating model. |
| Hosted file or upload | Teams with an existing export or a controlled data pipeline. | The file must follow Google's format, stay reachable, and refresh before commercial data goes stale. |
| Google Sheets | Small catalogs and teams that need a visible template. | Manual edits and a 24-hour sync are a poor fit for fast-changing inventory. |
| Merchant API | Large catalogs, frequent updates, or a system that needs programmatic control. | It requires authentication, retries, rate-limit handling, and version maintenance. |
Google's product-upload guide explains the current setup paths. For custom integrations, use the Merchant API, not the retired Content API for Shopping.
Map a trusted product record to Google's inputs
The most reliable Google product feed starts with one governed record for each sellable product or variant. A feed should be an output of that record, not the place where teams invent or repair product truth.
For a waterproof commuter jacket in navy, size medium, the source record should preserve the variant's identity and offer state. A compact mapping might look like this:
| Source record | Merchant Center input | Why it matters |
|---|---|---|
Stable variant ID, such as JKT-001-NAVY-M | id | Lets Google recognize the same item across updates. |
Product-family ID, such as JKT-001 | item_group_id | Groups color and size variants without merging separate offers. |
| Product name plus useful variant details | title | Gives Google and the shopper a clear description of the item. |
| Variant landing page | link | Sends the click to the product the ad represents. |
| Primary variant image | image_link | Gives the ad a usable visual for the exact offer. |
| Current amount and currency | price | Must match the offer shown on the landing page and checkout. |
| Current stock state | availability | Prevents promotion of an item shoppers cannot buy. |
| Brand, GTIN, or MPN when applicable | Identifier fields | Helps Google match products and apply category-specific rules. |
| Internal category and Google taxonomy mapping | product_type and, when relevant, google_product_category | Separates your merchandising taxonomy from Google's category vocabulary. |
The Google product data specification marks attributes as required, conditional, or optional. Requirements vary by product, destination, country, and marketing method. A brand or GTIN is not a universal license to invent an identifier. Keep the identifier that the manufacturer or source system actually owns.
Give each variant its own price, availability, link, image, and identifiers when those values differ. Keep the parent relationship explicit. A title that says “navy medium” does not create a valid variant relationship by itself.
Set up a product listing ads campaign
Use this sequence for a clean first launch:
1. Prepare the account and store
Create or access Merchant Center, add business details, claim and verify your website, define the target country and language, and configure shipping and returns. Your landing pages need to show the offer a shopper can buy. Title, image, price, currency, and availability should agree across source data, page, structured data, and checkout.
2. Add one primary data source
Open Settings → Data sources → Product sources in Merchant Center, then select the source method that owns the normalized output. Upload a file, connect the ecommerce platform, use a Sheet, enable discovery, or configure the Merchant API. Keep supplemental data to narrow overlays, such as a custom label, while the primary source owns the product lifecycle.
3. Process and fix the first submission
Inspect processing results and product-level issue details. Correct invalid values, missing fields, inaccessible image URLs, duplicate IDs, variant errors, and source-to-page mismatches upstream. Resubmit or wait for the next scheduled fetch after the correction reaches the output.
4. Link Google Ads
Link the Google Ads account to Merchant Center, set up conversion tracking, and choose a Shopping or Performance Max campaign. Google says Shopping ads can be served by both campaign types. Standard Shopping gives a more explicit product-group and campaign structure. Performance Max can use more Google Ads inventory from one campaign, with control expressed through goals, assets, signals, budgets, and product data.
5. Define the initial product scope
Start with products that have reliable availability, margin, images, and conversion tracking. Use product groups or inventory filters to separate categories, price bands, brands, seasons, or custom labels. Give the campaign enough data to learn, then change budgets and bids in measured increments rather than rewriting the whole setup each day.
6. Launch and read two dashboards
Use Google Ads for campaign performance. Use Merchant Center for source processing, product status, destinations, and issue details. A campaign with clicks and conversions can still hide disapproved products. An approved product can still receive no impressions because campaign, query, budget, competition, or targeting do not make it eligible to serve.
Google's Shopping ads onboarding guide provides the current account-linking and campaign sequence.
Optimize in the right order
Optimization works better when eligibility and performance are separate workstreams.
First, protect eligibility
Fix the problems that stop products from serving:
- missing or invalid required and conditional attributes;
- unstable or duplicate IDs;
- broken
item_group_id, color, or size relationships; - price, currency, availability, or sale-date mismatches;
- inaccessible pages or images;
- policy, shipping, return, or checkout problems;
- low-quality images or prohibited overlays;
- products that are discontinued or out of stock but remain in the output.
Google's specification says incorrect categories, identifiers, variant attributes, images, and conflicts between the data source and website can cause disapprovals, limited eligibility, or display problems. Fix the earliest failed layer instead of rewriting a title when Google never received the file.
Then improve relevance and click quality
Once the product is eligible, improve the record that Google uses to match and render the ad:
- Put the product type, brand, model, and useful differentiators near the front of the title.
- Write descriptions that clarify material, fit, compatibility, use case, and constraints. Store important facts in structured attributes too.
- Map the most specific accurate product category and maintain a detailed internal
product_type. - Use a clear primary image that represents the offer. Add additional images when they answer a buying question.
- Keep variant landing pages, images, titles, price, and availability aligned.
Custom labels can segment products by margin, season, best-seller status, price tier, or inventory risk. They help you organize campaigns and budgets. They do not replace product attributes or guarantee a higher position.
Finally, measure controlled changes
Track feed completeness and issue counts beside impressions, click-through rate, conversion rate, revenue, cost, and return on ad spend. Compare product groups with similar intent and economics. Change one meaningful input at a time, record the source version, and give bidding systems enough time to collect data before drawing a conclusion.
For volatile catalogs, set freshness by field. Price, availability, and sale dates need the shortest update path. New products, titles, descriptions, images, and taxonomy can follow the approval workflow that owns them. A scheduled file that updates once per day may be fine for copy and still be too slow for stock that changes hourly.
Why an approved product may still be invisible
Treat these as four separate states:
| State | What it proves | What it does not prove |
|---|---|---|
| Submitted or fetched | Google received the file or API input. | The row parsed correctly or the product can serve. |
| Processed | Google parsed the item and built a product record. | The item passed policy, page, image, or destination review. |
| Approved | The item is eligible for a selected destination. | The campaign will show it for a query. |
| Visible | The item appeared on the selected surface. | The source will stay current or the offer will remain in stock. |
If a product is processed but disapproved, read the item-level issue. If it is approved but has no impressions, inspect campaign scope, budget, targeting, query relevance, competition, inventory, and destination settings. If an ad shows the wrong price or variant, compare the source row, product page, structured data, and checkout. A new upload cannot repair a page that sells a different offer.
This source-to-surface separation is where Catalog fits. Catalog is the product data layer for that work: we help brands structure product data, normalize identities and variants, keep live records synchronized, publish machine-readable product objects to AI shopping surfaces, and measure outcomes. Use Catalog upstream when the same product facts are fragmented across storefronts, PIM or ERP systems, supplier files, and channel exports. Then map a controlled product record to Google rather than maintaining a fragile one-off feed.
Read our Merchant Center glossary for the platform model, product feed management guide for the broader operating workflow, and product data quality guide for the audit layer behind reliable listings.
FAQ
Are Google product listing ads the same as Google Shopping ads?
Yes. Product Listing Ads, or PLAs, is the older name. Google currently calls the ad format Shopping ads. The current campaign types are Shopping and Performance Max.
Do I need a product feed to run Shopping ads?
You need product data in Merchant Center, but a traditional feed file is only one option. Google also supports online-store discovery, ecommerce platform connections, Google Sheets, manual entry in eligible accounts, and the Merchant API.
How often should a Google product data source update?
Match the schedule to the field. Update price and availability as often as those values change. A daily update can work for slower catalog content. Use a faster reliable path, such as automatic updates or the Merchant API, when a stale offer could create a mismatch or disapproval.
Why are products in Merchant Center but missing from my ads?
Being submitted or processed is not approval, and approval is not an impression. Check product issues, campaign scope, destination settings, budget, targeting, relevance, competition, and inventory in both Merchant Center and Google Ads.
