>_ Product Page Testing Checklist

Short answer

A Product Page Testing Checklist is a list of checks for a product detail page in an e-commerce store, marketplace, SaaS pricing flow, booking product, digital product store, or any product where the user makes a purchase decision on a dedicated product, plan, or service page.

Product page testing helps make sure that the user sees the correct product title, images, price, discount, variants, availability, description, specifications, delivery and return information, reviews, CTA buttons, and can add the product to cart or continue to purchase without errors.

The product page is one of the most important pages in the e-commerce flow. This is where the user decides whether the product fits their needs, whether they trust the page, whether they understand the price, and whether they can continue to purchase.

The main idea is: product page testing checks whether the user can understand the product, choose the correct variant, and start the purchase from this page.

This guide can also be used as a product detail page testing checklist, PDP testing checklist, e-commerce product page QA checklist, product page smoke checklist, or product page release checklist.

Product Page Testing vs Shopping Cart Testing

Product page testing and shopping cart testing are connected, but they check different stages of the purchase journey.

Product page testing checks the page before the product is added to cart:

• product title;
• product images;
• price;
• sale price;
• variants;
• stock status;
• product description;
• specifications;
• quantity selector;
• add to cart button;
• buy now button;
• delivery information;
• return policy;
• reviews;
• related products;
• product SEO;
• product analytics.

Shopping cart testing checks what happens after the product is added:

• cart item;
• selected variant;
• quantity;
• subtotal;
• remove item;
• cart persistence;
• guest cart;
• logged-in cart;
• cart merge;
• cart-to-checkout transition.

In simple terms: product page testing answers “can the user choose a product and start the purchase?”, while shopping cart testing answers “did the cart correctly save the selected product?”

Product Page Testing vs E-commerce QA

Product page testing is part of e-commerce QA, but it is not the entire e-commerce QA process.

[E-commerce QA](/qa-guides/ecommerce-qa-checklist) is broader. It includes:

• catalog;
• category pages;
• product listing;
• product detail pages;
• search;
• filters;
• cart;
• checkout;
• payment;
• shipping;
• inventory;
• order confirmation;
• emails;
• admin panel;
• analytics.

Product page QA focuses on one page: how correctly, clearly, and reliably the user can review the product and move to the next purchase step.

For example, if the user selects size M and color Black, product page testing checks that these options are available, the selected values are shown correctly, price and stock update correctly, and add to cart sends this exact variant.

When to use a Product Page Testing Checklist

Use this checklist whenever a product detail page is created or changed.

For example:

• a new e-commerce site is launching;
• a marketplace is launching;
• a new product page template is added;
• product image gallery changes;
• price display changes;
• sale prices are added;
• variant selector is added;
• stock status changes;
• add to cart button changes;
• buy now button is added;
• quantity selector changes;
• product description changes;
• specifications change;
• reviews are added;
• delivery or return information is added;
• related products block is added;
• product SEO changes;
• product structured data changes;
• mobile product page changes;
• there was a production bug: wrong price, broken image, wrong variant, unavailable product can be purchased, or add to cart does not work.

For a small change, a short product page smoke test may be enough. For an e-commerce launch, product page redesign, pricing changes, variant logic, or stock changes, it is better to go through the full product page testing checklist.

Short Product Page Testing Checklist

If you need a minimal product page smoke test, check that:

• product page opens;
• product title is correct;
• product images are displayed;
• image gallery works;
• price is correct;
• sale price is displayed correctly, if available;
• stock status is correct;
• product description is displayed;
• variants can be selected;
• unavailable variants cannot be purchased;
• quantity selector works, if available;
• add to cart button works;
• buy now button works, if available;
• selected variant is passed to cart;
• delivery and return information is available, if needed;
• reviews are displayed, if available;
• related products are displayed, if available;
• product page works on mobile;
• product page does not contain test content;
• product SEO basics are configured;
• product analytics events are sent, if important;
• there are no critical console errors or failed API requests.

