Appearance

Product Feed: monitor your Merchant Center feed ​

The Shelf Edge Product Feed report shows the state of your Google Merchant Center product feed: the items it lists, what each fetch changed, which feed checks fail, and whether Google's crawlers came back for the products that changed. Also called a Merchant Center feed monitor or a product feed audit.

EdgeComet fetches the feed you add to Merchant Feed Re-cache every hour by default, and you can set it as often as every 5 minutes. It keeps the current state of every item and records which fields each fetch changed.

EdgeComet re-caches product pages whose price, stock or title changed at high priority, which means bots read the new values. You add only the feed URL: EdgeComet needs no access to your Merchant Center account.

The Product Feed report, Overview tab, for the last 7 days. Items in the catalog 105,105, up 68 since fetch 1287. Items moved 2,298: 45 removed, 113 new, 2,140 changed. Changed items Google re-fetched 57.0%, 1,220 of 2,140 changed items. Items with a P0 issue 127, 0.1% of the catalog, 11 P0 codes. The What moved in the last 7 days card shows a bar of Removed 45 (2.0%), New 113 (4.9%) and Changed 2,140 (93.1%), and a table of items and Google re-fetches per change: Removed 45 and 21, New 113 and 113, Price 2,124 and 1,204, URL 17 and 16, Title 2 and 1, GTIN 1 and 1, Validation issues 1 and 1

What the report shows ​

The report has two tabs: Overview and Feed items. Overview reads the items EdgeComet stored from your feed and Google's fetches of your product pages.

The header sets the period: Last 24h, 7 Days (the default) or 30 Days. It applies to the cards, What moved, the Change column of Issues and Waiting for Google. Fetch history always covers the last 30 days. Demand on issues covers Search Console's last 28 days and the last 30 days of AI fetches.

Cards: how big is the catalog, and did Google see the changes? ​

  • Items in the catalog: the items in the feed now, with the change since the last fetch before the period, such as +68 above the footer "since fetch 1287".
  • Items moved: items removed, new and changed in the period, such as "45 removed - 113 new - 2,140 changed".
  • Changed items Google re-fetched: of the items whose page fields changed in the period, the share that a verified Googlebot, AdsBot or StoreBot fetched after the change. Red at 0%.
  • Items with a P0 issue: items that carry any P0 issue, such as a missing price or an invalid link. See Feed check severity from P0 to P3.

View on Items in the catalog, Changed items Google re-fetched and Items with a P0 issue opens the matching rows in the Feed items tab.

What moved: which items changed, and in which field? ​

This card splits the period's movement into Removed, New and one row per changed field: URL, Title, Price, Sale price, Sale price dates, Availability, Availability date, Link in scope, Currency, Brand, GTIN, Product type and Validation issues. Only fields that changed get a row.

A page field is one that shows on the product page: the link, title, price, sale price, sale price dates, availability and availability date. A change to a page field makes EdgeComet re-cache the page and counts toward Google re-fetches.

Google re-fetched counts the items a verified Googlebot, AdsBot or StoreBot fetched after the change, or after the removal on the Removed row. An item that moved several times in the period is one row. An item that changed several fields at once counts under each of them.

Issues: what is wrong with the feed and its items? ​

EdgeComet runs every feed check on every fetch. The Issues card lists them, worst first, in two lenses:

  • What changed: checks grouped into New, Worse, Improved, Open, nothing to compare and Resolved, against the catalog before the period.
  • All issues: checks grouped by category: Feed Health, Item Data, Links & Scope and Coverage.

The Issues card on the What changed lens. Worse, 3 checks: P2 Availability uses a non-standard spelling, marked Whole feed, +68, on 105,105 items (100%) with 63.4K GSC impressions and 3.6K AI fetches; P2 Missing value: Google product category, Whole feed; P2 Missing value: GTIN, +2, 7,156 items (7%). Improved: P0 Missing value: image link, -2, 81 items. Open, nothing to compare, 6 checks: P0 Feed entries with no id, P1 Changed items Google has not re-fetched on 922 items, P1 Pre-cache is failing on the landing page on 65, P1 Duplicate id, the second entry was dropped, P2 Left the feed, still indexable in the latest crawl on 45, and P2 No Google fetch in the last 30 days on 55. Footer: 19 checks ran and found nothing, 2 checks were compared and did not move

