We read the page the way the agent does
We turn your HTML into the same kind of view an accessibility tree gives: roles, names, text and structure, with anything marked aria-hidden removed.
Free Meta Muse website checker
Can Meta Muse read your website?
Muse's browser agent does not look at your page. It reads an accessibility tree: a list of named nodes. Enter one public page and we score what survives that translation, with the exact markup to change.
17 checks, one score, every finding tied to markup on your page.
One public page, plus its contact page and robots.txt. No email required.
What a person sees, and what the tree exposes.
Free Meta Muse website checker
Enter the public page you want Muse to understand.
Your home page is a good start. A location, service or menu page tells you more about the facts an assistant quotes.
How the check works
Three questions, in the order the agent asks them.
We score what an agent can act on
Unnamed controls, facts locked in images, text hidden from the tree, missing contact facts, structured data and your stated position on Meta's agents. Each check is weighted by how often it decides a task.
You get the markup, not a lecture
Every finding shows what we saw in your page and the specific change to make, ordered so the first fix is the one worth doing first.
The Muse toolkit
Four checkers, two agents.
Meta Muse Shopping Checker
Selling products? Check a product page for price, variants, the add to basket control and catalogue data.
Instinct AI Website Checker
22 checks across reachability, completion and the accessibility tree, with the fix for each.
Instinct AI Shopping Checker
27 checks on the path from product page to delivered order, scored for one product page.
FAQ
Questions about Meta Muse Website 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.
What does the Meta Muse Website Checker score?
Accessible names on every control, icon-only buttons, readable text hidden inside aria-hidden regions, link destinations, image descriptions, form labels, landmarks, whether your phone, email, address and hours exist as text, structured data, and whether your robots.txt takes a position on Meta's agents.
Is this the same as an accessibility audit?
It overlaps on purpose, because an agent reading an accessibility tree fails where assistive technology fails. It is narrower than a full WCAG audit and focused on the facts and controls an assistant needs to answer and act.
How to show up in Meta Muse: the 2026 playbook · All free tools