This is not full e-commerce QA. It is a minimal check that helps quickly confirm whether the product page works at a basic level.

Product Page Testing Checklist

1. Define the product page testing scope

Before testing starts, define which type of product page is being checked and which elements are in scope.

Check that:

• product page template being tested is clear;
• supported product types are known;
• physical products are supported, if relevant;
• digital products are supported, if relevant;
• subscription plans are supported, if relevant;
• product variants exist, if relevant;
• bundles exist, if relevant;
• sale prices exist, if relevant;
• stock status exists, if relevant;
• reviews exist, if relevant;
• related products exist, if relevant;
• delivery information exists, if relevant;
• return policy exists, if relevant;
• add to cart exists;
• buy now exists, if supported;
• wishlist exists, if supported;
• product SEO requirements are known;
• important devices and browsers are known;
• the person responsible for pass / fail decision is known.

The main question is: which product page elements should help the user make a decision and start the purchase?

2. Prepare test products and product data

One regular product will not show all possible product page issues. You need different types of test products.

Check that you have:

• regular product;
• product with variants;
• product with sale price;
• out-of-stock product;
• low-stock product;
• hidden product;
• product with long title;
• product with short title;
• product with long description;
• product with multiple images;
• product with missing image, if possible;
• product with video, if supported;
• product with reviews;
• product without reviews;
• digital product, if supported;
• physical product, if supported;
• bundle, if supported;
• subscription product or plan, if supported.

Product page testing is better with realistic product data, not only ideal short test products.

3. Check product page availability

First, make sure the product page opens and is available to the user.

Check that:

• product page opens at the correct URL;
• page does not return 404 for an active product;
• unavailable product is handled according to product rules;
• hidden product is not publicly available if it should be hidden;
• deleted product shows the correct state;
• out-of-stock product page opens if the product should remain visible;
• URL does not point to staging or an old domain;
• page is available without login if it should be public;
• page requires login if the product is private;
• direct URL works correctly;
• page does not show a broken or empty state without explanation.

If the product page does not open or points to the wrong URL, all deeper checks lose value.

4. Check product title and basic information

Product title and basic information should help the user understand what they are viewing.

Check that:

• product title is displayed;
• product title is correct;
• title is not critically cut off;
• long title does not break layout;
• brand is displayed, if needed;
• category is displayed, if needed;
• SKU is displayed, if needed;
• product ID is not shown to the user unnecessarily;
• short description is displayed;
• key selling points are displayed, if available;
• product status is clear;
• there is no placeholder text;
• there are no internal comments;
• there is no test content.

The product page should immediately answer: what is this product, what is its status, and why should the user continue reviewing it?

5. Check product images

Images are one of the main elements of a product page. Users often make purchase decisions visually.

Check that:

• main image is displayed;
• image loads without error;
• image is not stretched;
• image is not unexpectedly cropped;
• image quality is acceptable;
• thumbnails are displayed;
• user can switch between images;
• selected image updates;
• missing image is handled clearly;
• images match the product;
• images do not show the wrong variant;
• image alt text exists where important;
• images do not contain test or placeholder content.

If the product image is wrong or broken, trust in the product page drops quickly.

6. Check image gallery, zoom, and video

If the product page has gallery, zoom, or video, these elements should be checked separately.

Check that:

• gallery opens;
• gallery navigation works;
• user can move to the next image;
• user can move to the previous image;
• thumbnails work;
• zoom works, if supported;
• zoom does not break layout;
• full-screen image view works, if available;
• video plays;
• video controls are available;
• video does not autoplay unnecessarily;
• video does not break mobile layout;
• gallery works on mobile;
• gallery does not block add to cart.

Media interaction should help the user understand the product, not interfere with purchase.

7. Check price display

Price is one of the most critical elements of the product page.

Check that:

