Most site audits treat every site the same way. Title, meta, H1, canonical, schema, run the same checks on all of them. That misses 80 percent of what actually matters on a Shopify store, a Squarespace portfolio, a Wix small-business site, a Webflow brochure, a Ghost newsletter, or a BigCommerce shop. Each of those platforms has its own failure modes, its own admin paths, its own schema conventions, and its own performance surface.
The Platform Audit detects which platform the site is running on, then runs the platform-specific checks.
What gets detected
Ten platforms currently. Shopify, BigCommerce, Squarespace, Wix, Webflow, Ghost, HubSpot CMS, Drupal, Magento / Adobe Commerce, Framer. WordPress is deliberately not in this set; it routes to the WordPress + WooCommerce Audit and the WordPress Security + Stability Audit which go deeper than this tool would.
Detection uses public HTML fingerprints (Shopify's cdn.shopify.com, Squarespace's Static.SQUARESPACE_CONTEXT, Wix's _wixCIDX, and so on). The first matching platform wins, ordered by specificity so heavily-customized sites don't get misclassified.
What each platform gets checked for
Shopify
Active theme handle, Online Store 2.0 (JSON templates + section groups), Checkout Extensibility migration status, Product JSON-LD on PDP, Shop Pay button, multi-currency / country selector, app-script bloat count. Sites with more than eight Shopify app scripts loading are flagged because every app embed is a separate blocking request.
Squarespace
Version 7.1 vs 7.0 detection (7.0 sites can't move to 7.1; a rebuild is required if you want Fluid Engine), Commerce signals, custom CSS bundle size (large inline CSS is a common Squarespace performance trap), SEO site title config, cookie banner status, typography-source count.
Wix
Editor X vs classic Editor, Wix Stores detection, Velo custom-code presence, parastorage bundle count (Wix ships one of the heaviest client-side runtimes on the web; the audit flags the counts), SEO Wiz configuration, Wix Analytics.
Webflow
CMS collection usage, Webflow Ecommerce, interactions.js loading (dequeue opportunity if IX2 isn't used), jQuery detection (Webflow ships jQuery by default; disable if unused), Lottie file presence.
Ghost
Default Casper theme vs custom, Members portal activation, Koenig editor cards, Portal signup CTA, Article JSON-LD.
BigCommerce
Stencil (modern) vs Blueprint (legacy) theme, headless Storefront API usage, Product JSON-LD, Optimized One-Page Checkout signals.
HubSpot CMS, Drupal, Magento, Framer
Each gets a smaller check set focused on the one or two things that most often go wrong on each platform.
The fix prompt
For each finding, the emitted prompt asks the LLM to produce fixes in the platform's native language. Liquid snippets for Shopify. Section config for Squarespace. Custom code blocks for Wix. Custom-code embeds for Webflow. Handlebars partials for Ghost. Stencil config for BigCommerce. HubL for HubSpot. Twig for Drupal. PHTML for Magento. React components for Framer. Plus admin paths inside each platform where relevant.
The prompt also includes a migration-consideration section. If the signals suggest the site would be better served on a different platform (a Shopify store with 12 custom apps might actually be a Woo + managed-host candidate; a Squarespace portfolio outgrowing 7.0 might be an Astro or Eleventy candidate), the prompt surfaces that option with reasoning. It never forces migration; just offers the option when the data supports it.
Why one audit for many platforms, not many audits for many platforms
Fair question. The answer is maintenance. Each platform-specific check list has 6 to 10 items. A unified router means the shared scaffolding (URL normalization, HTML fetching, check rendering, fix-prompt assembly, Fix / Audit this / Learn pill integration) is one code path, not ten. When a new platform is added, a new function goes in the PLATFORM_CHECKS map and nothing else changes.
SEO for specific platforms (people searching "Shopify audit tool" or "Squarespace SEO audit") is handled by the blog layer, not by duplicate tool pages. This post plus follow-up per-platform posts cover those keywords while the tool itself stays one maintained surface.
The honest limitations
The tool can only see public HTML. It can't read your Shopify app configurations, your Squarespace Commerce cart logic, your Wix Velo functions, your Webflow CMS collection schemas, your Ghost membership tier pricing, your BigCommerce tax configuration. For any of that, the audit calls out what it couldn't see rather than pretending to know.
Related reading
- WordPress + WooCommerce Audit for WordPress and WooCommerce
- WordPress Security + Stability Audit for hardening the same
- Competitor Contrast for comparing multiple platforms against each other
- Site Migration Capture when the right fix is to change platforms
- Restaurant Site Audit and Law Firm Site Audit for vertical-specific layers on top of any platform
Fact-check notes and sources
- Shopify theme documentation on Online Store 2.0, Checkout Extensibility, and Shop Pay.
- Squarespace documentation on 7.1 vs 7.0 and the Fluid Engine migration path.
- Wix Help Center on Editor X and the Wix Velo dev-mode runtime.
- Webflow University on interactions.js and jQuery dependencies.
- Ghost.org documentation on Portal, Casper, and Koenig.
- BigCommerce Stencil developer documentation.
This post is informational, not platform-consulting or legal advice. All platform and vendor names are trademarks of their respective owners, referenced under nominative fair use. No affiliation is implied.
