Short answer. Merchant Center raises “Inaccurate availability status due to inconsistency between feed and landing page” on the account when the availability in your feed disagrees with your product pages across many products. Bring the feed and the pages into agreement, on the page including the structured data, resubmit the feed, and request a review; Google’s re-crawl usually finishes within 24 to 48 hours.
| Shown in Merchant Center as | Inaccurate availability status due to inconsistency between feed and landing page |
|---|---|
| Effect | Account-level risk |
| Where to find it | Products → Needs attention, then filter by this issue |
| Free check | Not something a feed file shows; see below for what the check can tell you instead |
What Merchant Center means by “Inaccurate availability status due to inconsistency between feed and landing page”
Google’s help page for the issue states the principle: someone who clicks a Shopping ad expects to see the same availability on the landing page as in the ad. When the feed and the pages disagree across many products, the item-level page-crawl mismatches become this account-level warning. The page lists the causes Google sees most, from IP-based availability to preorders sold as in stock to structured data that has not been updated, and says the re-crawl after a fix usually finishes within 24 to 48 hours. The availability specification states the rule the check enforces.
It is a warning with a deadline: unresolved, it leads to suspension. It also needs a review request after the fix, and Google’s page lists that as the third step.
Why it happens
- Stale feeds: a file uploaded once, or regenerated on a slow schedule, while stock moved.
- Structured data that ignores inventory: the theme says InStock for every variant.
- Preorder or backorder sold as in stock, or long fulfilment times undeclared.
- Location-dependent availability: pages that change by visitor IP or need a postcode first.
- Variant links opening the wrong variant, so the sold-out size’s row shows an in-stock page.
- Broken buy buttons or maintenance pages at crawl time.
How to fix it
In Shopify
Use a feed that follows inventory in near real time (Shopify’s channel and our integration both receive inventory changes as they happen), fix the theme’s product structured data so availability follows the selected variant, link rows to their variant URL, and once the item-level mismatches are gone, request the review from the account issue.
In WooCommerce
Serve a feed built at request time from live stock (our free plugin does) and schedule Merchant Center’s fetch as often as your plan allows; check the product page’s structured data per variation; make sure preorders and backorders are declared as such. Then request the review.
In a CSV or XML feed
Follow Google’s three steps: identify the problem products from the warning emails and the Needs attention filter and investigate why the feed and page diverged; update the availability values and resubmit the feed, by upload, API or platform; request a review once the values agree. Fix the update process, not just the values, or the warning returns.
How long until Merchant Center clears it
Item-level mismatches clear as Google re-crawls, usually within 24–48 hours of the fix. The account warning clears only after the review, which you request when the item-level issues are gone.
What FeedRobin does about it
The free feed check compares prices between the feed and a sample of product pages today, not availability, and the report does not claim otherwise; it does report every availability word no channel recognises. For connected stores the feed’s availability comes from live inventory on every sync and webhook, which removes the stale-snapshot cause; the theme’s structured data remains yours to check.
Questions merchants ask
What causes does Google list?
Its help page names, among others: location-based pages that change availability by visitor IP, preorder or sold-out products listed as in stock, variant mismatches, site maintenance, long fulfilment times, shipping restrictions, broken buy buttons, outdated structured data, postcode gates before availability shows, and colour mismatches between feed and page.
Do I request the review before or after fixing?
After. Google re-crawls the pages during the review, and a request made while the feed and pages still disagree fails and costs you the cooldown before the next one.
Will a feed that updates in real time prevent this?
It removes the most common cause, the stale snapshot. It does not fix a page whose structured data says InStock regardless of inventory; that is a theme problem, and Google reads the structured data first.
Sources
- How to fix: Inaccurate availability status due to inconsistency between feed and landing page — Google Merchant Center Help
- Availability [availability] — Google Merchant Center Help
- Product issues (Content API for Shopping): the issue codes and the titles Merchant Center shows — Google Merchant Center Help