This checklist is for ecommerce stores that already get traffic but are not turning enough of it into orders. It helps you decide where conversion is breaking first: traffic intent, product-page confidence, cart friction, checkout, performance, accessibility, or tracking.
By Deep Digital Ventures WebsiteAdvisor team. Created and reviewed by ecommerce/CRO practitioners who audit Shopify, WooCommerce, and custom storefronts for qualified traffic, product-page clarity, checkout reliability, performance, accessibility, and measurement gaps.
Methodology: This checklist was assembled from hands-on ecommerce audits, manual mobile checkout tests, analytics review, and current Google and W3C documentation. The source guidance checked for this revision includes people-first content, spam policy, title-link, product data, Web Vitals, event, and accessibility docs.[1][2][3]
Do not start with a theme redesign. Start by proving whether qualified shoppers can find the right product, understand the offer, trust the store, and complete checkout without new uncertainty.
Audit These 6 Things in Order
- Match traffic intent to the landing page before judging page design.
- Check whether the product page answers the buying questions above the decision point.
- Confirm trust, delivery, returns, reviews, and support are visible where uncertainty happens.
- Test cart and checkout on mobile and desktop with a real order path.
- Segment the diagnosis by product type instead of treating every template the same.
- Fix the first measurable drop-off, then retest the same path before buying more traffic.
Use four evidence sources before changing layouts: query and landing-page data, ecommerce event flow, lab and field performance data, and a manual checkout test for anything analytics cannot explain. Each section below gives you a pass/fail test and the next action to take.
Start With Traffic Quality
Pass/fail test: The page passes if its main queries, ads, or campaigns match the product or collection a shopper sees first. It fails if research visitors, broad category searches, or mismatched ads are being judged against a purchase target. Next action: sort one high-traffic landing page into product intent, research intent, brand intent, or wrong-page intent before changing design.
Low conversion is not always a design problem. It can be a mismatch between the visitor’s intent and the page they land on. The Search Console Performance report shows queries, pages, devices, clicks, impressions, CTR, and average position, so use it to separate product-intent traffic from research traffic before judging a product page.[4]
- Organic query and landing page: if the query is "how to choose running shoe size" and the landing page is a product detail page, expect lower purchase intent than a model-specific query.
- Source and path: compare
view_item,add_to_cart,begin_checkout, andpurchaseby source or campaign using recommended ecommerce events.[5] - Paid traffic destination: send model, variant, or offer-specific ads to the matching product or collection page, not a generic category page.
- Device split: check mobile and desktop separately because speed and layout problems often appear on one device class first.
- Content intent: do not score buyers’ guides, sizing pages, or care guides against the same purchase conversion target as product pages.
Use this mini-workflow for one high-traffic landing page before making sitewide changes.
- Open the page in search data and list the main queries that send clicks to it.
- Open the same page in analytics and check whether users reach
view_item,add_to_cart,begin_checkout, andpurchase. - Run the URL in PageSpeed Insights and note whether field data is available from the Chrome User Experience Report.[6]
- Complete one mobile test order with a real product, shipping address, discount code if one is active, and every payment method the store offers.
- Write one diagnosis: intent mismatch, product-page uncertainty, performance delay, accessibility blocker, cart friction, checkout friction, or tracking gap.
Anonymized audit example: In a Shopify apparel audit, the highest-spend ad group sent qualified shoppers to the right product family, but the product page still lost them before add-to-cart. The selected color did not update the image, the size guide opened away from the product decision, and the delivery estimate appeared only after checkout began. The diagnosis was not "redesign the store"; it was "variant confidence and delivery clarity are missing before add-to-cart."
| Observed pattern | Likely diagnosis | Next audit action |
|---|---|---|
High search clicks, weak view_item | The landing page may not expose the expected product clearly enough. | Rewrite the title, first product block, internal links, and above-the-fold category filters. |
Strong view_item, weak add_to_cart | The product page is not answering price, fit, variant, shipping, return, or trust questions. | Audit product facts, images, reviews, policy summaries, and add-to-cart visibility. |
Strong begin_checkout, weak purchase | Cart or checkout is adding cost, account, payment, coupon, address, or error-message friction. | Test checkout on mobile and desktop with a real order path. |
| Analytics shows no clear drop-off | Event tracking may be incomplete or firing on the wrong interaction. | Check ecommerce events and tag triggers before making design changes. |
Audit Product Page Clarity
Pass/fail test: The page passes if a mobile shopper can identify the product, variant, price, availability, delivery expectation, return rule, and next step without hunting. It fails if the shopper needs a policy page, extra tab, or checkout step to understand a basic purchase condition. Next action: fix the first missing fact closest to the add-to-cart decision.
Product pages should answer buyer questions before the shopper has to hunt for details. Product data guidance names many of the same facts shoppers look for: price, availability, review ratings, shipping information, variants, and return information.[9] Markup can help search results reflect the offer, but the visible page still has to make the same information easy for people to confirm.
| Product page element | Audit question | Evidence to check |
|---|---|---|
| Product title | Does it name the item, model, material, size, variant, or use case? | Compare the page title, H1, product feed title, and the queries that send clicks. |
| Images | Do images show scale, variants, details, packaging, and real use? | Check mobile cropping, thumbnail order, alt text, and whether the selected variant changes the image. |
| Price | Is the current price obvious before add-to-cart? | Check sale price, currency, subscription price, bundle price, and any minimum order condition. |
| Availability | Does the page clearly show in-stock, preorder, backorder, or out-of-stock status? | Compare visible page copy with feed and merchant values so search promises and product-page promises match. |
| Shipping and returns | Can shoppers understand delivery cost, timing, return window, and return fees before checkout? | Check the product page, cart, checkout, policy page, product data, and feed for conflicts. |
| CTA | Is the add-to-cart action visible, specific, and consistent after variant selection? | Test disabled variants, sold-out states, sticky buttons, and mobile keyboard or screen-reader focus. |
| Accessibility | Can a keyboard user choose a variant, read errors, and add the item to cart? | Use WCAG 2.2 checks for labels, focus order, focus visibility, error identification, and input assistance.[10] |
For performance triage, use Web Vitals thresholds as a pass-or-fix check: Largest Contentful Paint should occur within 2.5 seconds, Interaction to Next Paint should be 200 milliseconds or less, and Cumulative Layout Shift should be 0.1 or less at the 75th percentile.[7] INP became an official Core Web Vital on March 12, 2024, replacing First Input Delay as the responsiveness metric.[8]
If shoppers need to open several tabs or visit a policy page to understand a basic purchase condition, the product page is carrying hidden friction. Rewrite the page so the first decision area answers what the item is, whether it fits the shopper’s need, what it costs, when it can arrive, how returns work, and what happens after add-to-cart.
Review Trust Signals Near the Decision Point
Pass/fail test: The page passes if proof appears next to the exact moment of doubt: price, fit, compatibility, shipping, return risk, or payment. It fails if trust lives only in a footer, homepage, or generic reviews block. Next action: move the strongest product-specific proof beside the decision it supports.
Trust signals work best near the moment of uncertainty. Search features can show ratings, shipping, availability, and returns, but the shopper needs that proof on the product page too. Put product-specific evidence near the price, variant picker, delivery estimate, and add-to-cart button.
- Reviews should attach to the exact product, variant, or collection being sold, not only to the store as a whole.
- Return policy copy should summarize the real policy in plain language and link to the full policy when details matter.
- Customer service options should be visible before checkout when the product has sizing, compatibility, installation, or customization risk.
- Shipping timelines should be stated before checkout and match the delivery promise used in ads, feeds, and product data.
- Security and payment reassurance should support the checkout decision without replacing product facts.
- Brand story should stay below purchase facts unless origin, materials, manufacturing, warranty, or support directly affects the buying decision.
For higher-risk products, add proof that reduces the exact risk. Apparel needs size charts, fit notes, model details, fabric closeups, and return clarity. Electronics need compatibility, specs, warranty terms, setup help, and support access. Custom products need production steps, proofing rules, delivery timing, and a visible contact path before payment.
Find Cart and Checkout Friction
Pass/fail test: Checkout passes if a shopper can edit the cart, understand total cost, choose delivery, apply or reject a discount code, fix errors, and pay without surprise. It fails when a new condition appears after the shopper has already committed effort. Next action: reproduce the weak path on the device and payment method where the drop-off is largest.
Checkout problems often hide behind averages. Test the full purchase flow on mobile and desktop with a real product, real shipping address, active discount code, and each live payment method. Field performance data can explain speed and interaction delays, but only a manual order test will expose unclear coupon states, address errors, surprise shipping costs, and account prompts.
- Cart editing: shoppers should be able to change quantity, variant, and cart contents without losing progress.
- Shipping: cost and delivery expectations should appear before the payment step whenever possible.
- Accounts: if account creation is required, explain that before checkout; if guest checkout is available, do not hide it.
- Discount codes: show whether a code was applied, expired, invalid, or excluded from the item in the cart.
- Payment: confirm that the available payment methods fit the product price, country, and customer device.
- Errors: field-level messages should explain exactly what needs to be fixed and remain visible after submission.
- Accessibility: address, payment, and validation errors should not be only color-based or hidden from keyboard users.
| Checkout signal | What to inspect | Fix priority |
|---|---|---|
| Cart views are high, checkout starts are low | Shipping threshold, coupon field, tax estimate, cart editing, and trust copy. | Clarify cost and remove uncertainty before checkout. |
| Checkout starts are high, payment info is low | Account requirement, address form, shipping method choice, and page errors. | Reduce form friction and show the next required step. |
| Payment info is high, purchases are low | Payment declines, final cost changes, unsupported wallets, and error handling. | Audit payment gateway logs and reproduce the failed path. |
| Purchases are high on desktop but weak on mobile | Mobile keyboard types, sticky checkout buttons, interaction delays, layout shifts, and focus order. | Fix mobile checkout usability before increasing mobile ad spend. |
A checkout page should reduce uncertainty with every step. If a shopper learns the real shipping cost, account requirement, delivery range, or return condition only after beginning payment, the audit should mark that as checkout friction, not normal abandonment.
Segment Conversion Problems by Product Type
Pass/fail test: The audit passes if each high-value product type has evidence that matches its buying risk. It fails if one template treats a refill item, premium product, custom product, and gift product as the same decision. Next action: choose the product group with the most traffic, spend, or revenue and audit that template first.
Do not let one product template make every buying decision look the same. A refill product, premium comparison product, custom product, and gift product need different evidence, even if they all sit inside the same Shopify collection or WooCommerce category.
| Product type | Likely conversion need | Audit the page for |
|---|---|---|
| Low-cost repeat item | Fast reorder, subscriptions, bundles, and a clear shipping threshold. | Saved quantity, multipack pricing, reorder path, subscription terms, and low-friction checkout. |
| Premium product | Proof, warranty, detailed specs, financing if already offered, and stronger reviews. | Comparison table, customer photos, technical details, warranty summary, delivery care, and support access. |
| Custom product | Process explanation, preview, production timing, revision rules, and support contact. | Customization fields, proofing workflow, file requirements, turnaround language, and error handling. |
| Gift purchase | Delivery date confidence, packaging details, gift message support, and easy returns. | Cutoff language, recipient privacy, gift receipt options, packaging photos, and return instructions. |
The audit should identify which products deserve richer pages. If one product drives most paid spend, organic clicks, or revenue, give that page deeper proof before rewriting a long tail of low-traffic products.
What to Fix First
Pass/fail test: Your fix list passes if the first item names a page, a drop-off, the shopper uncertainty behind it, and the evidence that will prove the change worked. It fails if it starts with a redesign, new app, or campaign increase without naming the conversion break. Next action: fix the closest cause of the first measurable drop-off and retest the same path.
- If queries are broad or informational, fix landing-page intent before judging product-page design.
- If
view_itemis strong butadd_to_cartis weak, fix product facts, price, stock, variant clarity, shipping, returns, and trust signals. - If
begin_checkoutis strong butpurchaseis weak, test account rules, shipping cost, payment methods, coupon states, address errors, and checkout accessibility. - If field data fails LCP, INP, or CLS at the 75th percentile, treat performance as a conversion risk before adding more scripts or apps.
- If keyboard focus, labels, or form errors fail accessibility checks, treat that as checkout reliability, not a separate compliance task.
- If analytics events are incomplete, repair tracking before ranking design changes by impact.
After you have one written diagnosis, run Deep Digital Ventures WebsiteAdvisor as a second pass by entering the site URL and comparing the audit findings against the shopper path above. The useful output is not a longer to-do list; it is a clearer decision about which page, step, or template should be fixed first.
Tomorrow’s decision rule is simple: pick the highest-value landing page, diagnose the first measurable drop-off, fix the closest source of shopper uncertainty, and retest the same path. Buying more traffic before that work usually multiplies the same abandoned carts.
Common Audit Mistakes
- Starting with a full redesign before proving whether the first break is intent, product clarity, checkout, speed, accessibility, or tracking.
- Using one sitewide conversion rate instead of checking the highest-value landing page, device, source, and product type separately.
- Adding trust badges while leaving price, shipping, returns, fit, availability, or variant behavior unclear near the add-to-cart button.
- Treating technical SEO fields as the fix when the visible product page still fails to answer the shopper’s buying questions.
- Skipping a manual mobile test order because analytics appears clean.
- Increasing ad spend before retesting the same path that already produced abandoned carts.
Sources
- Google people-first content guidance: https://developers.google.com/search/docs/fundamentals/creating-helpful-content
- Google Search spam policies: https://developers.google.com/search/docs/essentials/spam-policies
- Google title-link guidance: https://developers.google.com/search/docs/advanced/appearance/good-titles-snippets
- Google Search Console Performance report help: https://support.google.com/webmasters/answer/7576553
- GA4 recommended ecommerce events: https://support.google.com/analytics/answer/9267735
- PageSpeed Insights documentation: https://developers.google.com/speed/docs/insights/v5/about
- web.dev Web Vitals thresholds: https://web.dev/articles/vitals
- web.dev INP Core Web Vital update: https://web.dev/blog/inp-cwv
- Google product structured-data documentation: https://developers.google.com/search/docs/appearance/structured-data/product
- W3C WCAG 2.2 recommendation: https://www.w3.org/TR/WCAG22/