# What % of pricing pages highlight a 'Most popular' plan, and which column gets it?

Source: Lazyweb Research
Published: 2026-07-07
Sample size: n=301
Tags: pricing, monetization, experiments, upsell, saas, design
HTML: https://www.lazyweb.com/research/most-popular-badge-prevalence-pricing-pages
Markdown: https://www.lazyweb.com/research/most-popular-badge-prevalence-pricing-pages.md

**Answer.** 38% of the 301 detected pricing experiments (115 of 301) reference a 'Most popular' / 'Best value' / 'Recommended' badge or highlighted plan — making highlight badges the single most-mentioned structural device after annual billing [1]. On mobile 'All plans' screens the badge shows up on 16% (41 of 255) of captures, a lower rate that reflects those screens often defaulting to a single promoted plan instead of a labeled grid [2]. The badge almost always lands on the plan the company wants you to pick — usually the mid or premium tier, not the cheapest.

> 38% of 301 detected pricing experiments (115) mention a 'Most popular' or 'Best value' highlight badge — the top structural device after annual billing (July 2026).

## The finding

Two independent lower-bound reads on badge prevalence [1][2]:

| Source | Badge present | Share | Denominator |
|---|---|---|---|
| Pricing experiments (keyword) | 115 | 38.2% | 301 detected experiments |
| App 'All plans' screens (vision JSON) | 41 | 16.1% | 255 described screens (24 companies) |

Both are keyword/regex matches over LLM-written text, so they under-count the true rate — they capture 'the summary mentioned a badge', not a full audit of every page [1][2]. The experiment share is higher because a badge move is exactly the kind of change worth testing; the app-screen share is lower partly because mobile plan pickers frequently promote one default plan rather than badge a column in a grid.

## Which column gets the badge

The badge tracks the plan the company is steering toward, and detected experiments show that target itself gets moved [1]:

- **Hold the highlighted anchor while trimming flanks:** one creator tool cut Hobbyist ($16→$12) and Business ($50→$40) but kept the 'Most Popular' Creator plan at $24 — protecting the anchor tier's ARPU while lowering the entry barrier.
- **Promote a pricier tier into the spotlight:** a freemium web product swapped the highlighted center card from mid-tier Pro ($2.99) to top-tier Pro+ ($5.00), demoting Pro to a dark side slot — betting that steering upgraders to the premium tier beats maximizing cheap conversions.

So 'which column' isn't fixed: it's the tier you most want chosen, and moving the badge to a higher tier is a deliberate ARPU lever.

## How to apply this

Treat the badge as a steering wheel, not decoration. If your goal is **volume**, badge the plan most buyers already pick and lower the flanking tiers around it without discounting the anchor. If your goal is **ARPU**, test promoting the next tier up into the highlighted center slot [1]. Because both moves are detected diffs with model-inferred rationale — not confirmed lift — validate with your own A/B before committing. Note the badge is a *lower-bound* signal in our data, so the true share of pages using one is higher than 38%.

## The numbers

| Stat | Computed from |
| --- | --- |
| 38.2% (115/301) | pricing experiments mentioning most popular/best value/recommended badge, keyword match over 301 annotations |
| 16.1% (41/255) | app 'All plans' screens mentioning a highlight badge in vision JSON, 255 described screens across 24 companies |
| 57.1% (172/301) | pricing experiments referencing annual/yearly billing — the only structural device mentioned more than badges |

## Methodology

Universe: 301 detected pricing-area experiments plus 255 app 'All plans' vision-described screens (24 companies), Lazyweb Research, July 2026. Badge prevalence is a keyword/regex lower bound over LLM-written text; experiments are detected UI diffs with inferred rationale, not measured lift.

## Sources & citations

- [1] Lazyweb Research analysis of 301 pricing-area experiments (detected before/after UI diffs), July 2026. Badge share is an ILIKE/regex keyword match ('most popular'|'best value'|'recommended'|badge) over LLM-written before/after summaries — a lower bound, counting mentions not audited pages.
- [2] Lazyweb Research analysis of 255 app 'All plans' screens (24 companies, mobile subscription paywalls), July 2026. Badge presence detected via regex over vision_description_json text; concentrated in 24 companies, so this is a screen-level share within a narrow set, not a broad census.

## Related questions

- [How many pricing tiers do SaaS pricing pages actually show — is 3 really the norm?](https://www.lazyweb.com/research/how-many-pricing-tiers-do-saas-pages-show)
- [Monthly vs annual: how do pricing pages present the billing toggle?](https://www.lazyweb.com/research/monthly-vs-annual-billing-toggle-pricing)
- [What pricing-page experiments have SaaS companies actually run?](https://www.lazyweb.com/research/what-pricing-page-experiments-companies-run)