How to create a Google Shopping feed step by step
A beginner-friendly guide to preparing your catalog, adding products to Merchant Center, and checking diagnostics without mixing clean product data with promotional creatives.
Julia Villegas

A Google Shopping feed is the file or URL that sends Google your product data: title, price, availability, landing page, image, and other attributes. If you are adding products to Merchant Center for the first time, the real task is not just uploading a file. It is preparing a catalog that is accurate, reviewable, and easy to maintain.
What a Google Shopping feed is
A product feed is a structured data source that Google Merchant Center uses to understand what you sell and how those products should appear across Google’s commerce surfaces. Depending on your setup, it can be a file, a scheduled URL that Google fetches, or another input method supported by Merchant Center.
Google’s product data specification defines the attributes that may be required for each item. Some fields are common to most online stores, such as product ID, title, description, link, image, price, and availability. Others depend on the product type, target country, language, or Merchant Center configuration.
For beginners, it helps to separate three terms that are often used interchangeably:
- Catalog: the full product database from your ecommerce platform, ERP, PIM, spreadsheet, or product file.
- Feed: the version of that catalog prepared for a specific channel, in this case Google Merchant Center.
- Data source: the source you add inside Merchant Center so Google can receive and process those products.
Creating a feed does not mean launching campaigns. Merchant Center reviews product data so items can become eligible for Google experiences, while Google Ads campaigns are configured separately. It also does not guarantee approval. Google can review your product data, policies, landing pages, images, and consistency between the feed and your store.
Why it matters before you build campaigns
In Google Shopping and Performance Max, the feed is one of the foundations of campaign quality. If titles are vague, prices do not match the website, links are broken, or the main image contains promotional overlays, the problem starts before any bidding strategy can help.
A clean product feed makes it easier for Merchant Center to interpret each item. It also makes troubleshooting simpler when diagnostics appear, helps you expand to more countries or languages, and allows you to build channel-specific feeds without rebuilding the catalog every time.
| Feed element | What it should do | Common mistake |
|---|---|---|
| ID | Identify the same product over time | Changing the ID in every export |
| Title | Describe the product clearly | Using internal names or generic labels |
| Link | Open the correct product page | Sending users to a broken URL or category page |
| Price | Match the landing page | Sending a different price than the store shows |
| Availability | Reflect real stock status | Marking out-of-stock items as in stock |
| Image | Show the product clearly | Adding prices, CTAs, badges, or promotional logos |
If you also advertise on Meta, TikTok, Pinterest, or other channels, it is normal to reuse parts of your catalog. But do not confuse product photography with ad creative. For Google Merchant Center, the main image should represent the product clearly and follow Google’s Merchant Center image requirements. Promotional frames, discount badges, price overlays, and calls to action are better suited to ad creatives, not the main image in your feed.
If you need branded product images with prices or offers for other channels, you can create them separately with the Templates Editor, while keeping a clean feed for Google.
How to create a Google Shopping feed step by step
Before you open Merchant Center, prepare your catalog. Most feed issues come from incomplete, inconsistent, or hard-to-update product data.
1. Choose which products to send first
You do not always need to upload your entire catalog on day one. A better first step is often a stable product set: items with stock, complete product pages, accurate prices, and clean images.
Fictional example: a footwear retailer has 8,000 SKUs but starts with 1,200 seasonal sneakers. The team excludes out-of-stock items, discontinued clearance products, and pages waiting for photography. That smaller first feed is easier to review, and any errors are easier to understand.
The selected product set should be commercially useful and operationally reliable. If you send products with missing images, unstable prices, or incomplete landing pages, Merchant Center diagnostics will usually reflect those issues.
2. Define stable product IDs
The product ID is the unique identifier for an item in your feed. It should remain stable over time. If a shoe variant is sent today as SHOE-123-BLACK-42, it should not become 123456 tomorrow just because you changed export tools.
Google uses the ID to recognize the product in future updates. Changing IDs unnecessarily can make an existing item behave like a new one during processing and review.
Good practices:
- Use unique IDs.
- Do not reuse the same ID for different products.
- Avoid randomly generated IDs that change on every download.
- Keep the same ID logic across your primary data source and any supplemental source.
This is especially important for stores with many variants. If size, color, or model options are handled inconsistently, diagnostics become harder to interpret and supplemental data sources become harder to match.
3. Review the basic product attributes
Required attributes vary by product, market, and account setup, so always check Google’s current documentation. Still, most first feeds rely on a core group of fields:
- id: unique product identifier.
- title: a useful product name written for shoppers, not only for internal teams.
- description: a clear explanation of the product without misleading text.
- link: the URL of the product page.
- image_link: the URL of the main product image.
- availability: the real stock status.
- price: price and currency matching the landing page.
- brand: the product brand, when applicable.
- gtin or mpn: product identifiers, when applicable.
- condition: product condition when required.
A good title does not need to be overloaded, but it should be descriptive. “Dress” is too broad. “Short sleeve floral midi dress” gives Google and shoppers more useful information. Avoid stuffing titles with promotional claims that do not describe the product itself.
Descriptions should also be practical. They can explain the material, use case, key features, size, or style, but they should not promise things that are not visible or true on the landing page.
4. Check links, price, and stock consistency
Merchant Center can compare feed data with the landing page. If the feed says a product costs $49.99 but the product page shows another price, you are likely to see issues. The same applies if the feed marks an item as in stock while the store shows it as unavailable.
Review these areas carefully:
- URLs that return errors.
- Product links that redirect to a category page instead of a product page.
- Variants that land on the wrong size or color.
- Prices without the correct currency.
- Prices that do not update when the store changes.
- Availability values that do not reflect real stock.
For larger catalogs, checking this manually is not realistic. This is where it helps to centralize cleaning rules, filters, and exports in a Feed Manager, so the product data is fixed before it reaches each channel.
5. Prepare clean images for Google
Your main product image should not be treated like a promotional banner. Google provides specific image requirements, and you should review the current documentation before publishing your feed. As a practical rule: show the product clearly, without added promotional text, discount badges, call-to-action copy, or logos that are not part of the product itself.
This matters if your marketing team already creates Meta Ads or TikTok creatives with sale labels, crossed-out prices, countdowns, or campaign frames. Those assets may be useful as ads, but they should not replace the clean product photography Merchant Center uses to identify the item.
Keep two layers of visual work:
- Product photo for Google: clean, accurate, and focused on the product.
- Ad creative for paid media: adapted to placements and allowed to include brand elements, price, offers, or campaign layouts where appropriate.
The examples gallery can help you separate creative advertising formats from clean catalog images.
6. Create a primary data source in Merchant Center
Once the catalog is prepared, create the data source. Google’s help documentation explains how to create a product data source in Merchant Center.
For a store that is just starting, the primary data source is usually the right foundation. This is the source that adds new products to Merchant Center. You can then update it on a schedule that makes sense for your catalog and operations.
When setting it up, check:
- Target country or countries.
- Feed language.
- Input method.
- File or URL Merchant Center will use.
- Fetch frequency if you are using a scheduled URL.
Language and IDs must be consistent. If you later use supplemental data sources, they need to match the products from the primary source correctly.
7. Use supplemental sources only to enrich existing products
A supplemental data source is not meant to add new products. Its role is to update or enrich products that already exist in the primary source. For example, you might use it to add custom labels, fill in missing values, or adjust attributes for a specific subset of products.
For this to work, product IDs must match. If an item has one ID in the primary source and a different ID in the supplemental source, Merchant Center cannot reliably connect the two.
Think of the primary source as the base product record, and the supplemental source as an enrichment layer. Do not use supplemental sources to cover up structural problems in the main catalog.
How to do it with AdMotion Export Channels
If your catalog comes from an ecommerce platform, a file, or multiple product sources, you can prepare the feed with Export Channels. AdMotion connects the catalog, lets you map fields, apply rules or sets, and publish a feed adapted to the channel specification.
A practical workflow would be:
- Connect the catalog from your store or product file.
- Map fields so your catalog data matches the attributes Google expects, such as title, link, price, stock, and image.
- Create rules or sets to exclude products without images, separate categories, or send only available products.
- Create the Google feed in the relevant export channel.
- Review errors and warnings with the feed analyzer against the channel specification.
- Copy the feed URL and add it in Merchant Center as a product data source.
This workflow does not guarantee product approval and does not replace Google’s review. It does help you send a more controlled feed to Merchant Center. If you manage multiple channels, the same catalog can support different formats and sets, so you do not have to mix Google Shopping requirements with Meta, TikTok, Pinterest, or other channel needs.
Final check before you upload the feed
Before registering the feed URL in Merchant Center, review a real sample of products. Do not only check the first row of a spreadsheet. Look at variants, different categories, expensive products, low-price products, promotional items, and products recently updated in your store.
Use this quick checklist:
- Does every product have a unique and stable ID?
- Does the title describe the product clearly?
- Does the link open the correct product page?
- Does the feed price match the landing page?
- Does availability reflect real stock?
- Is the main image clean and free of promotional overlays?
- Are excluded products removed by a clear rule?
- Does the feed language match the configured market?
- Does the primary source contain all products you want to add?
- Do supplemental sources, if used, rely on the same IDs?
After the first upload, review Merchant Center diagnostics. Some issues appear when the source is processed, while others can appear later after additional checks. Do not treat warnings as background noise. They often point to catalog quality problems or product eligibility issues that will be easier to fix if you document the root cause.
What to do this week
- Audit 20 products from your catalog. Choose different categories and check ID, title, landing page, price, stock, and image. If you find repeated errors, fix the pattern at the source.
- Define your first Google Shopping product set. Start with available products that have complete pages and clean images. You do not need to solve the entire catalog before learning the process.
- Separate clean product photos from promotional creatives. Keep Google images free of overlays, and use discount frames, highlighted prices, or campaign visuals in channel-specific ad creatives.
- Create or review your primary data source in Merchant Center. Make sure it is the source that adds products and that language, country, and IDs are consistent.
- Check diagnostics after the first upload. Prioritize issues that block products, then document the field or rule you need to fix so the same issue does not return.
A well-prepared Google Shopping feed is not just a technical upload. It is the structure Google uses to understand your catalog. The cleaner the source data is, the easier it becomes to keep products updated, diagnose errors, and expand to more channels without rebuilding everything from scratch.
Frequently asked questions
Does creating a Google Shopping feed automatically approve my products?
No. Creating and uploading a feed lets Merchant Center receive your product data, but Google still reviews products, landing pages, images, and policy compliance. A well-structured feed can reduce common errors and make diagnostics easier, but it does not guarantee approval, visibility, or campaign activation.
Can I use a supplemental data source to add new products?
No. The primary data source is what adds new products to Merchant Center. A supplemental source is used to update or enrich products that already exist, such as adding custom labels or filling specific attributes. Product IDs must match the primary source, and language settings need to be compatible.
Can the main feed image include discounts or promotional text?
For the main product image, use a clean photo that represents the product without added prices, calls to action, promotional overlays, or extra logos. Discount-led visuals can be created for ads on other channels, but they should not replace the product image sent to Merchant Center.
Sources
Related posts

TikTok Smart+: how to prepare your catalog, control and creatives
TikTok Smart+ can combine campaign automation with catalog-based ads, but performance still depends on product data, stock, landing pages, creative assets and measurement. Here is what to prepare before you switch it on.

Pinterest gift catalog: how to prepare it for Christmas
Learn how to prepare a Pinterest gift catalog for Christmas: what product data to check, how to build product groups and how to keep stock, images and links from hurting your shopping ads.

How to create a TikTok product feed step by step
Creating a TikTok product feed is not the same as copying your Google or Meta catalog. Learn how to adapt IDs, prices, availability, images and video to TikTok’s feed requirements.