Which website platforms does Visibility Mesh work with?
The Visibility Mesh scan reads any public website, whatever it is built on. The Shopify app and the done for you AI Visibility Setup work only on Shopify. On Shopify and WordPress we can also make the changes ourselves and manage the work month to month. That is Monthly AI Visibility Management, sold by quote. You or your developer apply the fix plan on Webflow, custom built sites and every other platform. A rescan then shows what changed.
Our own website runs on Shopify. We make changes ourselves only on Shopify and WordPress, and everywhere else we give your developer an exact change to make. The scan needs no login, no plugin and no admin account. It reads your public pages the way an AI crawler receives them, and it writes nothing to your site.
What works on every platform
The free scan and the paid scans
The free scan reads up to five key pages of any public website, and it emails you a scorecard with the top issues and their fix steps. The Essential, Advanced and Agency plans read 100, 150 and 400 pages on every scan. Each delivers a report, a fix plan and a detailed audit, and you apply the fixes. The Full Assessment reads up to 400 pages once and adds an ordered roadmap. Prices are on the pricing page.
The crawler check
On every platform the scan checks your robots.txt for eight crawlers, one at a time. From OpenAI it checks GPTBot, OAI-SearchBot and ChatGPT-User. From Anthropic it checks ClaudeBot, Claude-SearchBot and Claude-User. From Perplexity it checks PerplexityBot and Perplexity-User. Google-Extended is reported on its own as a control for Gemini training and grounding. It never counts as a block, since Google documents that Google-Extended has no crawler of its own.
The fix plan and the rescan
The fix steps are written for the platform the scan recognizes. A WordPress site gets steps for a WordPress developer. After you change something, scan again at the same depth. A rescan shows what changed in the score and in what a crawler can read. It does not show that any AI answer changed. Two scans of an unchanged site usually land within about 2 points of each other.
Platform by platform
| Platform | The scan reads it | The report names the platform | Who applies the fixes | Catalog upload | We make the changes, by quote |
|---|---|---|---|---|---|
| Shopify | Yes | Yes | You, the Shopify app on its Growth plan, or us in an AI Visibility Setup or Monthly AI Visibility Management | Yes | Yes, in an AI Visibility Setup in English or in Monthly AI Visibility Management |
| WordPress | Yes | Yes | Your developer, or us in Monthly AI Visibility Management | No | Yes, in Monthly AI Visibility Management |
| WooCommerce | Yes | Yes | Your developer, or us in Monthly AI Visibility Management | No | Yes, in Monthly AI Visibility Management |
| Webflow | Yes | Yes | Your designer or developer | No | No |
| Wix | Yes | Yes | You, in the Wix editor | No | No |
| Squarespace | Yes | Yes | You or your developer | No | No |
| BigCommerce | Yes | Yes | Your developer | No | No |
| Magento or Adobe Commerce | Yes | No, it is labeled custom | Your developer | No | No |
| Headless, Next.js and React sites | Yes, rendered like a browser | Partly | Your developers | No | Quoted for headless Shopify |
| Other custom built sites | Yes | Labeled custom | Your developer | No | No |
We checked this table against our own engine and Shopify app on September 26, 2026. Visibility Mesh changes websites itself only on Shopify and WordPress.
Shopify
The Visibility Mesh Shopify app runs the same engine inside your admin. On its Growth plan it applies each fix you approve and lets you undo it. It writes product and collection titles, descriptions, SEO fields, image alt text and tags. It also writes care and fit facts and can publish FAQ pages and blog posts. It cannot write theme files, robots.txt, llms.txt, redirects or navigation. You or your developer make those changes from the steps in the report.
Do you want the structure built by hand? The AI Visibility Setup for Shopify works in a copy of your theme, in English, and you approve each change before it goes live. It is sold by quote, and so is Monthly AI Visibility Management, where we make the changes for you.
WordPress and WooCommerce
The scan recognizes WordPress and WooCommerce. It writes its fix steps for a developer on that platform, and there is no plugin to install. On WordPress, WooCommerce stores included, we can also make the changes ourselves and manage the work through Monthly AI Visibility Management, which is sold by quote. The catalog upload cannot read a WooCommerce product export today. A WooCommerce store should choose a plan or the Full Assessment rather than a Catalog Assessment.
Webflow, Wix and Squarespace
The scan recognizes all three. On Webflow the fix steps go to your designer or developer. On Wix they are written for the Wix editor. The scan also reads Wix pages that need JavaScript to show their content. On Squarespace the steps are written for the site owner. We do not change sites on any of the three ourselves.
BigCommerce and Adobe Commerce
The scan recognizes BigCommerce and writes steps for a BigCommerce developer. It reads Magento and Adobe Commerce stores well enough. It just does not know their name yet, which is on us rather than on Magento. So the report labels them custom and writes general steps. Neither platform's product export works in the catalog upload yet.
Headless, Next.js and custom builds
The scan renders JavaScript the way a browser does before it scores a page. Its fix steps go to the developers who own the application. A headless Shopify store is recognized as Shopify. We quote the work on a headless Shopify store after a scan, and you can ask for that quote on the Managed AI Visibility page. On other custom builds your developers apply the fix plan.
Who applies the fixes
On Shopify and WordPress we can apply the fixes ourselves as part of Managed AI Visibility, which is sold by quote. Everywhere else your developer applies them from our fix plan, and a rescan shows what changed. That way your developer keeps the keys to the site. For measurement in managed work we ask for read access to Search Console and analytics as a restricted user, and you can remove it the day the work ends.
Catalog uploads and which exports they read
The Catalog Assessments and the Agency plan accept a product export. The upload reads Shopify and Matrixify exports as CSV or XLSX. It reports how many of your products carry a description, an SEO title, an SEO description and an image. It cannot read WooCommerce, BigCommerce or Magento exports yet. Stores on those platforms should choose a plan or the Full Assessment instead.
JavaScript rendering and what the scan sees
The scan renders each page in a browser engine before it scores it. When rendering fails, it falls back to a plain fetch. So the scan can see content that a crawler without JavaScript would miss. Your page source shows what that crawler receives. Password protected sites cannot be scored. Neither can pages behind a login, a consent wall or a firewall that blocks the scan. In those cases you get a crawl diagnosis instead of a score.
Questions people ask
Does Visibility Mesh work on BigCommerce stores?
The scan works on BigCommerce stores, and the catalog upload does not. The scan recognizes BigCommerce, reads the live pages and writes fix steps for a BigCommerce developer. The Catalog Assessment cannot read a BigCommerce product export today. It reads Shopify and Matrixify exports only. Visibility Mesh does not change BigCommerce stores itself. For a BigCommerce store, a plan or the Full Assessment gives you the findings and an ordered fix plan.
Does Visibility Mesh recognize Magento or Adobe Commerce stores?
It scans them, but it does not recognize the platform by name yet. The scan reads Magento and Adobe Commerce storefronts like any public website and labels them custom. Its fix steps are then written for a general web developer. They do not name Magento settings. The catalog upload cannot read a Magento export, and Visibility Mesh does not change Magento stores itself.
Does the Visibility Mesh scan render JavaScript?
Yes, it renders each page in a browser engine before it scores it, with a plain fetch as a fallback. So the scan sees content that JavaScript adds after the page loads. A crawler that does not run JavaScript sees only the HTML your server sends. View the page source yourself and check that anything critical is there. For React and Next.js sites, the fix steps are written for the developers who own the application.
Does Visibility Mesh work on custom built or enterprise CMS websites?
It works on their public pages, with limits. The scan reads any public website. When it cannot recognize the platform, it labels the site custom and writes fix steps for a general web developer. A firewall, a consent wall or a login can stop the scan. You then get a crawl diagnosis instead of a score. On a large site the scan reads up to the page depth of your plan, so it reads a sample of the site. On custom built sites your developer applies the fix plan, and a rescan shows what changed.
More answers about scans, plans and data are in the Visibility Mesh FAQ.
Next step
Start with the free scan of up to five key pages, which needs no card and no call. If your own team will do the work, get the implementation plan, which lists every fix in order. If you want us to make the changes on Shopify or WordPress, ask for a quote. If you are not sure what you need, tell us what is going wrong.