Skip to content

Free Meta Muse shopping checker

Can Meta Muse shop your products?

Muse reaches a shop two ways: products flowing from catalogues into Meta, and its own browser agent working your product page. Enter a shop or product page and we check both, down to whether your size swatches have names.

24 checks on price, variants, basket, catalogue data and delivery, scored for one product page.

One shop or product page. Give us the shop home page and we find a product page ourselves. No email required.

The Schmitdy dolphin in a shopkeeper's apron ties a blank tag onto the one item on a harbour market stall that has none
Every item tagged, every choice named.

Free Meta Muse shopping checker

Enter a product page, or your shop's home page.

A product page gives the sharpest report. From a home page we follow one product link and say which page we read.

We fetch the public page you enter, and its contact page and robots.txt if we find them, for this check only. We do not keep the address or the page content in analytics or run records. A basic request receipt with a daily-changing coded network identifier limits abuse. The report stays in this tab unless you save it. Privacy policy. Private network addresses, sign-in details, unusual ports and unsafe redirects are rejected.

How the check works

Three questions, in the order the agent asks them.

We find a product page

Give us any page on your shop. If it has no product on it, we follow one product link and tell you which one.

We read it as Muse's agent would

Price, availability, every size and colour control, the add to basket control and your product structured data, scored by how often each one decides whether an item gets shortlisted.

We check the machine price against the human price

Stores that convert currency by location often keep the shop currency in their markup. We compare the two, because a catalogue that reads the wrong currency quotes the wrong price.

FAQ

Questions about Meta Muse Shopping Checker

How does Meta Muse read a website?
Meta says Muse's browser sub-agent sees an accessibility tree snapshot of the page rather than the raw DOM, and cannot run JavaScript in the page context. The browser is still Chrome, so the page renders and your scripts run. What matters is whether each fact reaches the tree as text and whether every control carries a name.
Do I need to server-render my site for Muse?
No. That was a common misreading of Meta's description. Ordinary visible text reaches the accessibility tree even inside a plain div. The failures that matter are facts locked in images or canvas, text inside aria-hidden regions, and controls with no accessible name.
Can I see Muse visits in my analytics?
Not cleanly. Meta's security post says that when Muse browses, 'it will appear as your activity', and we found no documented Muse user agent or referrer in Meta's public materials. That is why this checker scores your page rather than your traffic, and why the report ends with twenty questions to baseline by hand.
Are Shopify products already in Meta Muse?
Shopify's changelog says products are shared with Meta by default through Shopify Catalog, and Meta appears as an AI channel in the admin. Shopify documents a Meta channel rather than a Muse-specific route, so check the channel settings and treat Muse as one of the Meta surfaces those products reach.
Why does the checker care about my size swatches?
A swatch is usually a coloured square with no text. Unless it has an accessible name such as 'Size: UK 10', an agent knows a choice exists but not what it means, so it cannot answer 'do you have this in medium' or pick the right variant.