Suggestions

The Suggestions page is where DynoWeb turns store data into a prioritized list of what to fix and exactly how to fix it.

DynoWeb does the diagnosis and writes the playbook. You stay in control of the change — every suggestion comes with a step-by-step guide so you (or your developer) can implement it confidently in the Shopify admin or in code.

What It Does

Suggestions has two starting points.

Quick Store Check scans the live theme for easy wins. It works even before the store has any traffic, so new merchants get value on day one.

Traffic Analysis uses real visitor behavior — clicks, frustration signals, scroll depth, journey drop-offs — to surface higher-confidence opportunities based on what shoppers are actually doing on the store.

Once suggestions are generated, they're grouped into four tiers so users know what to tackle first:

• Quick Wins — low-effort, high-leverage fixes ranked first.
• Strategic — bigger improvements with strong evidence behind them.
• Ambitious — high-impact changes that need more planning.
• Needs Triage — items that don't fit the primary tiers and warrant manual review.

Every suggestion card carries the recommendation, the page it applies to, the evidence behind it, an expected impact signal, a difficulty rating (Easy / Medium / Hard), and a confidence rating based on how strong the data is.

Opening a suggestion takes the user to a dedicated detail page — this is where DynoWeb explains how to fix it.

The Implementation Guide (the heart of every suggestion)

DynoWeb does not push code into your theme. Instead, every suggestion comes with a complete Implementation Guide that gives users two routes to applying the fix:

Theme Editor Steps — a clean, numbered walkthrough written for non-technical users. Each step describes exactly what to click, where to find the setting in the Shopify theme editor, and what value to enter. No code required.

Code Changes — for developers or merchants who prefer editing the theme files directly. Each file change shows the file path, the exact code to add or modify, and a one-click Copy button so the snippet can be dropped straight into the theme editor or a Git workflow.

Every guide also includes:

• A short Summary explaining what the change does and why it matters.
• A How to Verify section so users can confirm the fix landed correctly after applying it.
• An Expected Outcome describing the metric or behavior they should see improve.

If a suggestion doesn't yet have a fully detailed guide, users can click Enrich with AI to generate a developer-ready, theme-aware plan on demand. The enrichment uses the merchant's actual theme files as context, so the steps and code refer to the right sections, classes, and templates.

For behavior-driven suggestions (rage-click hotspots, drop-off pages, frustrated journeys), the detail page also opens an Investigation Dossier that deep-links into matching session replays — so users can watch the issue happen before deciding what to change.

Other Card Actions

Beyond opening the guide, each suggestion card supports:

• Open Preview — see the affected page on the live storefront.
• Matching Replays — jump straight to recorded sessions that triggered the suggestion.
• Dismiss — remove suggestions that don't apply to the store.

How To Use It Best

The intended flow is:

1. Run Quick Store Check first, especially for newer stores. It surfaces theme-level fixes that don't need traffic.
2. Once the store has been collecting events for a few days, run Traffic Analysis to layer in evidence-backed recommendations from real visitor behavior.
3. Sort the list by Quick Wins and start there. They're the smallest changes with the strongest leverage.
4. Open any suggestion to read the Implementation Guide. Pick the route that fits — Theme Editor for no-code, Code Changes for development work.
5. Apply the change yourself, then use How to Verify to check that it landed.
6. Track results over time as new metrics flow in. Suggestions that no longer apply will fall out of the list automatically.

The page works best when treated as a decision queue: review the priority, read the evidence, follow the guide, ship the change, and confirm the outcome.

Workflow Tools

The bottom of the page helps users manage and audit the suggestion pipeline.

Analysis Runs shows recent engine jobs and what each run produced — useful for understanding when the last refresh happened and whether anything is queued.

Preview Candidates (Pending Publishing) lists engine-generated suggestions that have been validated against baseline metrics but haven't been promoted to the main list yet. Filter by target, modification type, source, or sort order to inspect what's waiting in the pipeline.

A Note on How DynoWeb Applies Changes

DynoWeb does not auto-apply suggestions to the live theme. Every change is something the user — or their developer — implements with the guidance DynoWeb provides. This keeps the merchant in full control of what ships, while still removing the hardest part of CRO work: knowing what to change and exactly how to change it.

Good Help-Guide Positioning

"Suggestions is where DynoWeb turns theme checks and visitor behavior into a prioritized to-do list — each one paired with a step-by-step guide and ready-to-paste code so you (or your developer) can implement the fix confidently in the Shopify admin or theme files."