• base price is displayed;
• price is correct;
• currency is correct;
• price format is correct;
• sale price is displayed, if available;
• original price is displayed, if needed;
• discount percentage is correct, if shown;
• price updates after variant selection if variants affect price;
• price does not disappear during loading;
• price on product page matches cart;
• price does not contain test values;
• price is visible on desktop and mobile;
• rounding works correctly;
• tax included/excluded message is displayed, if needed.

Incorrect price on a product page is a critical bug because it directly affects purchase and user trust.

8. Check sale price, discounts, and promotions

Sale labels and promotions should be accurate and not misleading.

Check that:

• sale badge is displayed if product is on sale;
• sale badge is not displayed if sale is not active;
• original price is correct;
• discounted price is correct;
• discount amount is correct;
• discount percentage is correct;
• promotion text is up to date;
• promotion expiration date is correct, if shown;
• expired promotion is not displayed;
• promotion applies only to eligible product;
• variant-specific discounts work;
• promo message does not contradict cart or checkout;
• sale price is passed to cart.

If the user sees a discount on the product page, cart and checkout should confirm the same logic.

9. Check stock status and availability

Availability should be clear before add to cart.

Check that:

• in-stock product can be purchased;
• out-of-stock product cannot be purchased, if expected;
• out-of-stock status is displayed clearly;
• low-stock message is displayed, if available;
• preorder status is displayed, if supported;
• backorder status is displayed, if supported;
• stock status updates after variant selection;
• unavailable product has disabled add to cart;
• user cannot bypass stock restriction through UI;
• stock message does not contradict cart;
• stock status updates after refresh;
• user sees a clear message if the product becomes unavailable.

Stock bugs are especially dangerous: the store may sell a product that is not available or block a product that is available.

10. Check product variants

Variants are one of the riskiest parts of a product page.

Check that:

• user can select size;
• user can select color;
• user can select material;
• user can select style;
• user can select plan, if this is SaaS;
• user can select subscription interval, if available;
• selected variant is visually clear;
• unavailable variant is disabled;
• unavailable variant cannot be added to cart;
• variant selection updates price, if needed;
• variant selection updates image, if needed;
• variant selection updates stock status, if needed;
• selected SKU is correct;
• selected variant is passed to cart;
• user cannot add to cart without required variant.

If a product has variants, the product page should clearly show which exact variant is selected.

11. Check default variant behavior

Default variant can strongly affect purchase behavior.

Check that:

• default variant is selected if this is the product rule;
• no variant is selected if user must choose manually;
• default variant is available;
• default variant price is correct;
• default variant image is correct;
• default variant stock status is correct;
• unavailable default variant is not selected accidentally;
• user understands that they need to select a variant;
• error appears if user clicks add to cart without required variant;
• selected variant remains after navigation or refresh if expected.

Default selection should not cause the user to accidentally buy the wrong size, color, or plan.

12. Check quantity selector

Quantity selector on the product page should work before the product is added to cart.

Check that:

• quantity selector is displayed, if needed;
• default quantity is correct;
• user can increase quantity;
• user can decrease quantity;
• quantity cannot be lower than minimum;
• quantity cannot be higher than maximum;
• quantity cannot exceed stock;
• manual quantity input works, if allowed;
• invalid quantity shows an error;
• quantity affects add to cart result;
• selected quantity is passed to cart;
• quantity selector works on mobile.

If quantity is selected on the product page, cart should receive this exact quantity.

13. Check Add to Cart button

Add to Cart is the main action on many product pages.

Check that:

• add to cart button is visible;
• button text is clear;
• button is enabled for available product;
• button is disabled for unavailable product;
• button is disabled until required variant is selected, if needed;
• click adds product to cart;
• selected variant is passed to cart;
• selected quantity is passed to cart;
• user receives feedback after click;
• cart icon updates;
• cart drawer opens, if expected;
• double click does not create unexpected duplicate;
• loading state is displayed;
• error state is displayed if add to cart fails.

