Skip to main content
After a run, the Feed health tab lists every product that had a problem — what the problem was, whether the product still published, and what you can do about it. A number on the tab is the count of rows waiting for you. This is the page to read after your first generation. Most catalogs have some gaps in them, and until you look here you cannot tell whether ten products or a thousand are affected.
Feed health is what Rogus found in your product data before sending anything. It is not Google’s opinion. If you send this feed to Merchant Center, Google’s own decision on each product is on the In Google tab — and the two can disagree, because Google checks things Rogus cannot see, such as whether the price on your product page matches the feed. See Send to Merchant Center.

​
The Status column

Every row carries a status. It answers one question: what did this cost me? Skipped is the one that costs you sales, so those rows come first.
A Fixed row is usually one of two things: a fallback you applied, or copy written by AI content fill. Either way the row stays in the table so you can read what is in effect and undo it.

​
The Reason column

Plain text saying what is actually wrong: No description, No image link, Title is 180 characters; Google’s limit is 150. One row is one product and one problem. A product missing both a description and an image appears twice, because they are two different fixes.

​
Fixing things

There are two places a problem can be fixed, and the right one depends on the problem.

​
In Shopify

For anything genuinely missing, the real fix is the product itself. Add the description, add the image, set the category. Rogus tells you which products are affected so you know where to go. This is the better fix in almost every case: the same content is what your shoppers read.

​
In Rogus, with a fallback

For some attributes Rogus can offer a fallback — a second source used when the first is empty. Press Apply fallback on the row, or select several rows and apply it to all of them at once. The clearest example is description: falling back to the product title publishes the item instead of skipping it.
A fallback is a stopgap. A title used as a description is thin content, and Google reads descriptions to decide when to show your product. Rows fixed this way keep showing as Fallback rather than disappearing, precisely so they do not look solved.
Some problems have no fallback at all. There is no substitute for a product image — Rogus says so on the row rather than offering something that would not work.

​
Warnings on published items

These do not cost you an item today, but Google may reject or downgrade it later:
  • Title or description too long — Google’s limits are 150 and 5,000 characters
  • A link that is not a full URL — it must start with http:// or https://
  • A value outside Google’s allowed list — for example, an availability Google does not recognise
  • Too many additional images
  • availability is preorder or backorder without an availability date — Google wants the ship date
  • An availability date set on an item that is not a preorder — Google ignores it

​
Products left out by your plan

Different from skipped items, and reported separately: if your catalog is bigger than your plan allows, the feed keeps your oldest products and stops at the limit. The run tells you how many were left out. Those products are simply absent from Google, with nothing wrong with them. See Plans.

​
The 200-row limit

The health tab lists up to 200 rows. If a run has more problems than that, the tab says so. The cap is on the list, not on the fixing. A bulk fix applies to what you selected, and the next run reports the next 200.

​
Blank feeds

An XML or CSV feed you built yourself gets a much smaller version of this tab: only fields you marked required can skip an item, and there are no format warnings or suggested fallbacks. Rogus does not hold your own file to Google’s rules. See Custom feeds.