E-commerce, SXO and UX

Improve e-commerce journeys from discovery to conversion, with close attention to search, usability and trust.

55 articles · Latest article updated

Search covers every article in this topic, including the archive and article text.

Understand the topic

A practical guide to this topic

A commerce journey should make the offer, conditions, choices and next steps clear. This category connects discovery, comprehension, trust and conversion across mobile and desktop. Cart abandonment alone does not demonstrate an interface problem. Check the observed step, product availability, final cost and measurement events. Connect traces to a reproducible task rather than assigning intent to every missing conversion.

What to examine
  • Study search, comparison, basket, checkout and support as one journey.
  • Show price, availability, delivery and conditions before commitment.
  • Test errors, backtracking and accessibility needs at decisive steps.
  • Check that a variant URL actually selects the image, price, stock and offer added to cart.
  • Connect customer language, reliable attributes and filter states to clear results and controlled URLs.
  • Distinguish physical, sellable, reserved and incoming stock, then test concurrent purchases, cancellations and channel synchronisation.
  • Separate return approval, receipt, requested refunds and confirmed outcomes.
  • Explain verified-review labels and keep moderation fair from submission to structured data.
  • Reconcile displayed prices, orders, payments and refunds without mixing units.
  • Verify what changes after a stop request, immediately or at a planned period boundary.
Useful questions
  • Where does a customer lose context or trust?
  • Which information arrives too late?
  • Can someone complete the task with keyboard or zoom?
  • Does the email confirmation reflect an order actually accepted?
  • Does an unavailable variant still appear purchasable on another channel?
  • Are units and values coherent?
  • Is an on-hand unit always sellable?
  • Can a refund be announced when a return is approved?
  • Should a negative review be removed?
  • Do all currencies use two decimals?
  • Does cancellation mean a refund?

Illustrative decision example

Situation
Fictional example: these inputs describe no customer or observed result. Someone filters a list, opens a product page and returns to find the selection and position lost.
Check
Replay with multiple filters on mobile and keyboard. Check URL, visible state, result count and empty-list communication.
Act
Preserve useful context and provide an understandable route out of no-match results. The presence of a filter does not establish usability.

Optimizing User Experience in E-Commerce: Enhancing Navigation and Building Customer Trust

Search and facets: make a catalog usable

Google — Managing crawling of faceted navigation URLs

Cover the apparently lost order

Missing confirmation can conceal a successful payment. Reconcile provider state, order and fulfilment before asking users to retry; test repeated notifications and interrupted returns.

Does disconnection after payment result in one order and a retrievable state?

Explore the methods

Read data · verify · decide

Cart and refund: reconcile exact amounts

Page, order and payment need matching currency, discounts and states. Receiving a notification twice must not produce two effects.

Paid amount
€58.8759.97 − 6.00 + 4.90
Example refund
€17.9919.99 − 2.00
Balance after refund
€40.8858.87 − 17.99

Fictional teaching case — figures describe neither CIE nor a client.

Questions to support your decisions

Find answers and practical checks in the analyses in this category.

Explore the archive

Further analysis in this topic beyond the recent articles listed below.

References: data, uses and limitations

Documentation reviewed on .

References: data, uses and limitations
Source and purposeVerified data or benchmarkHow to use itLimitation to retain
W3C · WCAG 2.2

Evaluate accessibility criteria for web content.

WCAG 2.2 is a W3C Recommendation. Success criteria have A, AA and AAA levels. Define tasks, pages and states, then combine inspection, keyboard, zoom and relevant assistive technology. Keep reproduction steps for barriers.

Explore the method →

An automated scanner does not establish conformity of a complete journey. Evaluation must cover interactive states and actual content.
Google · Core Web Vitals

Distinguish loading, responsiveness and visual stability.

Good thresholds are LCP ≤ 2.5 s, INP ≤ 200 ms and CLS ≤ 0.1 at the 75th percentile, segmented by mobile and desktop. Separate field measurement from laboratory tests. Record period, URL, device, population and sample size before comparing changes.

Explore the method →

These thresholds are not measured results for this site. A good lab score alone does not establish visitor experience.
MDN · Cookie boundaries

Understand session-cookie scope and SameSite boundaries.

Secure, HttpOnly, SameSite and the __Host- prefix address different risks. A site can include multiple origins. Test external navigation, subdomains, provider returns and authenticated operations separately.

Explore the method →

Cookie configuration does not replace CSRF checks or server-side authorisation.

Email security: identity, alignment and transport

E-commerce: distinguish authenticated and expected mail

Orders, receipts and promotions have different purposes. Validated domain identity establishes neither commercial relevance nor the recipient’s expectations.

  • Map transactional and promotional platforms separately.
  • Test alignment on each stream, including authorised payment or delivery providers.
  • Analyse technical refusals separately from unsubscribe and open metrics.

Open the comparison and DMARC simulator →

References and status checked on · SPF · RFC 7208 DKIM · RFC 6376 DMARC · RFC 9989

Product identity: GTIN and variants

Ecommerce: enrich the page without blurring the entity

Connect structured data and the purchase journey to a documented identity model.

  • Preserve zeros and raw values useful for acceptance checks.
  • Test the URL preselecting each variant.
  • Compare identity, price and availability on the page and in the cart.

Explore identifiers and check a GTIN digit →

GS1 · 2D Barcodes at Retail POS Implementation Guideline · Release 1.1.0 · ratified December 2025 · §4.3 / Table 4-2

Google Search Central · Product variant structured data · Updated 2026-09-08 · consulted 2026-10-23

API amount precision and exact units

Separate exact conversion from payment confirmation

An interface can display the correct price while preparing an incorrect provider integer. Acceptance must reconcile the server amount with the operation contract, then check confirmed state without mistaking arithmetic for completed payment.

  • Test zero-, two- and three-decimal currencies.
  • Include a case where step cannot be inferred from decimals.
  • Retain an exact reference before localised formatting.

Check a unit in the workshop →

Adyen · Currency codes and minor units · Provider documentation · reviewed 2026-10-23

Stripe · Supported currencies and special cases · Provider documentation · reviewed 2026-10-23

Reference material

Primary guidance published by the organizations responsible for these methods and standards.