Add to cart should be fast, clear, and reliable. The user should immediately understand that the product was added.

14. Check Buy Now button

Buy Now sends the user directly to checkout or purchase flow, so it should be tested separately.

Check that:

• buy now button is displayed, if supported;
• button leads to the correct flow;
• selected product is passed to checkout;
• selected variant is passed;
• selected quantity is passed;
• buy now does not add the wrong item;
• buy now does not unexpectedly lose existing cart, if cart already has items;
• unavailable product cannot be bought;
• required variant selection is enforced;
• checkout receives correct price and product data;
• buy now works on mobile;
• user understands the difference between Add to Cart and Buy Now.

Buy Now is a faster path to purchase, but it should not bypass critical validation.

15. Check wishlist, save, and compare actions

If the product page supports wishlist, save for later, or compare, these actions should be tested.

Check that:

• wishlist button is displayed;
• user can add product to wishlist;
• user can remove product from wishlist;
• wishlist state remains;
• login required message is displayed if login is needed;
• saved product appears in account;
• selected variant is saved if supported;
• compare button works, if available;
• compare state is displayed;
• actions do not interfere with add to cart;
• actions work on mobile;
• no duplicate saved items are created without reason.

Wishlist and compare should not interfere with the main purchase flow.

16. Check product description

Product description should be accurate, up to date, and readable.

Check that:

• description is displayed;
• description matches the product;
• formatting is correct;
• bullets are displayed;
• long description does not break layout;
• expandable content works, if available;
• hidden/collapsed content can be opened;
• HTML formatting does not break the page;
• description does not contain outdated information;
• description does not contain placeholder text;
• description is readable on mobile;
• important information is not hidden too deeply.

Description should help the user make a decision, not create doubts.

17. Check specifications and product details

Specifications are often important for technical products, apparel, electronics, furniture, SaaS plans, and B2B products.

Check that:

• specifications section is displayed;
• key attributes are correct;
• size or dimensions are correct;
• weight is correct, if needed;
• material is correct;
• compatibility information is correct;
• included items are listed;
• plan limits are listed, if this is SaaS;
• technical details are not cut off;
• table is readable on mobile;
• empty specifications are not shown as a broken section;
• details match catalog/admin data.

Incorrect specifications can lead to returns, support tickets, and loss of trust.

18. Check size guide or product guide, if available

For apparel, shoes, furniture, hardware, and other products, a guide may be critical.

Check that:

• size guide link is displayed;
• guide opens;
• guide matches product category;
• units are correct;
• table is readable;
• modal or page works on mobile;
• guide does not contain outdated data;
• guide can be closed;
• selected size is not reset after opening guide;
• guide does not block add to cart.

Size guide should help the user choose the correct variant, not interfere with purchase.

19. Check delivery and shipping information

Users often make purchase decisions based on delivery information.

Check that:

• delivery information is displayed;
• shipping cost or estimate is clear;
• delivery date estimate is displayed, if available;
• free shipping message is correct;
• region-specific delivery info works, if available;
• pickup information is displayed, if supported;
• digital product does not show irrelevant shipping info;
• restricted region message is clear;
• delivery info does not contradict checkout;
• delivery info is readable on mobile.

If delivery information differs between product page and checkout, user trust can drop.

20. Check return, refund, and warranty information

Return policy, refund policy, and warranty often affect trust.

Check that:

• return information is available;
• refund information is available, if needed;
• warranty information is displayed, if available;
• policy link works;
• modal or accordion opens;
• policy matches product type;
• final sale or non-returnable status is displayed, if applicable;
• policy does not contain outdated text;
• policy is readable on mobile;
• policy does not contradict checkout or FAQ.

For e-commerce product pages, trust information can be as important as the product description.

21. Check reviews and ratings

Reviews help users make decisions, but they can also break layout or show incorrect data.

Check that:

