How do I test my pricing page?

A pricing-page check you can run today

1. Start signed out: open the homepage in a private window.
2. Find the page: is there a link called Pricing in the header, visible without opening a menu?
3. Type the usual address: does yoursite.com/pricing open the pricing page, or redirect to it?
4. The price: does each plan show its price as a number, with the currency? Does it state the billing period and whether it is per seat?
5. Monthly and yearly: if there is a toggle, can you tell which price is showing? Is the total yearly cost clear?
6. Limits: does each plan state its limits in numbers on this page? A free tier feels like a catch when its real limits only appear in the FAQ.
7. The same promise: does the pricing page match what the homepage says? Changing “free” on the homepage to “free trial” here walks back that claim.
8. Which plan is mine: can a visitor pick a plan without doing the maths?
9. The button: does each plan's button say what comes next: a signup form, a checkout or a sales call? Can you tell whether a card is needed?
10. On a phone: can you still compare the plans at phone width?

Several of these come from the persona in Menso's Purchase intent template, a freelance UX consultant. She pays for her own tools and reads a pricing page the way she reads a contract. Free tiers whose real limits only show up in the FAQ make her suspicious. So do pricing pages that make her do the maths herself.

Check that the page works

Follow each plan's button to the end. If you take payments with Stripe, its testing guide describes a sandbox where no money moves. Use a test card such as 4242 4242 4242 4242. Enter any valid future expiry date and any three-digit CVC. Stripe's guide says not to use real card details for testing.

Then check where the price appears. Open the page source and search for the number. If it appears only inside a script, a browser shows the price and a reader that runs no scripts does not see it. The free site check requests your usual pricing address and reports whether a price is in the HTML text.

On November 11, 2026, we ran that check once on 516 sites posted to Show HN. It could read 73 pricing pages. Of those, 65 had a price in the HTML text. Another 6 had one only inside the page's scripts. On 2 it found none. These counts cover one sample of new projects on one day. They are not rates for the web. See every count and the method.

The price needs a different test

The page checks above cannot tell you whether the price is right. That takes people who could buy:

• Interviews. Ask recent buyers, and people who looked and did not buy, what they compared you with and what they expected to pay.
• A price-sensitivity survey. Van Westendorp's Price Sensitivity Meter was introduced in 1976. Each respondent answers four questions. At what price is the product too expensive to consider? At what price is it so cheap they would doubt its quality? At what price does it start to get expensive? At what price is it a bargain? Plot the answers, and the points where the curves cross suggest a range of acceptable prices. The method does not estimate how many people would buy.
• An A/B test. It compares two versions of the page with real visitors, so it needs traffic. Before starting, use a sample size calculator to find how many visitors each version needs.

What an AI user adds

• A buyer's first read. The persona has never seen your product. She reads the homepage, then looks for the pricing page, as a visitor would.
• A written comparison. The task asks her to compare the plans, their limits and what the free tier includes with the homepage's promise. It also asks her to check the FAQ or docs for hidden limits.
• A decision with reasons. The task asks her to finish with a clear decision on whether she would buy or sign up, and to say what convinced her or held her back. The replay shows every step that led to it.
• The same task after a fix. Run the template again and compare the two replays and their TRACES scores.

Where it stops

• The task tells the AI user to stop before paying. You need to test the checkout yourself.
• It has no money at stake. Its decision tells you how the page reads to one persona. It cannot tell you whether your price is right.
• Web runs use a fixed desktop window. You need to check the phone layout yourself.
• One run with one persona shows one path through your pricing. It cannot speak for every buyer.

Two real runs, both about finding the price

Both public runs below used the Purchase intent template, and in both the persona went looking for the pricing page. One reached it by typing the address and decided to sign up. The other got a not-found page at the usual pricing address and decided against.

The board's review kept only two week-38 runs for citing, each with a qualification shown as its note, so n=2. Read them as examples, not as a rate. The Product Hunt board has the whole week.

Every run here used Menso's Purchase intent template: the persona Zainab Salazar, a freelance UX consultant, reads the homepage, the pricing page and the FAQ, decides whether she would buy or sign up, and stops before paying. It is a route-specific diagnostic, not a product-wide score.

Made one of these products? Write to support@menso.io and we will correct or remove the example as soon as we can.