Is this only a JSON-LD validator?expand_more
No. Generic validators check whether markup is syntactically valid. ShopGox also compares Product, Offer, Review, AggregateRating, BreadcrumbList, metadata, and visible product content so you can find contradictions that syntax validators miss.
Which schema types matter most on an ecommerce product page?expand_more
For a sellable product page, start with Product and Offer. Then review BreadcrumbList, Review or AggregateRating when reviews are visible, and merchant listing fields such as price, availability, shipping, and return policy when your store can provide them accurately.
What fields are most often missing from product schema?expand_more
The common gaps are brand, SKU, GTIN or MPN, image arrays, priceCurrency, availability, canonical URL, variant attributes, and review counts that match the visible review widget.
Should I add Review schema if my product has no visible reviews?expand_more
No. Review and AggregateRating markup should reflect reviews that shoppers can see on the page. Adding hidden or unsupported ratings can create trust problems and structured data eligibility issues.
Does clean Product schema guarantee rich results?expand_more
No. Clean structured data improves the inputs search engines can evaluate, but rich results still depend on eligibility, crawlability, policy compliance, page quality, and Google's own display decisions.
How is this different from Google's Rich Results Test?expand_more
Use Google’s Rich Results Test to check supported rich-result markup, then use ShopGox to compare extracted structured data with visible product facts and inspect potential conflicts. Neither a valid test nor a ShopGox score guarantees Google will display a rich result.