• rating is displayed;
• average rating is correct;
• review count is correct;
• reviews are displayed;
• reviews match the product;
• empty reviews state is clear;
• user can open reviews;
• review sorting works, if available;
• review filtering works, if available;
• write review button works, if supported;
• review images are displayed, if available;
• reviews do not contain test content;
• reviews are readable on mobile.

If reviews belong to the wrong product, that is a serious trust issue.

22. Check Q&A or product questions, if available

Product Q&A helps answer user doubts before purchase.

Check that:

• Q&A section is displayed;
• questions match the product;
• answers are displayed;
• user can ask a question, if supported;
• form validation works;
• submitted question is saved;
• moderation works, if expected;
• empty state is clear;
• internal-only answers are not visible to users;
• Q&A does not break mobile layout.

Q&A can be especially important for complex products, electronics, furniture, marketplaces, and B2B products.

23. Check related products, recommendations, and upsell

Product page often contains related products, recommended products, bundles, or upsell.

Check that:

• related products are displayed;
• recommendations are relevant;
• recommended product opens the correct page;
• recommended product price is correct;
• unavailable products are not suggested or are marked correctly;
• bundle offer is displayed, if available;
• upsell does not interfere with main CTA;
• carousel works;
• user can add recommended product, if supported;
• recommendations work on mobile;
• analytics tracking works, if important.

Recommendations should support purchase, not distract from the main product.

24. Check breadcrumbs and navigation

Users should understand where they are and how to return to category or search results.

Check that:

• breadcrumbs are displayed;
• breadcrumbs lead to correct category pages;
• back to results works, if available;
• category link is correct;
• brand link is correct, if available;
• navigation preserves filters if returning to listing should keep them;
• user can continue shopping;
• header navigation works;
• cart icon is available;
• search is available;
• mobile navigation works.

Product page should not be a dead end. User should be able to continue browsing easily.

25. Check product page mobile experience

Mobile product page is critical for e-commerce conversion.

Check that:

• page opens on mobile;
• title is readable;
• images are usable;
• gallery works;
• price is visible;
• variants are easy to select;
• add to cart is visible;
• sticky CTA does not cover content;
• quantity selector is usable;
• description is readable;
• reviews are readable;
• delivery/returns information is available;
• there is no unexpected horizontal scroll;
• page is not too heavy;
• checkout/cart transition works on mobile.

Mobile product page should let the user not only view the product, but also start the purchase.

26. Check browser compatibility

Product page can break in different browsers because of gallery, scripts, variants, sticky CTA, media, or layout.

Check that:

• product page works in Chrome;
• product page works in Safari;
• product page works in Firefox, if supported;
• product page works in Edge, if supported;
• mobile Safari works;
• mobile Chrome works;
• image gallery works;
• variant selector works;
• add to cart works;
• sticky CTA works;
• media works;
• there is no browser-specific layout issue;
• there are no critical console errors.

Safari and mobile Safari should be checked especially carefully for image gallery, sticky CTA, media, and add to cart behavior.

27. Check product page performance

Product pages often contain images, videos, recommendations, and third-party scripts. Performance directly affects conversion.

Check that:

• page loads fast enough;
• main product content appears quickly;
• images are optimized;
• image gallery does not block the page;
• video does not slow down first load;
• recommendations do not block main content;
• add to cart responds quickly;
• variant change responds quickly;
• page remains usable on mobile;
• there is no heavy layout shift;
• third-party scripts do not block key actions;
• loading states are clear.

If the product page opens slowly or jumps during loading, the user may leave before adding to cart.

28. Check product page SEO basics

Product pages are often important for organic traffic, so basic SEO checks are needed.

Check that:

• product page has a unique title tag;
• meta description is filled;
• H1 matches product title;
• canonical URL is correct;
• product URL is readable;
• page is not noindexed if it should be indexed;
• out-of-stock SEO behavior matches product rules;
• structured data is added, if used;
• product name in structured data is correct;
• price in structured data is correct;
• availability in structured data is correct;
• product images are accessible;
• internal links work;
• Open Graph / social preview is configured, if important.

