A System is a productised capability that runs against one connected
store. 6 Systems ship today, each with its own dashboard under
/<org>/<store>/systems/.
| System | What it does | Domain | |---|---|---| | Tracking Scanner | Full audit of the store's tracking setup in about 90 seconds. | Tracking | | SEO Auditor | Technical and semantic SEO audit of the storefront. | SEO | | Conversion Analyzer | CRO diagnosis built from real Shopify data, not benchmarks. | Conversion | | AEO Optimizer | Makes the brand citable by answer engines, and measures the citations. | SEO | | AOV Optimizer | Bundle suggestions ranked by measured lift. | Merchandising | | Web Vitals | Field performance — what real visitors experience, not a lab score. | Ops |
Each also has a marketplace page at /marketplace/systems/<slug> with
the longer description.
What a System actually is
Three things at once, which is why the word is not just marketing:
- A dashboard. A page under
/<org>/<store>/systems/<aeo|aov|conversion|seo|tracking|vitals>. - Agent tools. The specialists call into the same engine you see on that page, so asking @Otis about tracking and opening the Tracking Scanner give the same answer.
- A schedule. Systems keep running against the store rather than producing one report and stopping.
Tracking Scanner, publicly
The Tracking Scanner is the one System with a public entry point: any
storefront URL can be scanned at /scan/tracking
without connecting it. Sign-in is required, the result is a real scan of
a real storefront, and public scan artefacts are retained for 30
days before the captures and the submitter's hashed IP are purged.
What Systems do not do
They read what your Shopify scopes allow and nothing more. A System is
not a way around a scope you did not approve: if read_analytics was
never granted, the Conversion Analyzer works from what it can see and
says so, rather than inferring numbers.