Each row shows Sev, Issue, Change, Items, GSC impr and AI fetches. Rows rank by severity, then by demand. See Feed check severity from P0 to P3. Two chips mark special rows:

  • Whole feed: every live item carries the issue. It is one wrong column at the source, not a list to work through.
  • Feed-level: the check counts feed files, not items.

Click a row for its details and the affected items. See Merchant Center feed checks and feed errors. A feed with no failing check reads "Nothing to fix in this feed."

Waiting for Google: which crawlers came back for changed items? ​

For AdsBot, StoreBot and Googlebot, this card shows the feed items each crawler fetched in the period, the items that changed, and the changed items it fetched after the change. Coverage is the share of changed items the crawler fetched after the change. A fetch counts only from a verified IP address.

The Waiting for Google card for the last 7 days: AdsBot fetched 28,394 items and 687 of 2,140 changed items after the change, 32.1% coverage; StoreBot fetched 3 items and none of the changed ones, 0.0%; Googlebot fetched 51,645 items and 979 changed items after the change, 45.7%. Below it, the Feeds card lists one feed (name blurred) with status Not modified, 105,105 items, last fetched 2 hours ago

Open the worklist lists the changed items no Google crawler has fetched since the change, oldest change first.

Feeds: did each feed import? ​

The Feeds card lists each feed file with its status, items and last fetch. Statuses:

  • Fetched: EdgeComet read the whole feed.
  • Not modified: the feed server answered that nothing changed since the last fetch, and the stored items stay as they are. EdgeComet asks the server for changes only, which keeps repeated fetches light.
  • Failed: the fetch failed, with the reason beside the status. See Feed errors.
  • Removed: the feed URL left the rule.
  • Not fetched yet: EdgeComet has not fetched the feed since you added it.

Fetch history: what did each fetch change? ​

Daily bars split each day's movement into Removed, New and Changed, over the last 30 days. The table lists the newest fetches with Fetch, When, Result, Items found, Removed, New and Changed. Two or more fetches in a row that the feed server answered as not modified fold into one line, such as "20 fetches not modified".

The Fetch history card. Daily stacked bars of removed, new and changed items from Sep 25 to Oct 25, 2026, with spikes on Oct 3 (about 30K removed and 15K changed), Oct 7 (about 26K changed and 6K removed) and Oct 9 (about 38K new), bars of 10K to 17K changed from Sep 30 to Oct 2, small bars on most other days and none after Oct 20. The table below holds one folded line, 20 fetches not modified, 2 days ago to 2 hours ago, and the caption 20 of 243 fetches since Sep 25, 2026

Click a fetch number to open the items that fetch touched. The menu in the card header exports the chart or its data.

Feed items tab: what does each item in the feed show? ​

The Feed items tab lists every item still in your feed, with its price, availability, issues, last cached copy and last Google fetch. It is the same table as Data Explorer > Feeds > Merchant feed. See Merchant feed: every product in your feed.

The Feed items tab of Product Feed with the filter Removed from feed Is not set and 105,105 results. Columns: URL (blurred), Title, Price, Availability, Issues, Page fields changed and Last cached. The first rows are Globo Lighting Robby table lamp at 117.8, a Grohe K700 steel sink at 1,838.91, a Hansgrohe Raindance shower channel cover and a Grohe K700 steel sink set, all In Stock, with issue chips Non-standard availability, No product category and, on the sink set, No GTIN

How to read it ​

  • Low Coverage on Googlebot or AdsBot: Google has not fetched many changed product pages since the change, and may still hold the old price or stock. See Product pages against the feed.
  • A Whole feed chip: fix the column once in your feed export.
  • A spike in Items moved or Fetch history: a large share of the catalog changed at once. That is often a feed format change, not a product change.
  • Removed items still indexable: products that left the feed still have indexable pages. See the Coverage check "Left the feed, still indexable in the latest crawl" in Coverage examples.

What to do next ​

"No product feed yet": add your feed ​

Cause: no feed URL is on the Merchant Feed Re-cache rule, or the rule is off. The report shows Add a product feed.

Fix: add your feed. See Add your Merchant Center feed. Until the first fetch completes, the report shows only Issues and Fetch history.

Where to find it ​

In the dashboard: E-commerce > Product Feed, with the tabs Overview and Feed items. Add or change feeds in Configuration > Caching > Merchant Feed Re-cache.

Related Articles