This SEO section does not replace an SEO audit, but it helps avoid breaking important product pages before release.

29. Check product structured data, if used

Product structured data may help search engines understand the product page, but it should match visible content.

Check that:

• product structured data is present, if used;
• product name matches the page;
• image URLs are correct;
• price matches visible price;
• currency is correct;
• availability matches stock status;
• rating matches visible rating, if included;
• review data is correct, if used;
• SKU or GTIN is correct, if available;
• structured data does not contain test values;
• structured data does not contradict page content.

If structured data shows price or availability that does not match the product page, this can create SEO and trust problems.

30. Check product analytics

Product analytics helps understand views, engagement, and conversion.

Check that:

• product view event is sent;
• product ID is correct;
• product name is correct;
• variant ID is passed if selected;
• price is correct;
• currency is correct;
• category is correct;
• add to cart event is sent;
• wishlist event is sent, if available;
• gallery interaction is tracked, if important;
• recommendation click is tracked, if needed;
• events are not duplicated;
• UTM/source is preserved;
• analytics does not hurt performance.

Product analytics is especially important for funnel analysis, merchandising, paid traffic, recommendations, and conversion optimization.

31. Check accessibility basics

Product page should be usable for different users.

Check that:

• page can be used keyboard-only;
• focus state is visible;
• product images have alt text if important;
• buttons have clear names;
• variants are keyboard-accessible;
• dropdowns are accessible;
• price is readable;
• contrast is acceptable;
• form fields or selectors have labels;
• reviews are readable;
• modals or size guide are accessible;
• error messages are clear;
• add to cart is keyboard-accessible.

A full accessibility audit is separate work, but product page should not have obvious accessibility blockers.

32. Check security and privacy basics

Product page is usually public, but it can still have security risks: hidden products, private prices, restricted offers, admin fields.

Check that:

• hidden product is not publicly available;
• private product requires access if needed;
• user does not see admin-only fields;
• user does not see private supplier/internal data;
• restricted price is not visible to the wrong user;
• direct request does not allow purchase of unavailable product;
• price cannot be changed from frontend;
• variant restrictions are enforced on backend;
• product page does not expose sensitive data;
• API response does not contain unnecessary internal fields.

Security on product page is often related to price manipulation, hidden catalog items, and private offers.

33. Check CMS/admin data consistency

If product page is managed through CMS or admin panel, compare the data.

Check that:

• product title matches admin data;
• price matches;
• sale price matches;
• stock status matches;
• variants match;
• images match;
• description matches;
• specifications match;
• SEO fields match;
• publish/unpublish status works;
• admin changes appear on product page;
• cache does not show old data for too long;
• preview mode works, if available.

Product page bugs often come not from frontend but from incorrect CMS/admin data sync.

34. Check error states and fallback behavior

Product page should handle data, API, and media errors correctly.

Check that:

• missing image shows fallback;
• missing description does not break page;
• missing price is handled;
• unavailable product state is clear;
• product API error shows a clear message;
• add to cart error is displayed;
• variant loading error is displayed;
• recommendations error does not break main product page;
• review loading error does not break the page;
• there is no endless loader;
• user can retry if needed.

Product page should not look broken if one secondary block fails to load.

35. Run production product page smoke after release

After product page changes, run a short production check.

Check that:

• production product page opens;
• title is correct;
• images are displayed;
• price is correct;
• variant selection works;
• stock status is correct;
• add to cart works;
• cart receives correct product;
• buy now works, if available;
• mobile page works;
• product structured data does not contain obvious errors, if used;
• analytics receives product view and add to cart events, if important;
• there are no staging links;
• there is no test content;
• logs and monitoring do not show increased errors.

