Why a page cannot be read · not_a_product
The page is not a product page
The page was read successfully. Nothing on it identifies it as a product, because it probably is not one.
The page was read successfully, but it is not a product page.
§01 · what is actually happening
What is actually happening.
The read worked and the markup carried no indication that this page describes something purchasable.
For a homepage, a category listing, an article or an about page, that is correct and expected. The check requests one page, and on most sites that page is not a product page.
Where it is wrong is a genuine product page whose markup does not say so, which reads to a machine exactly like a page about nothing in particular.
§02 · what it costs
What it costs.
For a page that is not a product, none at all. This is a description rather than a fault.
For a product page that does not identify itself, the same cost as carrying no structured data: an assistant asked about that item does not find it here.
§03 · what would change it
The fix.
Nothing, if the page is not meant to be one. If it is a product page, the markup on it does not identify it as such, and adding a schema.org Product block is what closes that gap.
Who does it. Nothing, unless the page is meant to be a product. If it is, a schema.org Product block is what closes the gap.
Check your own site.
One request, one verdict, no account. If this is the finding you get back, the page above is the one that applies.
See what a machine seesThe other findings