Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt

Use this file to discover all available pages before exploring further.

Store Audit answers the question every merchant asks every morning: what is broken, underperforming, or quietly leaking revenue across my store right now? It lives at app.vortexiq.ai/v2/store-audit and it is the most-clicked button on the Actions hub. One scan. Every connected source. Findings ranked by revenue impact, not by alphabetical order or arbitrary severity. Unlike traditional site auditors that hand you a PDF of technical flags, Store Audit reads from every connector wired into your workspace — Shopify or BigCommerce for catalogue and order signals, Google Analytics 4 for traffic and behaviour, Google Search Console for ranking surface, Google Ads for paid spend efficiency, Stripe and PayPal for payment performance, Datadog and New Relic for infrastructure health, and more. Findings come back contextualised: not “page X has a missing meta description” but “16 e-commerce scripts in <head> blocking First Contentful Paint, projected revenue impact 0.7% conversion lift if removed.”

​
The five Store Audit actions

The headline button. One click scans every connected source, scores each finding against the severity model, and pushes the results to the Latest Findings dashboard and (by default) your Kanban Board. Runs are asynchronous — leave the page and come back when it is done. Typical run time is 4 to 12 minutes for 4 to 6 connectors; larger catalogues can take up to 25 minutes.
The live findings dashboard. Filter by severity (Critical, High, Medium, Low, Warning, Passed) and by source connector (Catalog, Theme, GA4, Ads, Klaviyo, and one chip per live connector). Each finding row shows the finding name, severity badge, source, the time it was first surfaced, and a Board button to push it to the Kanban Board.
Ask Viq walks a specific customer journey end-to-end — homepage to purchase, category to add-to-cart, cart abandonment recovery, and more — and reports every point of friction as a Kanban-ready task. Specify the device (desktop, mobile, tablet), locale, and customer profile (new, returning), or write a free-text journey description.
Runs a configured script of customer flows on every release event and surfaces any flow that regressed since the previous approved baseline. Catches theme regressions, schema regressions, broken redirects, and layout shifts before customers notice them. Wire it to a Shopify theme-publish webhook or BigCommerce theme-update webhook for automatic post-deploy checks.
The proactive action. Ask Viq reads your audit findings, Vortex Mind context, and SEO project to propose new landing pages or design changes optimised for sales. Each proposal includes a draft artifact, the reasoning behind it, a projected revenue impact range, and a Kanban-ready card for review.

​
Running a full store audit

1

Open Store Audit

Navigate to app.vortexiq.ai/v2/store-audit. Check the source filter rail to confirm that your expected connectors — Shopify, GA4, Google Search Console, Google Ads, Stripe, and so on — are visible.
2

Click Run Audit

Click Run Audit in the top right. The header cards switch to a “running” state. A progress strip across the findings table shows completion percentage by connector. An Agent Log on the right side streams the agent’s reasoning in real time.
3

Wait for results

The audit runs asynchronously. You can leave the page and come back. If a connector errors out — for example, an expired token — the run logs it as partial and continues with the remaining connectors. The header marks partial sources with an asterisk.
4

Review the header summary

When the run completes, four header cards refresh: Stores audited, Critical issues, Warnings, and Checks passed. A right-hand summary card shows your overall AI Intelligence Score — for example, 30 of 35 — so you can track absolute store quality from one run to the next.
5

Explore the findings dashboard

The findings table groups results by severity band. Use the severity tabs (All, Critical, High, Low, Warning, Passed) and source tabs (All Sources, Catalog, Theme, GA4, Ads, Klaviyo, …) to scope the view. Click any finding row to expand the full description, the list of affected items, the recommended fix path, and the history strip.
6

Push findings to the Kanban Board

Click the Board button on any finding to send it to your Kanban Board as a card. If automation rules are configured, findings route automatically to the right column, swimlane, or assignee the moment the audit completes — for example, critical findings to In Review for engineering review, SEO findings to a Marketing swimlane.

​
What the findings dashboard shows

The findings table groups every result into colour-coded severity bands.
SeverityBadge colourWhat it means
CriticalRedBlocking revenue right now. Act within 24 hours.
HighDark orangeHigh-impact issues to resolve this week.
MediumAmberIssues that should be in the resolution queue but are not yet bleeding revenue.
LowLight amberMinor issues — often cosmetic or efficiency-driven.
InformationalBlueState descriptions that do not need action but explain the store.
Checks passedGreenEverything that ran clean.
Each finding row shows the finding name, the severity badge, the source connector that surfaced it, when it was first detected, and the Board action. Click the row to open the per-finding panel, which includes the full description, the affected items list (every URL, SKU, or transaction the finding applies to), a recommended fix path — often a one-click action to open the right Vortex IQ tool with affected items pre-loaded — a Vortex Mind cross-link if the finding is downstream of a diagnostic report, and the finding’s history strip showing recurrence and prior resolution dates.

​
How severity is scored

Severity in Store Audit is a composite of three signals, not a single check rule:
  1. Detected impact — what is this finding actually doing to traffic, conversion, AOV, or revenue right now?
  2. Reach — how many URLs, products, customers, sessions, or transactions does it affect?
  3. Reversibility — how hard is it to undo if you act and turn out to be wrong?
The underlying score is inspectable on the per-finding detail panel and stored in Vortex Memory for retroactive analysis.

​
When to run a store audit

ModeCadenceUse case
ScheduledDaily (typically overnight)Drift detection, fresh findings for the morning briefing, low time-to-resolution on regressions
On-demandAfter every deployCatch theme regressions, schema regressions, and redirect-chain breakage immediately
On-demandBefore every campaignPre-flight check before Black Friday, seasonal launches, or paid-spend bursts
Every AI-generated change that comes out of a Store Audit finding — whether applied through Bulk Content Edit, an Ask Viq fix-and-deploy, or a Generate New Page proposal — goes through your approval queue before it touches the live store. The audit itself is strictly read-only: it never writes back to your storefront or to any connected connector.