Production product page smoke should be short and safe. Its goal is to make sure real users can open the product page and start purchase after release.

Common mistakes

1. Testing only Add to Cart

Product page testing is not only add to cart. Title, images, price, variants, stock, description, delivery info, reviews, mobile, and analytics should also be checked.

2. Not testing variants

Variants are a frequent source of critical bugs. User selects one size or color, but a different variant goes to cart.

3. Not comparing price between product page and cart

If product page shows one price and cart shows another, user trust drops. Price should be consistent or the change should be clearly explained.

4. Ignoring out-of-stock products

Out-of-stock state should be clear. User should not be able to purchase a product that cannot be bought.

5. Not testing mobile product page

On mobile, gallery, sticky CTA, variant selector, reviews, delivery info, or add to cart can easily break.

6. Not testing media

Broken images, wrong variant images, or heavy videos can strongly affect conversion.

7. Not checking delivery and return information

Users often make decisions based on shipping, returns, and warranty. If this information is missing or contradicts checkout, it is a problem.

8. Not checking SEO basics

Product pages are often important for organic traffic. Title, canonical, indexability, structured data, and Open Graph should not be ignored.

9. Not testing analytics

If product view or add to cart events do not work, the team loses funnel and product performance data.

10. Not running production product page smoke

Staging may work, while production product page fails because of cache, CMS sync, CDN, image URLs, pricing config, inventory sync, or analytics.

FAQ

What is a Product Page Testing Checklist?

A Product Page Testing Checklist is a list of checks for a product detail page. It helps test title, images, gallery, price, sale price, variants, stock status, description, specifications, add to cart, buy now, delivery/returns info, reviews, related products, mobile behavior, SEO, and analytics.

What should be checked on a product page?

At minimum, check:

• product page opens;
• product title;
• product images;
• image gallery;
• price;
• sale price;
• stock status;
• variants;
• quantity selector;
• add to cart;
• buy now, if available;
• product description;
• specifications;
• delivery and returns information;
• reviews;
• related products;
• mobile experience;
• SEO basics;
• analytics;
• production smoke.

How is product page testing different from shopping cart testing?

Product page testing checks the product page before the item is added to cart: product data, images, price, variants, stock, CTA, and add to cart behavior.

Shopping cart testing checks the cart after the item is added: cart item, selected variant, quantity, subtotal, remove, cart persistence, and transition to checkout.

How do you test product variants?

Check that user can select size, color, material, plan, or subscription interval, unavailable variants cannot be purchased, price/image/stock update after selection, and selected variant is passed to cart and checkout.

How do you test product images?

Check main image, thumbnails, gallery navigation, zoom, variant-specific images, mobile behavior, fallback for missing image, and absence of placeholder/test images.

How do you test product price?

Check base price, sale price, original price, discount, currency, rounding, variant-specific price, tax included/excluded message, and consistency between product page, cart, and checkout.

How do you test Add to Cart on a product page?

Check that add to cart button is available for available product, disabled for unavailable product, requires variant selection, passes correct product/variant/quantity to cart, updates cart count, and shows clear feedback.

Should SEO be checked on product pages?

Yes, if product pages are important for organic traffic.

Check title, meta description, H1, canonical, indexability, product URL, structured data, images, internal links, and Open Graph / social preview.

Should product page be tested on mobile?

Yes. Mobile product page often affects conversion. Check images, gallery, price, variants, add to cart, sticky CTA, description, reviews, delivery info, and cart transition on mobile.

How do you know a product page is ready for release?

A product page can be considered ready for release when:

• page opens correctly;
• product data is accurate;
• images and gallery work;
• price and stock are correct;
• variants work;
• unavailable products cannot be purchased;
• add to cart works;
• selected product/variant/quantity is passed to cart;
• mobile page works;
• SEO basics are correct;
• analytics events are sent;
• no blocker or critical bugs remain;
• production product page smoke check has passed.