# Product Description: Expanded or Collapsed A/B Test

Page: https://alidemirbas.com.tr/en/lab/ab-test-library/tests/product-description-expanded-or-collapsed-ab-test

## Hypothesis

If the description starts expanded, shoppers can read the details without an extra tap; if it starts collapsed, the page stays shorter and they may reach the add-to-cart area sooner. With decision-critical information visible in both arms, which default state could raise the add-to-cart rate may depend on how much information the category needs.

## When to run this test

When scroll maps show the long description passed over, shoppers ask about topics it already covers, or returns point to mismatched expectations, the description may be slowing decisions or getting skipped. If one of the layouts works, shoppers find what they need sooner and add to cart. If the questions concern details the description never mentions, fill that gap first. Ahead of launch, verify that material, compatibility and warranty details are visible in both arms, that collapsed content opens for shoppers, and that search engines are not served a different version.

## Primary metric

**Add-to-cart rate**: Compare successful add-to-cart actions per assigned visitor when the same description starts expanded or collapsed.

## Other metrics

- **Purchase conversion rate (CR)**: Compare the effect of the default description state on completed purchases.
- **Return rate**: Compare returns for orders with the same completed follow-up window; review reasons separately when available.
- **Product-related support questions**: Compare questions about topics covered in the description across both arms.

## What to check before and during the test

- **Default state**: Start the same description expanded in one arm and collapsed in the other.
- **Expansion**: Report opens in the collapsed arm as a diagnostic measure, not as a shared success metric.
- **Section scope**: Keep included sections fixed and leave information essential to a purchase decision visible.
- **Layout effect**: Record how content and CTA visibility change without separately moving the CTA.
- **Category**: Review categories with different information needs.

## What to watch when reading the result

- Make the call on the add-to-cart rate. Section opens exist only in the collapsed arm, so do not use them to compare the two. If the leading arm adds more to cart but shows lower purchase conversion, more returns or more product-related support questions, shoppers may be missing information, so do not ship it on that basis.
- When the description text and included sections stay the same in both arms, the result reflects the default state alone; rewriting the copy in the same test would leave you unable to separate the two. Read categories with different information needs on their own, and compare returns only on orders whose return window has fully elapsed in both arms.
- Write section headings that describe what is inside, because a generic label keeps people from opening it. So before removing a rarely opened section, review its heading. If the add-to-cart gap is small, enter each arm's visitors and add-to-cart counts into the [A/B test significance calculator](https://alidemirbas.com.tr/en/calculators/ab-test), and if the result is not significant, do not call either layout a winner.

## Frequently Asked Questions

### What must remain visible in the collapsed version?

Keep essential material, compatibility and warranty information visible in both groups. Fix the sections included in the accordion and preserve the description copy.

### Can accordion expansion be the success metric?

No. Expansion exists only in the collapsed version. Report it as diagnostic information and use successful add-to-cart rate as the primary outcome.

### Should I remove a section with a low expansion rate?

Not automatically. Its heading may fail to explain the content. Use descriptive headings and compare support questions about the topics covered.

### Can collapsing content change CTA visibility?

Yes. Assess that layout effect without separately moving the CTA. Keep the same content accessible in HTML and user-expandable. Do not rely on important text loading from the server only after a click.