Introduction
Accurate product data is essential for products to be eligible for Google Shopping ads and free listings. Submitted details can conflict with a store’s website, and an eligible product can still have a separate issue that prevents it from appearing. A product record starts with id, title, description, link, image_link, availability, and price; further attributes depend on the product and destination.
What product attributes are required for a product to be accepted in Google Shopping or free listings?
The seven starting fields identify the product, describe it, point to its landing page and image, and state whether it is available and at what price. They are a starting record, not a guarantee of acceptance. Google’s product data specification requires accurate, correctly formatted information to avoid disapprovals and display problems, while the applicable attributes vary by product and destination.
Before submitting a product, compare its details with the landing page, particularly information a customer would rely on when buying it. Google recommends matching submitted data to the page and requires merchants to follow its free listings policies. Eligibility permits a product to appear across Google surfaces; it does not guarantee that customers will see it.
What is the difference between required, conditionally required, and optional product data attributes?
Conditionally required attributes apply when the product or its destination calls for them. For variants, check whether item_group_id, color, and size apply rather than adding them indiscriminately or omitting them from products that need them. Google identifies variant-attribute errors among the problems that can prevent products from showing.
An optional attribute has a specific use without belonging on every product. For example, expiration_date sets a date when a product stops showing, which can be useful for a seasonal or limited-stock item. The expiration rule still applies if the product reaches its usual refresh limit sooner. The practical check is therefore product by product: confirm which attributes apply, then make their values accurate.
How do I supply my product data to Google—what is a data source, and what input methods and file formats are supported?
A data source, previously called a feed, is how product information enters Merchant Center. You can connect an online store or ecommerce platform, supply a file or Google Sheet, add products individually, or use the Merchant API. An account can have multiple data sources using different methods.
For a direct file upload, Merchant Center’s file instructions list .txt, .xml, and .tsv and allow files up to 4 GB. A direct upload does not sync later edits: you must submit the changed file again. Alternatively, Merchant Center can fetch an accessible file from an http://, https://, or sftp:// link. In a data source, use the same language for free-form text attributes and write multiword attribute names in the required form, such as image_link.
Choose the method by how your catalog changes. File-based sources suit relatively stable catalogs or systems that export full snapshots; the Merchant API can send changes to fields such as price and availability without resending the whole product. In Merchant Center, the Data sources tab shows each source’s upload method and provides an Update control for a manual refresh. If multiple sources submit the same product, Google associates it with the source that updated it most recently.
A feed is also a requirement of our Managed Ads service, with upload included in onboarding. Our Premium CSS service does not require you to provide us with a feed or migrate an account; that service distinction does not change the product data Google requires.
How often must I update my product feed, and what happens if my data is wrong or my product gets disapproved?
Update submitted information when the product’s price, availability, or other details change. Most products expire from Merchant Center 30 days after their last refresh; products added directly in Merchant Center are exempt from that rule. The 30-day limit is not permission to leave an incorrect price or stock status in place. A submitted expiration_date ends the product on that date or at the 30-day limit, whichever comes first.
You can refresh products by resubmitting a data source or scheduling uploads. For a file supplied by link, Merchant Center fetches it every 24 hours by default, and you can adjust that schedule. If a product is disapproved, correct the issue affecting it and refresh the source where necessary. Conflicts with the website, incorrect category or GTIN values, variant errors, and poor images can prevent display. An unavailable landing page or an incorrect checkout URL can also cause disapproval. Fixing the submitted field alone is insufficient when the website is the source of the conflict.
Where can I check whether a product is approved and visible?
Open the Products table in Merchant Center and read Status and Visibility separately. Status describes the product data as Approved, Disapproved, or Pending review; Visibility indicates whether the product appears in ads or free listings. The Products page also shows information such as price and availability, so you can compare what Merchant Center has with the current store listing.
An Approved product can still be Not Visible because another issue affects display, including a policy issue or an unavailable store view. Open the product details to investigate that issue rather than treating approval as proof that customers can see it. For a larger catalog, you can search the product list by attributes such as brand, GTIN, MPN, product type, or category.
Eligibility depends on current data and actual visibility
Google Shopping product data begins with the core record, but eligibility depends on the additional attributes that apply and on details that remain accurate across Merchant Center and the website. Keeping submitted information aligned with the store and checking both measures is the continuing work that keeps eligible products up to date.