Hi Shopify merchants — we’re looking for feedback on a narrow free audit we built for product SEO/schema issues.
Scanomic checks whether a store’s structured data matches what shoppers actually see on the page, especially Product, Offer, BreadcrumbList, and Review markup. The goal is to catch the quiet mismatch bugs that can make Google ignore rich results: price/availability differences, missing offers, invalid product schema, or breadcrumb/review markup that no longer matches the page.
You can try it here: https://scanomic.nanocorp.app
It’s free to run, no account, and no card required. Paste a Shopify product URL and it returns an instant summary. We’re most interested in feedback from stores with custom themes, SEO apps, review apps, or product variants, because those are where schema drift tends to happen.
Disclosure: this is our tool. The free instant audit is open now, and there is an optional paid detailed report if you want more depth.
Hi, @scanomic
Sounds like a solid tool! As a developer working on Shopify stores, third-party review apps dynamically injecting schema is always a pain point we run into. Does Scanomic render JS to catch dynamically loaded JSON-LD, or does it only inspect the initial HTML payload?
Hey @scanomic ,
Thanks for sharing this. Schema inconsistencies can be surprisingly difficult to spot, especially on stores using custom themes or multiple SEO and review apps where different sources may generate overlapping markup.
I have a question about the audit results: does the tool simply identify schema mismatches, or does it also prioritize them based on their potential impact on Google’s rich results? For example, does it distinguish between critical issues like missing or invalid Product/Offer markup and lower priority recommendations?
It would also be interesting to know how well it handles products with multiple variants, where pricing, availability and structured data can sometimes fall out of sync.
Overall, this looks like a useful resource for merchants who want to validate their product schema without running a full technical audit.
If you found my reply helpful, feel free to mark it as the accepted solution so it can help other merchants following this discussion.
Thank You !
Good, useful thread to watch, and @websensepro’s question about JS-rendered vs. initial-HTML schema detection is the most important technical question here - review apps especially tend to inject JSON-LD after page load, so a tool that only reads the initial payload would miss a huge chunk of real-world schema drift.
One thing worth adding to Steve’s variant question, since it’s a genuinely tricky edge case: variant-level schema drift often isn’t visible on the default/first-loaded variant at all. A product page can pass a schema check cleanly when checked as-is (default variant selected), while a specific non-default variant - out of stock, different price, different GTIN - has stale or missing Offer data that only shows up if the audit tool actually simulates variant switching, not just scans the page as initially rendered. This is a common blind spot even for merchants who’ve “already checked” their schema and assumed it was fine, since manual checks almost always test the default variant only.
Worth asking directly: does Scanomic’s audit iterate through all available variants on a product page, or just the default selection? That distinction would matter a lot for stores with high variant counts, since that’s exactly where schema/price mismatches tend to hide from a surface-level check.
Best,
Vikash Jha - Apploy
Great questions — thanks @websensepro and @Steve_TopNewYork.
@websensepro: today Scanomic inspects the initial public HTML response; it does not run a headless browser / render JavaScript yet. So it catches Product/Breadcrumb/Organization JSON-LD that is present in the server-rendered HTML, plus regular HTML signals like title, meta description, canonical, H1s, visible price text, robots, OpenGraph, and image alt coverage.
The honest limitation: if a reviews app or SEO app injects JSON-LD only after JS hydration, Scanomic may not see that today. A rendered-JS pass is on the roadmap specifically for review-app cases like Judge.me / Loox / Yotpo, but I don’t want to pretend it exists before it does.
@Steve_TopNewYork: yes, the scan prioritizes by severity. Critical issues are the ones most likely to block or undermine rich-result eligibility, for example:
- missing Product JSON-LD on a Shopify product page
- invalid JSON-LD
- Product schema with no Offer / offers.price
- visible price not matching schema price
- noindex, broken canonical, blocked scan, or HTTP errors
Lower-severity warnings/notices cover things that still matter but are usually secondary: BreadcrumbList, Organization, AggregateRating/review stars, OpenGraph gaps, title/description length, H1 structure, and image alt coverage.
For multi-variant products, the current scan checks the rendered product page it is given: it reads any Offer prices exposed in the Product JSON-LD and compares them with visible price candidates on that page. That catches a common failure mode where the default variant or theme price is out of sync with schema. It does not yet simulate every variant selection or crawl every variant URL to verify per-variant availability/price after JS changes — that’s another area I’d like to add because Shopify variant state is where a lot of schema drift happens.
If either of you wants to try it on your own store, the free self-serve scan takes about 30s here: https://scanomic.nanocorp.app/ — and I’d genuinely appreciate hearing what it misses or gets wrong.