{"id":4386,"date":"2026-07-28T17:02:02","date_gmt":"2026-07-28T14:02:02","guid":{"rendered":"https:\/\/ivitskiy.com\/blog\/?p=4386"},"modified":"2026-07-28T17:02:02","modified_gmt":"2026-07-28T14:02:02","slug":"google-product-feed-explained","status":"publish","type":"post","link":"https:\/\/ivitskiy.com\/blog\/en\/google-product-feed-explained\/","title":{"rendered":"Google product feed: what is inside and how not to break it"},"content":{"rendered":"\n
In short:<\/strong> a feed is your catalogue as a table in a format Google can read. Most problems come not from complexity but from exceeded limits and invalid values, all of which can be checked numerically: id up to 50 characters, title up to 150, description up to 5000, brand and mpn up to 70. Availability accepts exactly four values, price requires a currency in ISO 4217 format, and links must start with http:\/\/ or https:\/\/. One date for the calendar: the minimum image size of 500\u00d7500 pixels starts being enforced on 31 January 2027.<\/div>\n\n\n\n

The word «feed» frightens store owners more than it deserves to. It is not programming. It is a table where each row is a product and each column is one of its characteristics. The difficulty is not in building it. The difficulty is that Google checks it formally: not «is this understandable» but «does this fit the rule».<\/p>\n\n\n\n

One word first, because it appears everywhere below. An attribute is a column in your table<\/strong>, that is, one characteristic of a product: title, price, availability. When the console reports «an error in the title attribute», it means «something is wrong in the column holding the name».<\/p>\n\n\n\n

Base attributes and their exact limits<\/h2>\n\n\n\n

The figures below are taken from the product data specification<\/a> as of 28 July 2026. This is the set practically every product needs. Beyond it the specification carries conditionally required fields that switch on for particular cases: apparel, size and colour variants, used goods. If you sell any of those, run the base check first and then open the full specification linked above.<\/p>\n\n\n\n

\n
Attribute<\/th>What it is<\/th>Limit or format<\/th><\/tr><\/thead>
id<\/code><\/td>Product identifier<\/td>Up to 50 characters, unique within the account<\/td><\/tr>\n
title<\/code><\/td>Product title<\/td>Up to 150 characters<\/td><\/tr>\n
description<\/code><\/td>Description<\/td>Up to 5000 characters<\/td><\/tr>\n
link<\/code><\/td>Product page address<\/td>Must start with http:\/\/ or https:\/\/<\/td><\/tr>\n
image_link<\/code><\/td>Main image address<\/td>Same protocol rule; at least 500\u00d7500 pixels (enforced from 31.01.2027)<\/td><\/tr>\n
availability<\/code><\/td>Availability<\/td>Exactly four values: in_stock, out_of_stock, preorder, backorder<\/td><\/tr>\n
price<\/code><\/td>Price<\/td>A number plus a currency in ISO 4217 format<\/td><\/tr>\n
brand<\/code><\/td>Brand<\/td>Up to 70 characters<\/td><\/tr>\n
mpn<\/code><\/td>Manufacturer part number<\/td>Up to 70 characters, needed when the product has no GTIN<\/td><\/tr>\n<\/tbody><\/table><\/figure>\n\n\n\n

Three errors from that table deserve their own note, because they come not from carelessness but from how stores are built. A title longer than 150 characters: everything fits on the product page, not everything fits in the feed. Availability written in plain language («in stock», «on order») instead of the four permitted values: that is how the store database holds it. And a price with no currency, because in the database it is just a number.<\/p>\n\n\n\n

The last one is worth showing, because «ISO 4217 format» explains nothing until you see it. Correct: 499.00 USD<\/code>. Incorrect: 499.00<\/code> or $499<\/code>. What is required is the three-letter currency code, not a symbol and not a word.<\/p>\n\n\n\n\n\n\n\n

One date for the calendar: 31 January 2027<\/h2>\n\n\n\n

The specification states directly that a product image must be at least 500\u00d7500 pixels, and that enforcement of this requirement begins on 31 January 2027. For a store this defines a concrete window: if your catalogue was photographed long ago and the images are small, you have time to reshoot or regenerate them calmly rather than in an emergency.<\/p>\n\n\n\n

Sizing the problem takes ten minutes: take 20-30 random products and look at the size of the main image. If small ones turn up, the task goes into the plan now, while it still costs hours rather than impressions. Just do not mistake sizing for checking: a sample tells you whether a problem exists, not that the whole catalogue is clean. Before the date itself the catalogue has to be swept in full, automatically.<\/p>\n\n\n\n

How to audit your feed in ten minutes<\/h2>\n\n\n\n
    \n
  1. Export the feed into a spreadsheet<\/strong> and add a column with the title length. Sort descending: anything above 150 lights up immediately.<\/li>\n
  2. Do the same for description<\/strong> (limit 5000), brand and mpn<\/strong> (70 each) and id<\/strong> (50).<\/li>\n
  3. Build a summary of the availability column.<\/strong> You should see exactly four distinct values and nothing else. Any fifth one is an error.<\/li>\n
  4. Confirm every price carries a currency<\/strong> in ISO 4217 format rather than a bare number.<\/li>\n
  5. Filter for links<\/strong> that do not start with http. This is the fastest win: it is fixed in bulk and removes an entire class of disapprovals.<\/li>\n
  6. Check that ids are unique.<\/strong> Duplicates appear when several catalogue sources are merged, and they break rows unpredictably.<\/li>\n<\/ol>\n\n\n\n

    After the fixes, wait. Per the documentation a recrawl usually clears within 24-48 hours<\/a>. Checking sooner tells you nothing, and it is exactly what creates the impression that the fixes are not working.<\/p>\n\n\n\n

    If spreadsheets are not your thing<\/h3>\n\n\n\n

    The list above assumes you can export the feed and turn it around in a spreadsheet. Without that access the console gives you the same result: it lists your products with their states and spells out the cause for each. The order is the same either way: first see what Google actually named, then go and fix it. That way you do not spend an evening rewriting titles when the real cause sits in the links or the price.<\/p>\n\n\n\n

    This is not the «simplified» route, it is the correct sequence for anyone. The spreadsheet earns its place when there are many causes and they have to be fixed in bulk.<\/p>\n\n\n\n

    Why «approved» does not yet mean «good»<\/h2>\n\n\n\n

    Limits are the floor for admission, not a recommendation. A 150-character title passes the check, which does not mean a title should be 150 characters long: in a shopping ad the user sees its beginning, so the word that matters belongs at the front rather than the end.<\/p>\n\n\n\n

    And separately, a common misuse of availability. When a product needs to come off the shelf temporarily, stores tend to mark it out_of_stock. The documentation forbids this outright: «Don’t use out_of_stock when you don’t want your product to show»<\/a>. Availability describes availability, not visibility. To stop showing a product that is in fact for sale there are separate attributes: pause for a break of up to 14 days, and excluded_destination to remove it from particular placements.<\/p>\n\n\n\n