Stored-data catalog prioritization
Know which products deserve attention next
Catalog Health recomputes priorities from stored product snapshots, audit state, readiness scorecards, recommendations, and Technical SEO findings so your team can focus on the catalog work already supported by Vittorious data.
| Product | Stored reason | Next action | Rerun? |
|---|---|---|---|
| Linen Field Jacket SKU-4471 | Shopify data changed after last audit | Review open recommendations | No |
| Wool Runner 03 SKU-2089 | Audit evidence older than threshold | Decide if another run is worthwhile | Maybe |
| Cotton Crew Tee SKU-1182 | Thin description, unclear variant data | Strengthen product-page content | No |
| Trail Pack 40L SKU-7704 | Unsupported performance claim in copy | Qualify or remove claim before publish | No |
- A fresh live Google Search or Shopping request happens only when a merchant starts another Evidence-backed Run.
- Manually refresh Catalog Health after meaningful catalog work to recompute the queue without requesting fresh Search or Shopping evidence.
Supported health labels
Work the reason, not just the score
Supported health labels tell the team why a product surfaced and what kind of follow-up is appropriate.
Needs attention
Open recommendations or Technical SEO findings give the team an existing action to review.
Changed after audit
Stored Shopify product data changed after the last audit, so prior recommendations may need another look.
Outdated
Existing audit evidence is old enough for the merchant to decide whether another Evidence-backed Run is worthwhile.
Weak
Stored readiness and recommendation data points to material product-page work, such as a thin description or unclear variant information.
Claim risk
An unsupported or conflicting claim needs evidence, qualification, or removal before it can support copy.
Healthy
Stored data does not currently surface a higher-priority catalog action.
Proof module
See stored reasons become a prioritized catalog queue
A staged queue distinguishes a changed product, outdated evidence, a weak description, and claim risk, then names the next merchant action.
Four health states, four different next actions
Stored product, audit, readiness, recommendation, and Technical SEO records place a changed product, an outdated audit, a weak description, and an unsupported claim in separate health states.
Linen Field Jacket
Stored reason: Shopify product data changed after the last audit. Prior recommendations may need another look.
Owner-ready next action
Review open recommendations against the updated product data before requesting new evidence.
Wool Runner 03
Stored reason: Existing audit evidence is old enough to consider whether another Evidence-backed Run is worthwhile.
Owner-ready next action
Decide whether the product justifies a fresh merchant-triggered run in one selected geo/language context.
Cotton Crew Tee
Stored reason: Readiness and recommendation data points to a thin description and unclear variant information.
Owner-ready next action
Strengthen the product description and clarify variant data using existing findings before requesting new evidence.
Trail Pack 40L
Stored reason: An unsupported or conflicting claim needs evidence, qualification, or removal before it can support copy.
Owner-ready next action
Qualify or remove the unsupported claim before publishing updated product copy.
Evidence
Stored product, audit, readiness, recommendation, and Technical SEO records place each SKU in a separate health state.
Gap / Risk
A flat product list hides why each SKU needs attention and can send the team toward fresh research before existing work is reviewed.
Recommended Action
Show the supported health label, stored reason, owner-ready next action, and whether the merchant should use existing findings or start another Evidence-backed Run.
Stored-data workflow
Keep maintenance work tied to stored evidence
Recompute after catalog work
Product imports, Technical SEO audits, gap analysis, and a merchant-triggered refresh can recompute health from stored Vittorious data.
Sort by the reason for attention
Filter and sort product health to separate changed products, outdated evidence, weak pages, and claim risks.
Use the work already available
Review open product-data, content, Technical SEO, and claim-safety actions before requesting new external evidence.
Start a fresh run deliberately
When new market evidence is warranted, the merchant starts another Evidence-backed Run for one product in one selected geo/language context.
Monthly report boundary
Give the monthly review a useful agenda
Monthly reports summarize stored Vittorious data: approved improvements, products needing attention, claim risks avoided, usage fields, status and action metrics, and conservative next actions. They do not add fresh Search or Shopping evidence.
- Show completed and pending catalog work without presenting activity as an external result.
- Bring weak descriptions, unclear variants, open Technical SEO findings, and claim risks into the next planning discussion.
- Keep recommendations conservative when stored evidence does not support a stronger conclusion.
Stored data, not live monitoring
Monthly reports aggregate work already captured in Vittorious. They do not trigger new Google Search or Shopping requests or imply continuous market monitoring.
Catalog Health
Decide what needs repair before buying fresh evidence
Use Catalog Health to organize stored findings, then choose the products whose changes or outdated evidence justify another merchant-triggered run.